Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
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.

On The Design Of Parallel And Serial Approval Routes

In the approval rules step in the system, you know that there are some approval steps. For example, personal info and hire an employee or document records. When these approval flows are initially defined, serial or parallel can be selected. However, as the approval rules increase, they can change in the demands. For example, there are too many approval rules in our 'Manage Document Records' approval flow. All of them are serial. However, for a new document type, the human resource specialist said that the flow should be parallel and the approval should go to everyone at the same time.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!