A decision specifies which path to take, when several paths are possible.
A decision can have one or more input flows and one or more output flows, each labeled with a distinct guard condition, a condition that must be satisfied for an associated flow to execute some action. Your guard conditions should avoid ambiguity by not overlapping, yet should also cover all possibilities in order to avoid process freeze.
A decision can represent:
-
A conditional branch: one input flow and several output flows. In the following example, the control flow passes to the left if the age given in the application form is <18, to the right if the age is >65, and takes the another route if the age is not mentioned:
You can display a condition on the decision symbol in order to factorize the conditions attached to the flows. In the following example, the condition Total * NB + VAT > 10.000 is entered in the Condition tab in the decision property sheet, and True and False are entered in the Condition tabs of the flows:
-
A merge: several input flows and one output flow. In the following example, the Subscription and Charge account flows merge to become the Ship order flow:
A decision allows you to create complex flows, such as: