- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-28-2016 10:39 AM
How to disable save option in form context menu
User is not having change co-coordinator role, still he is able to save from form context menu.
Solved! Go to Solution.
- Labels:
-
Personal Developer Instance
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-29-2016 10:58 AM
There is a Global UI action for 'save' makes save option to be visible only in context menu.
A global UI action applies to every table. You can override a UI action for a specific table, in which case you must ensure that the action_name of both, the overriding UI action and the original UI action - are identical.
For example, to override a UI action on Task for just the Incident table:
- Create a UI action on the incident table with the same Action name. If the Action name is not defined, use the same Name.
- Enter a script that is specific to the Incident table.
What you need to do now is, create new UI action for change table which overrides this. You can use conditions to control UI action visibility by role. Ex: gs.hasRole('itil_problem')
For more details on overriding UI actions, visit: UI Actions - ServiceNow Wiki
Thanks,
Rafi
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-28-2016 02:58 PM
From the Navigation Bar, type UI Actions.
Under System Definition, click on UI Actions. From the List, Search for "Save". Locate the table you want the save button to be disabled. Click on that Save UI Action > and remove the Check-mark next to Active.
I hope this helps
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-28-2016 03:56 PM
Can the user Submit a form or is that disabled? About the only difference between Submit and Save is that Save keeps you on the form while Submit takes you back to the List view, in most cases. If the user doesn't see the Submit button/context menu but sees Save, then Save has to be disabled in the same place Submit is disabled for the user, which may be role based.
What Shiraz is suggesting is to remove Save for everyone.
Can you clarify your requirements?
Hope this helps.
Please feel free to connect, follow, mark helpful / answer, like, endorse.
| John Chun, PhD PMP | ![]() |
Winner of November 2016 Members' Choice Award
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-28-2016 04:07 PM
if we have to remove the save button in context menu for example for ITIL user, then how can we achieve it?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-28-2016 05:05 PM
Controlling UI Action visibility based on roles is explained in UI Actions 4.2 Controlling Visibility with Roles - ServiceNow Wiki. If you want to hide a UI Action for someone with the "itil" role (you mentioned ITIL user, but you wouldn't typically want to do this for a single user), you'd add a condition similar to
!gs.hasRole('itil')
If there are other conditions, then you'd need to make sure the combined condition would hide the UI Action for the itil role.


