Playbooks
You use a playbook to define the response to incoming and changing events.
A customization is a tool within the playbook toolkit that can act upon, supplement or contain data. Customizations include functions, message destinations, tasks, notes, artifacts, and scripts.
- Playbook designer. A graphic-based tool that allows you to define the conditions to trigger the playbook, and organize various customizations into a comprehensive set of actions.
- Rules and workflows, formerly referred to as dynamic playbooks. Rules allow you to define the conditions to trigger the playbook and the subsequent activities. Workflows are a graphically designed set of activities you use to create a complex set of actions using various customizations.
The Playbook designer is the next step in the evolution of playbook design. It allows you to graphically design your conditions and subsequent activities. It uses all of the customizations in the playbook toolkit except rules and workflows, since it incorporates the capabilities of each.
Rules and workflows provide more flexibility in addressing use cases. Rules allows you to define more advanced conditions. Workflows are triggered by rules and also allows you to graphically design your activities using customizations in the toolkit. Unlike the Playbook designer, playbooks built with rules and workflows are not shown graphically in the user interface.
Ideally, you should design your playbook using Playbook designer when possible, and use rules and workflows to address use cases not supported by the Playbook designer.
You build multiple playbooks for different scenarios. One playbook can trigger another playbook if the result of the first playbook matches the condition set by the second playbook.