Another role to be able to create and process update set
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2016 07:01 AM
Hello,
We are trying to limit the use of admin in our instances but we want to be able to allow the user to use update set to move code around. We have created a new role 'slf_update_set' to do that and modified the update set module and many acl related to updated set so that that role can update the update set table. So far the user can create, do changes and get those changes captured into an update set properly. On the other instance, we have been able to retrieve the update set properly. The problem comes when we try to preview the update set, it just spins.
We have look at this document http://wiki.servicenow.com/index.php?title=Administering_Update_Sets#gsc.tab=0 and created 'glide.ui.update_set_picker.role' property and gave it our role but that did not help.
Any advise about what change may be missing.
Thanks...Jim
- Labels:
-
Team Development

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2016 11:30 AM
HI Jimmy,
Make sure the role has permission to read sys_update_set table.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2016 12:13 PM
It does. I modified ACL for these tables to give read/write/delete/create access
sys_remote_update_set
sys_update_preview_problem
sys_update_preview_xl
sys_update_set
sys_update_set_log
sys_update_set_source (Read only)
sys_update_xml
But so far, the preview just spins and do not work unless I have admin.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-18-2016 09:51 PM
Hi Jimmy, not sure if this is helpful but let me share our experience. Our requirement was to allow very few admins to move code to production, while we wanted other core developers to move update sets across test/qa/uat instances. To achieve this we allowed developers to have admin role on non prod and create a new role on production for additional security and restrictions for code movement.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2018 08:13 AM