Introduction
In context with Absence Management Approval Workflow processes and configurations many a times one way have a requirement where-in certain absence transactions needs to follow an alternative approval routing based on a Descriptive Flex-Field (DFF) enabled on the Absence Recording page. Unfortunately this cannot be achieved as the DFF attributes are not available while defining approval rules on the Absence Approval workflow. But having said so one can still have a workround solution where they can make use of “Absence Reason” field.
In this post we would try to demonstrate the same with a worked out example.
Pre-Requisites
In order to proceed with this approach we need to make sure that there are some pre-existing setups in the system.
- Pre-Existing Active Absence Type
There should be a pre-existing absence type present in the system against which we can associate the newly created absence reason. For this example, we will choose the “Sick” absence type.
Worked-Out Example
We would need to do some configuration steps which are described below:
Creating a New Absence Reason
We would need to navigate to Setup and Maintenance -> Manage Absence Reasons-> Create New Reason
Associating Absence Reason to Absence Type
Next we would need to associate the absence plan with absence type.
Navigation: Setup and Maintenance->Manage Absence Type-> Search for “Sick” and add absence reason under “Plans and Reasons”
Enable Display Properties for Absence Reason
We would need to enable the “Reason” field under “Manage Absence Type” > Sick (Display Features)-> Primary Absence Details
Enabling Approval Processing for Administrator
As a next step we would also need to enable Approval processing for Administrator.
Navigation: Setup and Maintenance->Manage Absence Type-> Display Features-> Approvals and Processing Rules-> Approval Processing and Approval Reset on Update to Enabled for Administrator
Configuring “Global Absence Recording” Transaction Workflow
Next, we would need to configure “Global Absence Recording” workflow.
Navigation: Setup and Maintenance -> Manage Approval Transactions for Human Capital Management-> Global Absence Recording
We need to configure two rules:
Rule: ApprovalReasonKeyForHT
IF (absencesApprovalsRequest.absenceTypeReasons != "Sickness Absence Reason - Alternative Approval Routing") THEN “Management Hierarchy”
Rule: SicknessAbsenceAlternativeApprovalRouting
IF (absencesApprovalsRequest.absenceTypeReasons == "Sickness Absence Reason - Alternative Approval Routing") THEN “Self Auto Approve”
Verification
We will book a “Sick” absence without using “Sickness Absence Reason - Alternative Approval Routing”
Next, we will book and absence with Absence Reason as “Sickness Absence Reason - Alternative Approval Routing”
Once we are done with the Absence Recording we could check the status of the booked absences.
We could clearly see that based on the Äbsence Reason used one of the absence has got auto-approved while the other is still awaiting approval.
Now if we change the absence reason for the absence awaiting approval and change it to “Sickness Absence Reason - Alternative Approval Routing” we expect that the transaction would also change to “Completed” status.
Summary
So, this is how we can make use of “Absence Reason” to route the Absence Transactions in an alternative approach. Considering the current pandemic situation there might be organizations who may like to add a absence reason say “COVID-19” such that if employee chooses this absence reason during absence booking then the absences should get auto-approved. This solution would be very useful in such scenario.
Comments
Do you have any latest update on this issue please?
If Yes, please share.
Regards
Anusuya
RSS feed for comments to this post