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 1, Yokohama, Xanadu Patch 10, Xanadu Patch 7, Xanadu Patch 3, Xanadu
Standalone Application
The primary components are now-playbook-experience (for legacy Workspaces) and now-playbook-experience-connected (for UI Builder and Configurable Workspaces). Both components take in a parent-table and parent-sys-id of a parent record containing running playbooks. The component displays all playbooks for the given parent record.
This plugin includes the component used in UI Builder and legacy workspace:
- The Playbook Experience component can be embedded within any workspace including configurable workspaces, and within any page built with UI Builder
- Choose between Stacked and Focused activity view
- Toggle Compact Mode for narrow viewports such as mobile-friendly pages or sidebars
- Connect Playbook Experience events to any UI Builder functionality
- Expand a specific playbook, stage, and activity using properties in UI Builder
- Connect UX Declarative Actions using UI Builder
- Provide pre-filled fields to use in Record Generator with UI Builder
- Includes custom activity renderers for displaying instructions, forms, checklists, knowledge articles, and lists
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.
The Playbook Experience Components application is automatically installed when the following application is activated:
- Playbook Experience (sn_playbook_exp)