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.
Approval Fails when 2nd line manager does not exist (even though manager level is set to 1 in rule)
Summary:
We have just noticed that one of our approvals fails, because a second line manager does not exist within the manager hierachy of the proposed line manager that gets the FYI notification. However, we have set the level to one, thus we expect the system to only consider the immediate proposed line manager and ignore any line managers higher up the org. chart.
Content (required):
Question: why is this happening and how can we force the system to just consider the first line manager as we set it in the rule?
Version (include the version you are using, if applicable):
0