Approval rule grouping and sequencing

  • Release version: Yokohama
  • Updated January 30, 2025
  • 3 minutes to read
  • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Approval rule grouping and sequencing

    Procurement Administrators can associate approval rules with approval groups and define the sequence in which these groups are evaluated. This enables a set of approval rules within a group to trigger sequentially rather than simultaneously, streamlining the approval process for purchase requisitions.

    Show full answer Show less

    Approval rules within a group are evaluated only if all rules in that group are satisfied, while multiple approval groups are evaluated simultaneously. Rules not assigned to any group are evaluated concurrently with grouped rules. Grouping also prevents duplicate evaluations by treating satisfied rule groups as fulfilling their individual rules.

    Key Features

    • Sequential evaluation within approval groups: Rules are triggered in a defined order rather than all at once.
    • Simultaneous evaluation across multiple groups: Multiple approval groups can be evaluated at the same time.
    • Independent evaluation of ungrouped rules: Rules without groups are evaluated alongside grouped rules.
    • Approval Group table and rule composition: Approval group details and the order of rules within groups are managed through related lists in the Approval Group table.
    • Resend approval for reassessment property behavior: For grouped rules, this property applies only if the same group rules are satisfied after a merge or revision. For rules evaluated independently or ungrouped, the property behaves as usual.

    Practical Scenarios

    • Scenario 1: Sequential triggering of approval rules (A then B) prevents simultaneous approval requests for a purchase requisition.
    • Scenario 2: Rules A and C trigger first, followed by B, optimizing the order based on conditions like product category and job hierarchy.
    • Scenario 3: With multiple purchases, grouped rules A and D trigger first, followed by B and C, managing complex approval flows efficiently.

    Impact on Resend Approval for Reassessment

    The property controls whether approvals are resent after a revision:

    • If set to No, only approvals for rules newly satisfied are resent individually.
    • If set to Yes, all approvals in the group that are satisfied after revision are resent, including any new rules triggered.

    This ensures that approval reassessment aligns with rule group status, avoiding unnecessary or duplicate approval requests.

    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
    Figure 1. Approval rules A and B
    Approval rules A and B
    • 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
    Figure 2. Approval rules A, B, and C
    Approval rules A, B, and C
    • 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
    Figure 3. Approval rules A, B, C, and D
    Approval rules A, B, C, and D
    • 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.

    For example, in scenario 2:
    • 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.