Decision activities

Create and define branches with different conditions for different paths that an agent can follow in playbook.

Before you begin

Role required: pd_admin

About this task

Add a decision activity to create a decision tree so that agents in Playbook Experience can troubleshoot if-then situations during runtime. Branches are the different paths with different conditions that agents can follow. For example, in a credit card approval playbook:

In this example, an agent can take different actions for different credit scores during a decision activity to assess the risk of a credit card applicant.

Decisions are not currently supported for stages, but you can create different stages and set different Run conditions to get achieve the same outcome.

Procedure

1. In Diagram view, hover on the object that you want to insert a decision activity next to, and select the + icon to add an activity.
   Note:

   Decision activities can only be added in Diagram view, but can be modified and viewed in Board view.
   The mini-picker displays.
2. Select the diamond icon to add a decision.
   A decision is added with two branches and the side panel opens for configuration.
3. Under the Details tab, fill in the following fields.

   Table 1. Decision details

   Label	Enter a unique name for your activity. This name appears in your playbook during runtime.
   Description	Optionally, enter some descriptive details about your activity.
   Start Rule	Choose when you want your activity to start running. Options include: When stage starts: Your activity starts running as soon as its stage starts running. Your stage starts running when your playbook is triggered. After specific activities: Your activity starts running after specified activities have finished running.
   Display order	Define the order in which this activity will appear during a playbook run.
   Run condition	After the activity starts, the activity runs only if specific conditions are met.
   Start with delay	Specify a duration of time to wait before running an activity whose start rule and conditions have been met. Give users a specific amount of time to complete actions. For more information, see Start with delay input properties.
   Restart rules	Choose what this activity does when a playbook is restarted: Skip on restart: Skip this activity when the playbook run is due to a restart. Run always: Always run this activity, including first runs. Skip on first run: Skip this activity during the first run. For more information, see Restart Playbooks.

4. Under the Branches tab, select your new branch to begin configuring it.
   1. Give your branch a unique label.
   2. Select the Add Condition button.
      The condition builder displays.

      Note:

      Branches can only be added in the side panel.
      
      
   3. Select or enter a field, operator, and value.
5. Add more branches as needed.
   Branches can only be added via the side panel.
6. If you add two or more branches, select whether to process all branches with conditions that are met, or just to process the first listed branch with conditions met.
7. If you selected to Process only the first one that is true, drag and drop the branch that you want to be evaluated to the top.
   
   

Related concepts

• Activity definitions
• Automation Assets
• Optional activities

Related tasks

• Add and configure a stage in a playbook
• Add and configure an activity in a playbook
• Parallel branches
• Add Dynamic Inputs to an Activity

Related reference

• Start with delay input properties