Approval rule grouping and sequencing
Summarize
Summary of Approval rule grouping and sequencing
ServiceNow enables Procurement Administrators to associate approval rules with approval groups and define the sequence in which these rules are triggered. This grouping and sequencing ensure that rules within a group are evaluated sequentially rather than simultaneously, allowing for more controlled and logical approval workflows. Multiple approval groups are evaluated simultaneously, but rules within each group follow the defined order.
Show less
Key Features
- Approval Grouping: Approval rules can be grouped so that all rules within a group must be satisfied for the group to be considered satisfied.
- Sequencing: Rules within a group are evaluated in a defined sequence, enabling staged approvals (e.g., manager approval before IT department approval).
- Simultaneous Evaluation: Multiple approval groups are evaluated simultaneously, but rules inside each group are sequential.
- Independent Rule Evaluation: Rules not associated with any group are evaluated at the same time as grouped rules.
- Prevention of Duplicate Evaluations: Once a rule group is satisfied, individual rules within the group do not need separate evaluation, reducing redundancy.
- Approval Group Storage: Group and sequencing details are maintained in the Approval Group table with related lists defining rule order.
- Resend Approval for Reassessment Impact: The “resend approval for reassessment” property applies differently depending on whether rules belong to a group or are evaluated independently, controlling when approvals are resent after revisions or merges.
Practical Examples
- Without grouping and sequencing, multiple approval rules trigger simultaneously.
- With grouping and sequencing, rules trigger in a logical order, for example:
- Scenario 1: Rule A triggers first, then Rule B after A completes.
- Scenario 2: Rules A and C trigger first, then Rule B after A completes.
- Scenario 3: Rules A and D trigger first, then Rules B and C after A completes.
Impact on Resend Approval for Reassessment
The resend approval for reassessment property behaves as follows:
- If rules belong to a group, this property applies only when the same rules in the group are satisfied after revision or merge.
- For rules evaluated independently, the property behaves normally.
- Examples illustrate that setting this property to Yes or No affects whether approvals are resent when rules are satisfied due to revisions, ensuring appropriate approval notifications.
This functionality allows ServiceNow customers to design flexible, clear, and efficient approval processes that reduce redundant approvals and align with organizational workflows.
As a Procurement Administrator, you can associate approval rules with approval groups and define the sequence to determine when these rules should be triggered. With this association, a set of approval rules within a rule group is triggered in sequence, instead of all of them being evaluated simultaneously.
For example, when purchasing an IT-related product, a manager can first approve the purchase before sending it to the IT department for approval.
Rules within an approval group are evaluated only if all the rules within it are satisfied. If there are multiple approval groups, all groups are evaluated simultaneously. For approval rules that do not have an associated approval group, evaluation is done as-is at the same time with rules that are associated to approval groups. By default, all rules in an approval group are also evaluated independently. If a rule group is satisfied, then the individual rules do not need to be evaluated. This prevents a Procurement Administrator from creating duplicate rules that need to be evaluated independently and also within the context of an approval group.
Consider the following scenarios:
Scenario 1
- Purchase requisition amount is $8,000
- Business owner’s job code is IC3, cost center is Engineering
- Business owner’s managerial job code hierarchy is IC3 => M3 => M4 => CFO
- Without rule group and group sequencing, approval rules A and B are triggered simultaneously.
- With rule group and group sequencing, approval rule A is triggered first, followed by approval rule B when A is complete.
Scenario 2
- Purchase requisition amount is $8,000, supplier product belongs to the XYZ product category
- Business owner’s job code is IC3, cost center is Engineering
- Business owner’s managerial job code hierarchy is IC3 => M3 => M4 => CFO
- Without rule group and group sequencing, approval rules A, B, and C are triggered simultaneously.
- With rule group and group sequencing, approval rules A and C are triggered first, followed by approval rule B when A is complete.
Scenario 3
- One purchase made for $120k
- Another purchase made for $95k
- Without rule group and group sequencing, approval rules A, B, C, and D are triggered simultaneously.
- With rule group and group sequencing, approval rules A and D are triggered first, followed by approval rules B and C when A is complete.
Approval group details are stored in the Approval Group table. Within each approval group, there is an approval rule composition related list to define the order of approval rule evaluation within that specific group.
Impact of rule groups and sequencing on the resend approval for reassessment property
If approval rules that belong to a rule group are triggered, the resend approval for reassessment property is only applicable if the same rules within that rule group are satisfied as a result of a merge or revision.
In the scenario where there are rules that belong to a group, and are also evaluated independently, the resend approval for reassessment property is only applicable if the same rules within the group are triggered. For rules that do not belong to a group, the property behaves as-is.
- If the resend approval for reassessment property is set to No, and as a result of a revision, approval rule A is satisfied, rule B is not satisfied, and rule C is satisfied, then approvals are resent to the approver for rule A.
- If the property is set to No, and rules A, B, and C are satisfied as a result of a revision, then the approvals are not resent.
- If the property is set to Yes, and rules A, B, and C are satisfied as a result of a revision, then all approvals are resent.
- If the property is set to Yes, and rules A, C, and a new rule D are satisfied as a result of a revision, then approvals A and C are resent, and a new approval D is sent.