Customize Playbook actions using forms, conditions, and scripts, components, or client actions. This customization enables users to submit forms, open records, and complete and skip activities.

1. Create the action and specify details.
   1. Navigate to Playbook Experience > Activity Actions.
   2. Select an action assignment or click New to create a new one.
      Note: For a list of default actions, see Playbook actions.
   3. On the form, fill in the fields.

      Table 1. Action Assignment form

      Field	Description
      Action Label	Label that appears on the button created through the action.
      Action Name	Name for your action that appears in the action assignment list.
      Implemented as	Type of action that is implemented. For example, UI Component.
      Specify UI Component	UI component that is associated with the Implemented as field. When the Implemented as field is set to UI Component, this field specifies a UI component that is displayed when the action is triggered.
      Declarative Actions Render Mode	Render mode on a Playbook card. Specify how the action should be rendered on the Playbook card. Select Button, Header Dropdown, or Header Icon.
      Button Type	Button type that's displayed in the Playbook UI. Select Primary, Secondary, or Tertiary.
      Form fields required	Option that communicates that the action requires data from the user to proceed. This field is consumed in the Playbook experience UI in the following ways. When an activity contains a form that's too large to fit on a card, the form is hidden in a modal. When an Activity contains a form but doesn't have actions that require form fields, the form is not rendered. Instead, the fields on the form are rendered as a stacked collection of label-value pairs. This field can be overridden by creating a custom activity renderer.
      Tooltip	Message that's displayed in the Playbook UI when your cursor points to the action.
      Description	Description for the action that's displayed in the Action Assignments list.
      Application	Application for the action assignment.
      Workspace	Workspace that the playbook action is associated with. For example, ServiceNow®ITSM or HR. Note: This field is not required.
      Table	Field to limit this action to activities with this associated table.
      View	Field to limit this action to activities with this Form View.
      Active	Option to activate the action.
      Order	Integer that determines the precedence of this action in relation to matching actions with the same name. The lower the number, the more likely it is to be selected against other actions. This ordering enables you to override other actions with your own. The typical practice is to use numbers that are in the hundreds. For example, 100, 200, 300, or 400.

   4. Click Update.
2. Set up conditions for the action.
   1. Click the Conditions tab.
   2. On the form, fill in the fields.

      Table 2. Conditions form

      Field	Description
      Script Condition	Script condition for the action assignment. Enter sn_playbook.PlaybookExperience.parentRecordContainsPlaybook(current). This script enables you to show a Playbook only when the record has triggered a process execution. Note: Adding queries involving multiple joins can impair performance.
      Client Conditions	Choose conditions to limit collisions based on your use case.
      Record Conditions	Choose conditions to limit collisions based on your use case.
      Required Roles	Roles to limit Playbook access.
      Requires create access	Option to require create access.
      Requires read access	Option to require read access.
      Requires write access	Option to require write access.
      Requires delete access	Option to require delete access.

3. If Server Script is selected in the Implemented as field, provide script for the action.
   • Server scripts can reference the associated record of an activity using the Current variable.
   • Calling current.update() updates the associated record with values that the user provides from embedded forms on Playbook cards.
   • Server scripts can reference the parent record of an activity using the parent variable.
4. If Client Action is selected in the Implemented as field, optionally specify the payload mapping on the Action Attributes tab.

   Payload mapping enables you to override portions of the payload dispatched by the client action. For example, the Preview Record client action enables you to open a record on a new Workspace tab. Using payload mapping, you can specify a related item tab that's displayed when the form is opened. Set the defaultTab to do this.

5. If UI Component is selected in the Implemented as field, optionally specify the component’s attributes on the Component Attributes tab.
6. Click Submit.