Define Multi-Level Approvals

Use the Approval Block Editor (accessed from within the Approval Editor) to create multi-level approvals.

You can use multiple dependent Approval Blocks to define multi-level approvals (different triggers, approvers, and actions for different situations within the same Business Object). For example, an Emergency Change Request might require that all Emergency Change Board members approve the change, whereas a regular server change might require only the approval of a hardware team member.

Multi-level approvals are also used for requests that require multiple individuals or teams to provide approval during each stage of an approval process. For example, the Networking Team might need to approve a Change Request before it is sent to the CAB (Change Advisory Board) for approval.

When you define multi-level approvals, you create multiple Approval Blocks that depend on each other. Specifically, the action that occurs as a result of the first Approval Block is the trigger condition for the second Approval Block.

To define a multi-level approval:

1. Open the Approval Block Editor.
2. Define the trigger condition for the first approval:
   1. Create a condition using a comparison clause and/or a grouping clause. See Define a Group Clause.
   2. Select the Leave Approvals if condition was changed by a block action option.

      This option must be selected because it prevents the first-level approvals from being deleted when the approval advances to the second-level approval.

3. Define the approvers for the first approval.

   You must select either Count block and manual or Count this block only to include approvals related to the first Approval Block.

4. Define the action for the first approval.

   You must clear the Executing the action completes the approval process check box so that the second level of approvals can occur (this action serves as the trigger condition for the second level of approvals).

5. Select OK.

6. Select Add on the Approvals page.
7. Define the trigger condition for the second approval:

   The trigger condition of the second approval should be made true by the action of the first approval.

   1. Create a condition using a comparison clause and/or a grouping clause.

      You also have the option to select Advanced to define a more complex condition.

   2. Select the Leave Approvals option.

      This option is recommended for the second level of approvals, so that the approval remains connected to the Business Object after the condition is no longer true.

8. Define the approvers for the second approval.

   You must select Count this block only in the drop-down list so that the results from the first approval are not counted in the results for the second approval.

9. Define the action for the second approval.
10. Define additional Approval Blocks as needed.

11. Select OK.