Approval rules

Many organizations rely on an approval process to ensure that requests are reasonable and fit an organization's budget.

Important: Classic approval rules have been replaced by the Workflow Studio Ask for Approval action. Use Workflow Studio to create workflow-driven approval logic that is easier to maintain and provides better reporting information.

The service catalog can use these classes of approvals:

• Gating approvals: Must occur before a request can be initiated. For example, allow a manager to reject an employee's request for a company car. To learn more about gating approvals, see Gating approvals.
• Process approvals: Take place within an execution plan process that has been initiated. For example, allow the security group to reject a request for access to SSN even though the employee's manager approved it. To learn more about process approvals, see Process approvals.

Note: To enable approval processes to operate smoothly, make sure that the appropriate users have the correct role, and that the role grants access to the necessary tables for users in all the relevant departments and domains.

• Set automatic approval rules
  Approval rules can automatically set the approval state to something other than Not yet requested. As a result, an approval rule can create a set of approvers. You can also start the approval process by setting the approval state to Requested.
• Gating approvals
  A gating approval acts as a gate through which a request must pass before it can start.
• Process approvals
  Once a request has passed its gating approvals, any relevant execution plans are initiated.
• Approve with a process guide
  Process guides work similarly to approval rules in that their execution is controlled via a condition.
• Schematic of a hypothetical approval process
  In the diagram below of a hypothetical approval process, the gating approval is color coded blue and an in-process approval is orange.

Parent Topic:Classic approvals