In some Playbook implementations, it may be necessary to remove or hide the “Skip” button from Playbook activities to enforce process compliance or avoid premature activity completion.
This article describes a clean approach to achieve this using Declarative Actions.
The solution leverages a custom record in the Declarative Action Assignment table.
Solution Summary
The approach consists of creating a Declarative Action Assignment that overrides the default Skip behavior by ensuring it never becomes available to the user.
This is achieved by:
- Targeting the correct table and action
- Forcing the condition to evaluate as
false - Ensuring execution order precedence
Key Configuration Requirements
When creating the Declarative Action Assignment, the following settings need to be done:
- Table:
Flow Data (flow_data) - Action name: Must match the Playbook activity action that starts or controls the activity execution.
- Order:
-100or-200 - Script condition with false
This guarantees that the Skip action is never displayed, regardless of user role or state.
Optionally, you can replace this with a call to a Script Include if you need more granular logic.
Important Notes About Cache
⚠️ Cache Behavior
Changes to Declarative Actions do not appear immediately in Workspace.
