Create a playbook

Enable playbook owners to configure and organize multiple instances of Workflow Studio content into an automated business process on the ServiceNow AI Platform®.

始める前に

• Activate Playbooks for your appropriate application.
• Familiarize yourself with the tables and relationships that your application uses for the playbook that you want to create.
• Make sure to familiarize yourself with any features that your business uses to automate operations on the ServiceNow AI Platform, such as flows, subflows, and actions.
• Learn how to get started with ServiceNow® Process Automation.
• Role required: admin, playbook.admin, or playbook.write. To learn more about playbook authoring access in Workflow Studio, see User access to Playbooks in Workflow Studio.

このタスクについて

手順

1. Navigate to All > Workflow Studio > Playbooks.
   The Workflow Studio landing page appears. Playbooks are shown by default, but you can toggle to flows, subflows, actions, and decisions.
2. In the upper right corner, click New and select Playbook from the drop-down menu.
   The Playbooks builder details screen for a new playbook opens in a new tab.
3. Fill in the following fields.

   Field	Action
   Playbook name	Enter a unique, user-facing name for your playbook. This name appears to agents and fulfillers during runtime of your playbook.
   Description	Optionally, enter some descriptive details about your playbook.
   Application	Choose an application scope that you want your playbook to run in. Selecting Global lets your playbook run in any application scope. For more information, see Application scope.

   The builder displays in Diagram view by default, but you can select Board view to switch views. Switch between views anytime as you build your playbook.
   
   
4. Select the Start node.
   The Playbook properties side panel opens.
5. Under the Details tab, update or fill in the following fields.

   Field	Action
   Playbook name	Enter a unique, user-facing name for your playbook. This name appears to agents and fulfillers during runtime of your playbook.
   Parent table	Select the table that you want your trigger records and other playbook inputs to come from. 注: This field is required for Knowledge and Email activities.
   Description	Optionally, enter some descriptive details about your playbook.
   Limit playbook executions for each parent record to	Limit the number of times a playbook can run for a single parent record.
   Allow this playbook to be restarted during runtime	Allow runtime users to restart the entire playbook during a run.

6. Under the Inputs tab, add inputs for a playbook to launch with.
   Inputs defined here are accessible throughout the playbook via dot-walking and dot notation (e.g. inputs.inputName) and can be used in activity fields, conditions, and UI elements.

   ヒント:

   Use this to trigger a playbook with API inputs instead of trigger records.
7. Under the Runtime permissions tab, add sets of users, user groups, user criteria and roles, and define whether they can add optional activities to the playbook, restart the playbook or its stages and activities, or cancel the playbook during runtime.
8. Configure your trigger.
   注:

   You can create a playbook with no trigger, a single trigger, or multiple triggers.
9. Add a stage.
10. オプション: Add a decision stage.
11. Add an activity.
12. Keep adding stages and activities according to your manual playbook.
    For an example of how to design an entire digitized process with Playbooks, see Create a sample playbook.
13. オプション: If you don't see the activity you need to add in the activity picker, create an activity definition.
14. オプション: Add a decision activity.
15. オプション: Add parallel activities.
16. オプション: Add optional activities.
17. After you've added all appropriate stages and activities to your playbook, select Activate in the header.
    Activating your playbook publishes it so that it runs when triggered.

    注:

    If you change your playbook after activating it, the system saves your changes but deactivates your playbook. You must click Activate again to publish any new changes to your playbook. For more information, see Playbook statuses and activation states.

タスクの結果

When your playbook's trigger conditions are met, your playbook runs. As a result, the system creates a Process Execution record and renders user-facing configurations for Playbook Experience. For an example of how to digitize a manual business process that renders as a playbook, see Create a sample playbook.

次のタスク

Set up the Playbook Experience for your agents and fulfillers.