Skipping an Approval Level with the Supervisory List Builder and Rule Priority

Say you want to approve a budget version for baseline using alternate level approvals. You can configure the ApprovePlanVersion workflow to route the approval sequentially to every other level in the management hierarchy, rather than to every immediate superior.

Let’s say we have the following hierarchy defined in Oracle Cloud HCM.

Person	Position	Manager	Approval Required
David	Project Manager	Henry	Yes
Henry	Senior Manager	Nick	No
Nick	Group Manager	Abraham	Yes

The budget version must first be approved by David. After David approves, the workflow should then skip Henry and route the budget version approval to Nick. After Nick approves, the workflow should move into the approved state.

In such case, edit the predefined rule set to define an additional rule that uses rule priority and a try-catch action.

Follow these steps:

1. In Setup and Maintenance, click the Task Panel, then search for and click the Manage Task Configurations for Project Financial Management task.

   The BPM Worklist application appears.

2. In the Tasks to be configured pane, search for the ApprovePlanVersion task, and click the ApprovePlanVersion link.
3. Click the Edit Task icon in the Tasks to be configured pane to open the task in edit mode.
4. Click the Assignees tab.

   The participants who must approve project budgets or forecasts are displayed. Click on each of these participants to review the workflow rules that apply to their approval choices.

5. Click the Approver participant in the workflow, click the Go to Rule (the diamond shaped) icon within the Approver box, and then click the Go to Rule option that appears.

   The list of rules associated with the Approver participant are displayed. Ensure that the BudgetForecastAMXRuleSet rule is selected in the drop-down list.

6. Change the rule priority to ensure that the workflow notification is sent to the project manager and only after this approver approves, notifications are sent to the next approver.
   1. Select the SoaOLabel.FinancialPlanApprovalRule.BudgetorForecastApprovalRule predefined rule.
   2. Click the Properties link.
   3. Select Highest from the Priority drop-down list, select the Advanced Mode check box, verify that the Active check box is selected, and click OK.
7. Change the IF condition of the predefined rules from 1 is 1 to 1 is 2 to disable the predefined workflow from sending project budget or forecast approvals to the project manager for approval.
8. Add the skip level rule, as follows:
   1. In the Rules pane, click the Advanced Add or Modify Options (the + icon) drop-down list and select General Rule.
   2. Click the Properties link, enter SkipLevel in the Name field, add the description, select Medium from the Priority drop-down list, verify that the Active check box is selected, select the Advanced Mode check box, and click OK.
   3. Click the Insert Pattern link.
   4. In the IF part of the rule, add the Task is a Task pattern by entering Task in both the text boxes. Then, click the Advanced Add or Modify Options drop-down list and select simple test, and add the IF condition, as follows:

      Value to Enter in the Left Text Box	Value to Select in the Number Comparison Drop-down List	Value to Enter in the Right Text Box	Why to Add the IF Condition
      Task.payload.planClassCode Note that you can also select this value by clicking the Left Value search icon and selecting Task.payload.planClassCode in the Condition Browser dialog box.	is	"BUDGET" This value is case-sensitive. Include the quotation marks. Don't copy and paste this value. To meet similar requirements for forecasts, enter "FORECAST".	To specify that the rule is applicable only for budget versions.

   5. In the THEN part of the rule, click the Insert Action drop-down list and select try. Then, perform these actions in the following order:

      Where to Perform the Action	Action to Perform	Result
      Under the try action	Click the Insert Action drop-down list and select catch.	The catch action is added.
      Under the catch action	Click the Insert Action drop-down list and select Add Approver > Supervisory.	The Supervisory list builder is added.
      Under the catch action	Select the check box against catch and click the Move down icon.	The Supervisory list builder moves directly under the try action.
      Under the try action	Enter the values as follows: Response Type: Required Number of levels: 1 Starting Participant: HierarchyBuilder.getManager("supervisory",HierarchyBuilder.getManager("supervisory",Task.payload.approvePlanPayload.approverName,-1,"","LINE_MANAGER").getId(),-1,"","LINE_MANAGER") Top Participant: HierarchyBuilder.getManager("supervisory",HierarchyBuilder.getManager("supervisory",Task.payload.approvePlanPayload.approverName,-1,"","LINE_MANAGER").getId(),-1,"","LINE_MANAGER") Note: Replace “LINE_MANAGER” with the hierarchy type that you define in Oracle Cloud HCM. Auto Action Enabled: False Auto Action: null Rule Name: “SkipLevel” Note: The rule name is autopopulated, its the name that you entered in Step 8. Dimension Id: null Note: The dimension id is autopopulated as null.	NA
      In the catch action	Select the check box against catch and click the Delete Action icon. Note: Before you perform this action, ensure that only the check box against catch is selected.	The catch action is deleted.
      In the try action	Select the check box against try and click the Insert Action drop-down list and select catch.	The catch action is added.
      In the catch action	Enter Object as the target and e as the identifier value in the text boxes.	NA
      Under the catch action	Click the Insert Action drop-down list and select return.	NA

      Note: If the try and catch actions are indented at the same level, it indicates that the rule is configured correctly.
9. Click Validate on the top right corner to validate the newly defined rules.
10. Click the Save icon in the Tasks to be configured pane to save the rules.
11. Click the Commit task icon in the Tasks to be configured pane to complete the rule configuration.
12. Click OK to close the confirmation message window.