In this article, we will look into another pain point of creating transactions to test the approvals. if a transaction ends in error, we need to recreate or submit a new transaction.
From 21D, Oracle has provided us with an option to test the approvals using the simulate option.
Here are the list of enhancements for Approvals and Notifications as part of 21D update:
- We will now be able to test approval rules without being required to recreate and submit any new transactions in the HCM Approval Rules page and Transaction Console.
- Users will now be shown a warning message if a duplicate attachment is found in the transaction at the time of submission. Users are not allowed to submit transactions that have duplicate attachments.
- The Transaction Console diagnostic log for failed transactions has been enhanced to list the approval rule conditions and to also highlight the specific rule condition that caused the transaction to fail.
- We can now create rules in the Transaction Design Studio to configure the Save and the Save and Close buttons, and to configure whether an Error or a Warning message appears if mandatory sections have not been visited.
The new simulate feature in the HCM Approval Rules page and Transaction Console gives an easy way to test approval rule changes without having to recreate and submit any new transactions. We can easily debug and incrementally build conditional logic for approval rules and instantaneously see the impact of the change.
We can search transactions by name, who created them, and transactions created within a date range. Use the Status to further refine results.
The following statuses are available: Draft, In Progress, or Failed.
From the list of filtered transactions, we can choose anyone and then simulate the approval rule results based on the values in the transaction you selected.
Handling of Duplicate Attachments: users are not allowed to submit transactions that have duplicate attachments. Users will be shown a warning message if a duplicate attachment is found in the transaction at the time of submission.
Changes to the Diagnostic Log: the Transaction Console diagnostic log for failed transactions has been enhanced to list the approval rule conditions and to also highlight the specific rule condition that caused the transaction to fail, as shown below:
Finally, we can now create rules in the Transaction Design Studio to configure the Save and the Save and Close buttons, and to configure whether an Error or Warning message appears if mandatory sections have not been visited. There is a setup required for this feature.
For more information, see the What’s New for Human Resources > Transaction Design Studio for HCM Experience Design Studio Enhancements.
STEPS TO ENABLE
For the Transaction Console and Approval Rules enhancements, we must enable a profile option.
To enable the profile option, navigate to the Setup and Maintenance work area:
- Search for and click the Manage Administrator Profile Values task.
- Search for and select the profile option: HCM_TEST_APPROVAL_RULES_ENABLED.
- In the Profile Values region, the Profile Level should be Site.
- Set the Profile Value field to Yes.
- Click Save and Close.
This is the list of process names that are enabled for Approval Rules Simulation:
Documents Of Record
- Manage Documents of Record
Employment
- Hire an Employee
- Add Contingent Worker
- Add Pending Worker
- Add Non Worker
- Add New Assignment
- Add Work Relationship
- Manage Employment
- Transfer
- Promotion
- Change Manager
- Change Location
- Change Work Hours
- Change Assignment
- Manage Directs
- Termination
- Resignation
- Manage Work Relationship
- Employment Start Dates
- Cancel Work Relationship
- Local and Global Transfer
- Additional Assignment Info
- Delete Assignment
