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.

FYI Notifications Trigger in incorrect order when PARALLEL Participants are used in Approval Rules

Summary:

FYI Notifications Trigger in incorrect order when PARALLEL or SINGLE Participants are used in Approval Rules 

Content (required):

When we create a rule with below example

Level 1 goes to Representative for approval

Then after approval a FYI goes to Manager and also FYI to Representatives

When we use Approval Participants as SERIAL the above flow works correctly as below


but when we amend the Approval Participants to PARRALLEL or SINGLE then it sends the FYI notifications before approval is done by the REPRESENTATIVE as you can see below


We want to use SERIAL to fulfil our Approval requirements to allow a Representatives to claim the approval first when sent to many Representatives. So then only one approval is required.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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