Get Started with Redwood for Oracle Cloud HCM Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
BPM Sequential Approvals Expiration Policy
Hello Team,
Business has decided to implement Expiration policy to the Change Working Hours task.
The rule has been setup as sequential, and the goal is: if the 1st approver does not act within the designated time, then the process moves to the 2nd approver.
The above process is described here even tough not an HCM manual BPM is of common use as far as I understand it.
And we proceeded to do just that, the 2 steps are created as serial.
And the expiration policy has been enabled from Deadlines:
Each rule works fine, however at expiration time the entire transaction expires, and the working hours are returned to the original value, and it does not pass to the 2nd approver. We have also tried with
Tagged:
0