Disable inherited UI action from Application Creator

[llarmeu]

I created an application with the Fuji application creator. It created a request and task structure. I was later asked to remove access to the task portion and only leave the main request portion. I hid the links in the nav to the tasks and removed the related lists. The only thing left that points to the Tasks is a UI Action under Related Links called "Add Task." It is inherited from the sm_order table and it is protected/read only. I can't figure out how to make it go away. Obviously, I want to do it in a way that it won't affect the sm_order table or any future applications created.

Any help is appreciated!

[llarmeu]

I know I cannot modify that code. Is there some other way I can hide it or supersede it?

[Pradeep Sharma]

Hi Larry,

You can have a client script on that table to hide the button. Please go through the below link for more info.

http://www.servicenowguru.com/scripting/client-scripts-scripting/removing-form-buttons/

[Tanaji Patil]

Hi Lary,

The simplest way in my opinion is to create a UI action with same name, same order and same script but on the table where you wanna hide and with and added condition "&& 'false'" or "&& current.number.nil()" . "current.number.nil()" added condition says "display this button if you have nothing in the number field" which will evaluate to false.

Exception: if you assign numbers after the record is created, in which case, change the condition to !current.number.nil().

Please check this excellent blog by Chuck Tomasi.

UI Action Overrides

Hope this will help you.

Thanks,

Tanaji

[llarmeu]

I tried this, and also looked into the client script, but as you can see from the screenshot above the OOB UI Action appears to have no action name. I think this is causing it to not work. Before I had posted this I duplicated the UI Action and set it to my custom table and set it to inactive, that didn't work. I just tried adding the false and nil conditions, neither worked. If I leave it as is, it creates a second Add Task UI Action, so I know it is working, it's just not overriding the sm_order one.

[llarmeu · Accepted solution]

I ended up opening a HI ticket for this. My guess was correct - the issue was that the OOB UI Action did not have an action name. The ServiceNow SE modified the OOB action and added a name, which I matched on the created table, and the UI action hid. Thanks for guiding me towards the answer!