Objective
Demonstrate a simple use-case scenario involving the Multiple-Condition Activity shape.
BUSINESS REQUIREMENT
Implement the following business logic:
If price change is greater than 20%, then auto-reject, else if price change is between 5 and 20%, then request approval, else auto-approve?
Resolution
The above use case can be easily achieved by using the Multiple-Condition Activity shape as shown here:
In AgilePoint, conditions can also be made against different data types such as integer, string … etc. In addition to using specific percentage numbers in the conditions per requirement as shown in the following, more flexible and dynamic category-based conditions can also be used (as shown below). These categories can be associated with configurable variables instead of hard-coded in the condition. Using variables allows changes to the percentage number to be made without requiring changes to the hard-coded conditions in the activity.
