Evaluating a Rule with Multiple Conditions

This example shows a scenario where a process is routed based on the value of a logical rule with multiple conditions using the Multiple Condition AgileShape.

Instructional Goals

  • Demonstrate how to route a process based on a logical rule with multiple conditions using theMultiple Condition AgileShape.

Example Process: Budget Request and Fulfillment

Problem Statement

Submit and approve a budget request.

Business Requirements

  • The process is initiated when an employee submits a budget request form.
  • The request is routed for approval and fulfillment based on one of 3 conditions:
    • If the request is greater than or equal to $1000, the request goes to the CFO for approval.
    • If the request is greater or equal to $100 (but less than $1000), the request is routed to the Manager for approval.
    • If the request is less than $100, it does not require approval, and goes straight to accounting for fulfillment.

Navigation

  1. In AgilePoint Envision, open a process template.
  2. Navigate to the Generic BPM stencil.
  3. On the Generic BPM stencil, drag the Multiple Condition AgileShape, and drop it on the process template.

Instructions

  1. On the New Condition Activity Window - Multiple Condition AgileShape, complete the fields as required to bind the Multiple Condition AgileShape to the Budget Amount field in the Submit Request form.
  2. Click OK.
  3. On the Condition Window, complete the fields as required to set up the following conditions:
    • BudgetAmount >= 1000 - This condition is routed to CFO Approval.
    • BudgetAmount >= 100 - This condition is routed to Manager Approval.
    • Else - This condition is required. It handles all values not included in the other conditions. In this case, that includes any amount under $100. These cases are routed directly to Accounting for fulfillment.