How to Hide the Out-of-the-Box Save Button in the Source-to-Pay Workspace Based on State?

[hamatu]

We are investigating whether it is possible to hide the standard Save button (OOTB Save button) in the Source-to-Pay workspace based on the record’s status.

The requirements we wish to implement are as follows.

Table: sn_slm_case

Condition: Status = Work in progress

Requirement: We want to show or hide the out-of-the-box Save button on the form based on the status.

Premise: UI Actions must not be used.

We investigated and verified the following:

UI Policy

Client Script

UI Builder

Action Visibility

Declarative Action

In UI Builder, we checked the Record Page Tabs component and found the save button but changing the setting of save button took me a UI action page.

At this point, it seems possible to achieve this through DOM manipulation using UX Client Script; however, considering the impact on updates and maintainability, I would prefer to implement this using standard methods if possible.

If anyone has any information regarding the following, I would appreciate your guidance.

Is there a standard method Without using UI action for hiding the out-of-the-box “Save” button in the Source-to-Pay workspace based on the current state? 

Is it possible that I’ve overlooked a setting in Action Visibility or the UI Builder?

If there are any recommended approaches other than DOM manipulation, I would appreciate your advice.

Thank you in advance.

[Tejas Adhalrao · Accepted solution]

hi @hamatu ,

Yes, I would first check the OOTB Save action from the Action/Declarative Action configuration rather than using DOM manipulation.

Go to the Workspace configuration and identify the Save action used by the Record Page Tabs component. From there, check the Action Assignment / visibility condition and see if you can add a condition based on the sn_slm_case status.

If the action supports a condition such as Status is not Work in progress, you can hide the Save button when the record is in Work in progress without using a UI Action or DOM manipulation.

If that condition is not available for the OOTB Save action, then the next step would be to check whether the action can be extended/configured in your ServiceNow release.

If this helps, please mark it as Helpful and accept the solution.
Regards,
Tejas