
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-02-2022 09:33 PM
Hi Community,
In my ServiceNow instance, the 'Edit' button which allows bulk update is showing for every ITSM table except Catalog Task for non-admin users. Ironically, that is the only table I actually want the bulk update functionality to allow users the action tasks in bulk.
I can't work out why the Edit button won't show for Catalog tasks. I have not made any configuration changes around list edit, but it does show for admins!
My investigations so far
- My instance has no row level acl for list edit on incident, and all roles users can bulk update on that table
- Creating list_edit ACL's on table and field level for itil on Catalog task has no effect
- There is two Edit List Actions OOB for global table but these appear to be for related lists
- Users with list_updater role still can't see the button
- I am aware that list cell edit is available from Rome
This is what admin sees:
Everyone else:
Please let me know if you know how to solve this.
Thanks in advanced 🙂
ServiceNow Nerd
ServiceNow Developer MVP 2020-2022
ServiceNow Community MVP 2019-2022
Solved! Go to Solution.
- Labels:
-
Agent Workspace

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-02-2022 11:13 PM
I remembered back many years ago when I worked out how to control security on 'Update All' in the Native UI which led me to the solution. I had a requirement to stop users from being able to edit some fields in bulk update. I worked out that SN evaluates its write ACL against a "invalid" sc_task record (just a new GlideRecord('sc_task'), which fails against my single ACL that checks the active flag.
I copied my existing ACL and removed the condition, adding the script below to ensure that it only passes for these types of checks:
// ACL specifically to allow bulk update on sc_task in Agent Workspace
answer = current.isValidRecord() == false
And presto, the Edit button is showing on Catalog Task.
ServiceNow Nerd
ServiceNow Developer MVP 2020-2022
ServiceNow Community MVP 2019-2022
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-02-2022 10:00 PM
Hi
please open /nav_to.do?uri=sys_declarative_action_assignment.do?sys_id=1a3fb85453103300099addeeff7b1259%26sysparm_view=advanced
This is the related Action Assignment which creates the "Edit" button. Then check:
- at the "Conditions" section whether there are any restrictions which could explain the behavior
- in the "Action Exclusions" Releated List whether any exclusions have been configured which could explain the behavior
Kind regards
Maik

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-02-2022 10:24 PM
Hey,
Thanks for your response. I did see your blog about getting this functionality to work for related lists.
I have already looked at this one, but I did miss the "!" at the start of the condition and dismissed it as belonging to 'many to many' tables.
When I run the code below, it returns true.
!(new global.ManyToManyChecker().isManyToMany("sc_task"))
I'll note that I have made no modifications to this record from OOB. It contains no Action Exclusion.
As an admin, I can see edit. There is nothing in this configuration that would suggest it should be hidden to all non-admins.
ServiceNow Nerd
ServiceNow Developer MVP 2020-2022
ServiceNow Community MVP 2019-2022

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-02-2022 10:41 PM
I even tried creating a custom one, just for Catalog Task.
No conditions, no roles.
It only shows for admin
...
ServiceNow Nerd
ServiceNow Developer MVP 2020-2022
ServiceNow Community MVP 2019-2022

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-02-2022 11:13 PM
I remembered back many years ago when I worked out how to control security on 'Update All' in the Native UI which led me to the solution. I had a requirement to stop users from being able to edit some fields in bulk update. I worked out that SN evaluates its write ACL against a "invalid" sc_task record (just a new GlideRecord('sc_task'), which fails against my single ACL that checks the active flag.
I copied my existing ACL and removed the condition, adding the script below to ensure that it only passes for these types of checks:
// ACL specifically to allow bulk update on sc_task in Agent Workspace
answer = current.isValidRecord() == false
And presto, the Edit button is showing on Catalog Task.
ServiceNow Nerd
ServiceNow Developer MVP 2020-2022
ServiceNow Community MVP 2019-2022