Creating transitions

You use transitions to connect tasks in a ruleflow and define conditions on transitions to specify the sequence of the ruleflow from one task to another.

About this task

Transitions connect tasks in a ruleflow and define the sequence of the ruleflow from one task to another. Transitions are unidirectional. With multiple transition paths, you must specify the conditions under which a particular path is taken in the ruleflow.

Transition conditions denote the conditions under which the flow passes from one path to another. Whenever multiple transitions come from a choice, the transitions must have Boolean conditions that specify which path to choose during execution. The last remaining empty transition is automatically computed as an Else transition.

Note:

In transition conditions, the variable scope is restricted to ruleset parameters and variables. It does not include access to the working memory.

Important:

When multiple transitions originating from the same task define overlapping conditions, the path taken to execute the ruleflow is unpredictable. Make sure the conditions you define for multiple transitions do not overlap.

Procedure

To add a transition to a ruleflow:

In the Ruleflow Editor palette, click Create a transition, and then in the ruleflow diagram, click the source task and then the target task to connect them with the transition.
To specify a condition for the transition, in the Properties view for the transition, click Condition.
Provide a name for the condition in the Label field.
Select Use BAL for transition condition and type a condition statement. For example:
```
'the current rental agreement' is accepted
```
You can also write the condition using IRL. In this case, make sure the text fields contain a valid Boolean expression. If you do not use BAL, in the ruleflow diagram the transition arrow displays the label and the expression.

Results

The nodes and tasks of the ruleflow are now connected with transitions.