Checklist Won't Show on Playbook | Process Automation Designer (PAD)/Playbook/Workspace Experience

JamieNow
Tera Contributor

Thanks for helping with this!

 

I imported an update set with a playbook I created through PAD from a depreciated instance, but the playbook isn't working correctly. Notably, I recreated the table I used in the old instance using the same name except I extended it from the Task table. I'm not sure if that has anything to do with this potential bug. All configurations are the same in PAD, but I did create a custom Workspace from scratch using UI Builder (UIB) this go-round.

 

Further, I posted a question to the community yesterday about another issue I came across where the UI action for viewing a knowledge article isn't working when clicked on. Here's a link to that post in case it helps with context: Re: Knowledge Articles Aren't Opening in Playbook ... - ServiceNow Community

 

Everything seems broken and I can't really compare to other workspaces since their page definitions are protected and the properties aren't copied when I create variants or an override.

 

Here's screenshots of the properties for the PAD activity that isn't working:

JamieNow_1-1704819865750.pngJamieNow_2-1704819892314.pngJamieNow_3-1704819941533.png

I greatly appreciate the help! I've tried everything and read all the product documentation.

1 ACCEPTED SOLUTION

Ean Grieve
ServiceNow Employee
ServiceNow Employee

This might work...

In your configuration of the activity make sure you populate populate the Task field with a task record that your user has read and write access to - such as the task that the playbook is running against.

 

The access to the checklist is driven by the task that the checklist is associated with.

 

If you don't specify a task it will create and associate the checklist to a private task (PTASK) that your user may or may not have access to.

EanGrieve_1-1743674183841.png

 

 

 

View solution in original post

1 REPLY 1

Ean Grieve
ServiceNow Employee
ServiceNow Employee

This might work...

In your configuration of the activity make sure you populate populate the Task field with a task record that your user has read and write access to - such as the task that the playbook is running against.

 

The access to the checklist is driven by the task that the checklist is associated with.

 

If you don't specify a task it will create and associate the checklist to a private task (PTASK) that your user may or may not have access to.

EanGrieve_1-1743674183841.png