Condition builder
You use the Condition builder to create those conditions that trigger the playbook.
- Automatic activates the playbook when the specified conditions are met. The Automatic activation type requires at least one condition.
- Manual uses conditions to determine when the playbook appears in an incident's Action menu, where a user can choose to activate the playbook. If no conditions are specified, the playbook always appears in the object's Action menu.
The playbook's object type determines which conditions are available. You can set an "is created" condition, various conditions for fields, or both. With specific object types, you can select fields from the parent object; for example, you can select incident fields for a playbook that has a Task or Note object type.
You access the playbook's conditions by clicking the activation node to display Activation details.
If there are no conditions, click Create condition. If there are conditions, they are listed along with an Edit condition link. Both open the Condition builder page.
- Choose a condition menu.
- Click Add condition to define more conditions.
- If there is more than one condition, determine how to implement the conditions using All, Any, or Advanced. For more information, see Conditions.
- Click Done when finished.
The following screen capture shows three conditions where all must be true to trigger the incident. An incident must be created, the City must be Boston, and the State must be Massachusetts.