How to Hide the OOB UI Actions in Custom Table Form in ServiceNow? Ex: Submit, Save, Delete, Update

[Rajkumarsamakar]

How to Hide the OOB UI Actions in Custom Table Form in ServiceNow? Ex: Submit, Save, Delete, Update

Hello everyone,

I created an application in ServiceNow where users provide input and receive responses by clicking on a custom UI action called "Get Response." However, users can also see standard UI actions like Submit, Save, Update, and Delete, which come by default.

I want to limit or hide these standard UI actions so that users can only interact with my custom "Get Response" UI action. Importantly, this should not affect the functionality of the standard UI actions; they just need to be hidden when the page loads.

How can I achieve this in ServiceNow on the form of my custom table? Your guidance would be appreciated.

[Dr Atul G- LNG]

Hi @Rajkumarsamakar 

what is the need to hide the OOTB UI Action 

Like Save / Update 

You can check in UI action, instead of deletion these UI action, better to hide for all users and available for Admin. 

[Rajkumarsamakar]

Hi @LearnNGrow-Atul

Thanks for your Response. 
In our ServiceNow application, we've implemented a user-centric approach where users can interact with the system by providing input and receiving results via a custom UI action named 'Get Response.' However, we have a specific requirement: we don't want users to submit records; instead, we aim to present them with the outcome directly on the form based on their choices. Our objective is to offer a seamless and controlled user experience focused on result visibility, without allowing traditional record submission.

Thanks & Regards
LinkedIn: https://www.linkedin.com/in/rajkumarsamakari

[Dr Atul G- LNG]

Hi @Rajkumarsamakar 

These buttons visibity defined in UI Properties. 

but if we disable this it will impact every where in SN.  

[Jim Coyne]

It is easy to override a UI Action.  Here's a SN Docs article that explains how to do it: Override a UI action for an extended table.

HOWEVER, if you want to remove a UI Action, I would NOT follow their example as it would create a Skipped Record during every update/upgrade/patch which you would have to deal with.  Not a great idea to create extra work for your development/admin teams.

To remove a UI Action from a specific table, create a new one with the same "Action name" on the specific table, make sure it is "Active", "Form button" is true/selected and set the condition to '"day" == "night"' or something that would never evaluate to "true":

Using the same "Action name" will override any others higher in the table hierarchy and the condition ensures it would never appear.  The "Show insert", "Show update" and "Client" checkboxes should not be selected.  They are basically ignored, but just to avoid confusion for others looking at the UI Actions.  Make sure the "Onclick" and "Script" fields are empty as well, again, to avoid confusion as they will never run.  The 5 records above removed all the UI Actions from my custom table, but you may have to create others based on your specific configuration.  Again, one for each "Action name".  Make sure you leave a nice description in the "Comments" field.

You could use the "Overrides" field, BUT that means you need to create one for EACH of the UI Actions, both current and future ones.  My 5 UI Actions in the screenshot above removes 15 OOTB ones and would keep new ones with the same "Action name" from appearing.

With all that being said, I'm thinking a UI Page/Portal Page or Catalog Item might better serve your purpose as you are overriding basic SN functionality.  But that's a discussion for another day.