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.
Requisition Approval Visibility
Summary:
Creating a Requisition Approval path that is robust
Content (please ensure you mask any confidential information):
Our current Requisition approval path is pretty much straight forward. for example, if the Requisition is an add to headcount, the approval path is, HR Rep -> Hiring Manager one over -> Hiring Manager 2 over, Else approved. One idea is to base the approval path on 'role' approvals vs hierarchy, i.e. HR, VP, SVP and or contextualize approvals by Generic title/Job Families/or Template. Is this possible? What are others doing to put more visibility around Req. approvers?
I saw that there is a way to add approvers ad hoc so this could be one solution.
Tagged:
0