Introduction
Usually, most of the times the approval flow followed is sequential in nature meaning one individual approves and then it goes to the 2nd approver and the process continues till the final approver has approved the transaction. But many a times there is a need to send parallel approval notifications for a specific transaction where-in all the approvers get notification at the same time and the moment one of the responders approves then the transaction gets completed.
A theoretical explanation is provided in attached meta-link note:
Fusion Global HR: How to Configure Parallel Approval Rel 10 (Doc ID 2081545.1)
In this article, we would simply follow the steps and verify if we can achieve the same using an example.
For this example we would try to make a location change for an individual and check whether parallel notifications are send. For this, we would need to perform the following pre-requisite tasks:
-
Identify the Job Role which controls the “Change Location Action”
A quick search on MOS (My Oracle Support) reveals that 'Business Unit Selection Duty' Duty Role is required to approve Change Location Action Transaction. The delivered Job Role “Human Resource Specialist” has this duty role attached to it.
-
Make a custom Job Role from the seeded Job Role (‘Human Resource Specialist’ for our example)
We will make a Custom Job Role by using following steps:
Security Console-> Human Resource Specialist -> Copy Role Option from dropdown
Once the above steps are completed a request will be submitted
We can navigate to the Authorization Tab and move to Role Copy Status to find the status of the operation
Once done we need to run the below ESS Scheduled Processes:
-
Send Pending LDAP Requests
-
Retrieve Latest LDAP Changes
And once the jobs are successfully executed we would be able to find the Custom Role
At this point we should perform a Compare Roles operation between the delivered roles and the custom created roles and the different ways in which this comparison can be done is detailed below:
-
All
Displays the comparsion result after comparing all the features of both the roles
-
Only In First Role
Displays the features which are only present in First Role and not in second
-
Only in Second Role
Displays the features which are only present in Second Role and not in First
-
In Both Roles
Common Features present in both the roles
This can be easily illustrated with the help of below table
Compare Roles |
|||
All |
Only in First Role |
Only in Second Role |
In Both Roles |
|
|
|
|
Remember we have already attached the custom job role to the users whom we want to include in Parallel Approval.
Next we would need to create a custom HCM Data Role
Creating a Custom HCM Data Role
We would need to navigate to “Assign Security Profiles To Role” task in Setup and Maintenance and create a custom Data Role
Making Changes to Change Location Approval Rule
We would need to navigate to “Manage Approval Transactions for Human Capital Management” Task under Setup and Maintenance and configure Approval Rules for “Change Location” Transaction
Screenshot below explains the new rule clearly
Initiating Change Location Transaction
Now since we have completed all the configuration related steps, we may proceed with performing a “Change Location” Transaction.
We would try to change the location of Christelle, Stevenson (Person# 1007) and we would initiate the Transaction using the Person Gallery Option (from ANTONIO.SANTOS who is the Supervisor of Christelle)
We will now submit the transaction and verify if the approval notification has gone to all users who have the Application Data Role “Human Resource Specialist Change Location Parallel Approval” assigned to them.
Application Data Role: Human Resource Specialist Change Location Parallel Approval |
|||
Assigned User 1 ALBERT.THOMSON |
Assigned User 2 CATHY.BETTY |
Assigned User 3 DEREK.FRANZ |
Assigned User 4 GARY.THAY |
|
|
|
|
Now once we approve this transaction from any of these users (say CATHY.BETTY in this case) by clicking on the ‘CLAIM’ option the notification will no longer be available for action for other users.
Once “CATHY.BETTY’ has taken action on this transaction we try to login with “GARY.THAY” who is also a user who holds parallel approval rights on this transaction and try to search for this notification:
Inference / Summary
So this is how we can configure Parallel Approval in Oracle HCM Cloud Environment thereby ensuring multiple users get notification for a single transaction at a same time and the moment nay of them takes action on the transaction the notification is no longer available to other approvers (in short FIRST RESPONDER wins scenario)
Comments
RSS feed for comments to this post