Condition points use data and Boolean condition statements to determine outgoing paths.
- Multiple incoming paths.
- Multiple outgoing paths. Each outgoing path requires a condition.
- Two condition settings.
- First true condition setting allows a single path only when a true condition occurs. With this setting, you can assign a condition to one path only. The Condition point on the canvas includes the setting name and has a purple indicator when set to First true condition. With this setting, conditions are evaluated from first to last as shown in the Condition point panel. Therefore, if multiple conditions are true, the first true condition that is evaluated is the one that is used.
- Any true condition setting allows multiple paths by activating a path for each true condition. With this setting, you can assign a condition to multiple paths. The Condition point on the canvas includes the setting name and has a green indicator when set to Any true condition.
- Conditions, which you provide as Boolean logic or a script. When you click Create
condition or edit an existing condition, you can choose to use the Condition builder or
- Condition builder creates Boolean logic conditions. It is the same as the condition builder used for the playbook activation except you must provide a descriptive name for the condition. The condition name cannot be more than 100 characters. For more information, see Condition builder.
- Script builder to create conditions based on a value available in the playbook. For more information, see Script builder.
- If you set the Condition point to First true condition, the conditions are evaluated in the order that you create them. If you need to change the order, you must delete then add the conditions back in the order you require.
- A condition must be associated with each outgoing path. You cannot have an unused condition.
- An Else condition that is used as a default path. It is true when none of the other conditions are met. You can assign an Else condition to one path only and can be used in either of the condition settings. The Else condition is mandatory for each Condition point.
- You can add multiple Condition points in a playbook.
You can define many outgoing paths; however, it is suggested to use multiple Condition points rather than using a Condition point with too many outgoing paths.
The following screen capture shows a Condition point that has two conditions, City and Region. Either condition can activate its path. The Else condition is activated only when both conditions are not true.
The following screen capture shows the screen that is displayed where you can create a condition based on a script.