- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
We are trying to add a button similar to "Skip" to the Playbook, such as "Continue" or "Complete".
I was able to locate the existing Skip button. However, when I used Insert and Stay, the record remained read-only, so I wasn't able to use that approach.
As a workaround, I manually created a new button, but it is not appearing on the form (see attached screenshot).
I have watched several videos and reviewed multiple documents, but I have not been able to determine what I am missing.
Has anyone implemented (Custom or OOB) a similar Playbook action before or can provide some guidance on how to make the button visible and functional?
Thanks,
G
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Hello @GB14
Thanks for the screenshots, they helped. Your checklist was the key. I added a Checklist Task to my test playbook and got exactly what you’re seeing: my button showed on the Instruction card but not on the checklist card.
The Reason is : checklist cards are backed by a Private Task record (vtb_task), not Flow Data. Your “Continue” action has Table = Flow Data [sys_flow_data], so it never matches a checklist card. My earlier test only used an Instruction card, which is Flow Data, so I missed this. Sorry about that.
What worked for checklist cards (it’s how the OOB skip_activity is set up):
- Create a new action with the same settings as before, but:
- Table: Global [global]
- Client Conditions: Activity State is In Progress (instead of a Record Condition)
- In the playbook experience’s Action Mapping, add a row for it with Activity Definition = Checklist Task
- Refresh the workspace
With that, the button showed on my checklist card, the click ran, and it hid once the step was skipped.
Your other question: I added the Instructional activity from the Add activity picker by searching “Instruction”. If you don’t see it, try ticking “Include all automation assets” at the bottom of the picker.
One Important note: I only tested the click with a log line. I haven’t checked what record the server script gets when Table = Global, so for real Continue/Complete logic you may need to look up the task yourself. The OOB Skip uses a Client Action instead, which may be the easier route.
[Screenshot1: checklist card with the new button]
[Screenshot2: skipped checklist card, button hidden]
Please mark Helpful / Accept as Solution if this works for you.
Regards,
Raghavendra G
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a week ago
UPDATE:
I used the out-of-the-box "Complete Activity" client action, and it successfully completes both the PTSK and the checklist activity in the SIR Workspace.
However, I am still running into one issue. Looks like by default, the Playbook requires users to either Skip the activity or check all checklist items before they can continue to the next step.
In our use case, the analyst may not need to complete every checklist item before moving forward. We would like to allow them to select Continue and proceed to the next checklist/activity without having to check all the boxes.
Completed using the Continue button
Next activity is not available until ALL previous activies are checked off
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Tuesday
Thank you again for your guidance. I was able to successfully meet our requirements with your support. Your assistance helped me get the custom button displayed, and from there I was able to work through the remaining pieces of the solution.
Since our process uses checklists, I needed a way to advance the Playbook to the next stage when the custom button was selected. I discovered that the checklist generates records in the checklist_item table behind the scenes. Using that relationship, I created a server-side script for the button to automatically complete the related checklist items and advance the Playbook.
I also created a Business Rule that establishes the relationship between the checklist task and SIR task, allowing me to populate the appropriate fields and maintain the association throughout the Playbook process.
Thanks again for your guidance and support. It pointed me in the right direction and helped me arrive at a solution that meets our requirements.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Tuesday
Glad to hear that!! Happy to help 😊