Changed in 51.0.3.0 Playbook decisions and condition points

Use a condition point when you want to make decisions based on the values of incoming data. The condition point evaluates the incoming data by using Boolean operators, and uses the result to determine which outgoing path to activate in the playbook. You can add both field and script conditions to a condition point.

A condition point has the following properties:
  • 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 in the form of a field, or a script. When you click Create condition or edit an existing condition, you can add a field and a script to the condition:
    • 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 Setting conditions that activate a playbook.
    • Script builder to create conditions based on a value available in the playbook. For more information, see Script builder for condition points.
    • 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 good practice to use multiple condition points rather than using a condition point with too many outgoing paths.

The following screen 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.

New in 51.0.1.0 Adding a playbook loop

You can design loops in your playbooks, where the playbook goes back to a previous node in the playbook sequence from a condition point.

The following example shows a simple playbook loop:
  1. The playbook starts with an Initial Triage task.
  2. When the Initial Triage is completed and closed, the playbook moves to the next task in the sequence, which is Interview key individuals.
  3. When the Interview key individuals task is completed and closed, the playbook moves to a Notify internal management chain task.
  4. When the Notify internal management chain task is completed and closed, the playbook moves to a simple if/else condition point.
  5. If the condition is met, the playbook goes back or loops and re-opens the Interview key individuals task. If the condition is not met, the playbook progresses to the next step in the main sequence.
example playbook loop
Important: If you design a playbook with a loop, the following behavior occurs when the playbook runs:
  • A task is reopened if the playbook encounters it for a second time. For example, if a playbook runs and completes tasks A, B, and C, and if a loop in the playbook goes back by a condition point, tasks A, B, and C are reopened when the playbook comes to them. However, if tasks A, B, and C were already completed before this playbook had started, these tasks are skipped. But if your loop moves the playbook to a task for the second time during a given playbook execution, it reopens the task.
  • If your loop goes back to any scripts, sub-playbooks, or functions, they are re-run.
  • If you create a loop consisting of only scripts, the loop is allowed for 100 instances. If the script does not break or change the condition path after 100 instances, an infinite loop is assumed and an error occurs at runtime.