- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-02-2026 11:12 AM
Hello everyone,
I’m currently working with a playbook, and I have a requirement for the Show List of Records activity.
In this activity, the Mark Complete button, for example, should only be visible after an email is received back into the instance through an inbound email action. The goal is to prevent the user from moving forward before the process is actually allowed to continue.
Do you know if it’s possible to show or hide the standard buttons from the Show List of Records activity based on a condition?
I tried duplicating the activity and duplicating the buttons. However, whenever I change the table from Global to another custom table within a scoped application, so that I can set a specific visibility condition for the button, the button is no longer visible.
Thanks in advance,
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-02-2026 07:35 PM
I got it working by using a script condition. I had already tried using current, but it didn’t work since it always returned null
What worked for me was using parent instead, like this: parent.getValue('field_name')
I couldn’t find any official docs about this, but I think it works because the playbook activity is embedded in the workspace, so the parent record is available in that context
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-02-2026 11:30 AM
hi @ftiezzi
Check if these links helps:
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-02-2026 07:38 PM
Hi,
Thanks for your input
I took a look at those links, but I think the scenarios there were a bit different from what I had, since my condition needed to be dynamic
I was able to solve it by using parent to get the values from the record, as I mentioned in the comment I added
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-02-2026 07:35 PM
I got it working by using a script condition. I had already tried using current, but it didn’t work since it always returned null
What worked for me was using parent instead, like this: parent.getValue('field_name')
I couldn’t find any official docs about this, but I think it works because the playbook activity is embedded in the workspace, so the parent record is available in that context