0
29.3.0
Australia Patch 3, Australia Patch 1, Australia, Zurich Patch 8, Zurich Patch 7, Zurich Patch 4, Zurich Patch 2, Zurich Patch 1, Zurich, Yokohama Patch 6, Yokohama Patch 2, Yokohama Patch 1, Yokohama, Xanadu Patch 10, Xanadu Patch 7, Xanadu Patch 3, Xanadu
Standalone Application
Playbook provides fulfillers with a way to visualize business process workflows in a simple, task-oriented view. This workflow ensures consistent responses to commonly encountered situations. These business process workflows are typically designed with Process Automation Designer.
Note: The following store app is for use with playbooks that have been built using Process Automation Designer. If you are looking for information related to Security Incident Response Playbooks, see the link to Security Incident Response in the supporting links section.
Interact with a business workflow in real-time from within any configurable Workspaces within ServiceNow.
- Agents can use Playbooks to create records, update records, upload attachments, and complete tasks across multiple workflow activities.
- You can have multiple Playbooks per record to enable different user access levels to view or take actions at different levels of information across the enterprise.
- You can preview Playbook Experience in real-time while building business process workflows.
- You can have a highly customized user experience provided by the deep integration between Playbooks and other elements in the application.
Fixed
- The Playbook stage picker header hid stages at 400% browser zoom or 320px viewport width in the CSM/FSM workspace.
- A playbook activity was incorrectly marked complete when its Declarative Action UI action returned an error.
- Single-section playbook activity forms incorrectly displayed the section heading (for example, "Variables").
- Work notes entered on a playbook activity form were added to the parent record's Work Notes component after Update or Mark Complete.
- Saving an unmodified playbook activity form left the loading indicator on screen until refresh.
- The Restart Stage action did not appear on a playbook stage when its display conditions were met.
- Playbook card status action element was keyboard-focusable without a semantic role for screen reader users.
This store app is the primary activation point for Playbook Experience that includes all dependent Playbook store apps and system plugins.
Automatically installs the following Plugins:
- Playbook Experience Core (com.glide.playbook_experience.config)
- Process Automation Designer (com.glide.pad.core)
Automatically installs the following application:
- Playbook Experience Components (now_playbook_exp)