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.

Requirement to adjust the BPM approval rule to skip one level

edited Aug 21, 2024 7:53AM in Recruiting, Opportunity Marketplace 1 comment

Hi Team,

I have a requirement to adjust the BPM approval rule to skip one level of management. Specifically, when a requisition is submitted by a recruiter, the approval should follow this path:

Hiring Manager (HM)
Line Manager Director (skipping the Hiring Manager's Line Manager)
In other words, instead of routing the requisition through the Hiring Manager's Line Manager, it should be directly approved by the Line Manager Director.

I tried this rule it does not work the approval goes to both Hiring Manager's Line Manager and Line manager Director
HierarchyBuilder.getManagerOfHierarchyPrincipal("supervisory",HierarchyBuilder.getManager("supervisory",Task.payload.transactionApprovalRequest.HiringManagerUsername,-1,null,"LINE_MANAGER"))

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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