Playbook tab isn't visible in SOW
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-10-2024 07:56 PM
I'm just starting my journey into PAD and playbooks and Service Operations Workspace. I've gotten to the point where I can create a process in PAD and I can see that it triggers fine and runs the first step in the process (automated ticket update) however, in SOW there is no Playbook tab being shown.
My understanding is that if the conditions are met, the Playbook tab should be shown for the user and then we can work our way through it. This should all be out of the box with no additional workspace configuration etc.
Can anyone recommend anything on where to even start looking at why this isn't working as expected? Or have I mis-understood and configuration of the workspace is required to get it working?
Thanks
- 4,219 Views

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-11-2024 03:09 AM
Hi @Craig22 ,
OOTB playbook tab is available for SOW record page. The OOTB conditions to make the tab visible are
1. record table != em_alert
2. record sys id != -1
3. plugin "com.glide.playbook_experience.config" is active
4. Screen condition specified here is met https://<your instance>/now/nav/ui/classic/params/target/sys_ux_screen_condition.do%3Fsys_id%3D7f7b1dd777a03110121e8f1a5b5a99b2%26sysparm_record_rows%3D1%26sysparm_record_scope%3D5ca1bcb3733320103e366238edf6a706%26sysparm_record_target%3Dsys_ux_screen_condition%26sysparm_record_list%3Dscreen%253D5ca31c5777c03110121e8f1a5b5a99dd%26sysparm_nostack%3Dtrue%26sysparm_record_row%3D1
If you drill down to script include(SOWDefaultRecordRouteUtil) used in above screen condition there are functions to check if playbook tab should be enabled which uses system properties "sn_sow.playbook.tables"
5. Current record must contain a playbook.
Please mark this answer as helpful and accept the solution if it solves your issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-29-2024 10:47 AM
What record type are you trying to get a playbook to show on?
I learned this the hard way, there's a system property that needs to be set for each table. OOTB it's only set for the incident table: sn_sow.playbook.tables.incident = true.
For example, if you want to see playbooks for Catalog Tasks (my use case), create a new system property: sn_sow.playbook.tables.sc_task , and set it to true.
That's it, that's all there is to it. Took me about a day digging through code to figure that out, haven't seen that documented anywhere.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-29-2024 05:53 PM - edited 04-29-2024 05:53 PM
Thanks Matt. I was looking sc_task and had the system property already added.
I did get it resolved in the end but had to essentially spin up a PDI to compare with what we had in our instance. Turns out there were some missing screen collections and ux app routes somehow. When I recreated it all, the playbook tab is now appearing correctly.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-20-2024 08:35 AM
This is really helpful. I have the same use case. I was able to enable the playbook for sc_task table on service operations workspace with this recommendation. But the same playbook does not appear on other workspaces. I need to enable the same playbook on Hardware Asset Workspace as well. Any recommendations?