How Do I Route Tasks to My Approvers?
Define routing patterns to build parts of an approval process that you can use in your step flow and assignment rules. For example, you can define a rule to get approval from an approval group instead of a specific user. Routing patterns work together, so for example, you can set an approval group as the designated approver in an approval authority.
You can think of routing patterns as an alias. Changes made to a pattern are reflected wherever they’re used.
| Routing Pattern | Description |
|---|---|
| Approval group | Create a group of users you can make assignments to. Require approval from the first responder, all group members, or in sequence. |
| Authority matrix | Define conditions and use the supervisory hierarchy and job level assignments to determine a supervisor with a sufficient spending limit to assign approvals to. |
| Approval authority | Map condition attributes, the conditions and limits you want met, and approvers or approval groups to assign approvals to. |
| Supervisory hierarchy | Use the supervisory hierarchy to determine the assignee, based on a starting point in the hierarchy and the number of levels or a specific job level. |
| Named condition | Name a set of condition attributes that can then be referenced in steps, approval authorities, or authority matrixes. |