Save button on Incident form disappeared

[Pooja P]

Hi Team,

We observed that SAVE button on incident form is disappeared , we have checked UI action there is no recent update on Global / incident table level UI action available for SAVE button.

even checked system property "glide.ui.advanced' also not true but eve though ity was false it was working until last week.

Anyone faced issue and what could be possible solution ?

[Me Being Mustaq]

Hi @Pooja P ,

The issue of the Save button disappearing on the Incident form despite no recent changes to UI Actions or the "glide.ui.advanced" system property can have several root causes. Here are the key troubleshooting steps and possible solutions:

Potential Causes & Fixes

1. UI Action Visibility Conditions

   • Check the Condition and Script fields of the Save UI Action(s) on the Incident table.

   • Sometimes a small logic change or field value (e.g., state of the incident) may cause the button not to show.

   • Validate if the UI action condition is evaluating to false unexpectedly for your user/context.

2. Client Scripts or UI Policies

   • Look for any recent or scheduled client scripts or UI policies that might disable or hide the Save button.

   • Particularly check for any scripts that manipulate buttons based on form state or user roles.

3. Form Layout or Sections

   • Sometimes form layout changes or section collapses hide buttons visually.

   • Reset the form layout or test on a different form version or browser.

4. System Property Caching

   • Though glide.ui.advanced set to false usually forces the classic UI, system properties cache refresh may be required.

   • Try clearing cache or flushing the browser cache to force reload.

5. UI Builder or Workspace Context

   • If you recently switched to a workspace UI or UI Builder environment from classic UI, controls like Save buttons are rendered differently.

   • Check if you are using a workspace where Save is replaced by other mechanisms or buttons.

6. Browser or Extension Issues

   • Try accessing the form on another browser or clean session to rule out local browser issues.

   • Disable extensions that might interfere with form rendering.

7. Known ServiceNow Issues or Patches

   • Check ServiceNow community/forums or your instance release notes for known issues in the latest platform patches affecting form controls.​

Immediate Workaround

• You can add a temporary UI action or a button on the form with a script like:

action.setRedirectURL(current);
current.update();

• This simulates save functionality until root cause is identified.

If it is helpful, please hit the thumbs button please mark the answer as correct based on the impact!!

Kind Regards,

Shaik Mohammed Mustaq

[Ankur Bawiskar]

@Pooja P 

was it working fine earlier?

SAVE button is not visible for other tables also or only this table?

Did you recently upgrade?

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[Pooja P]

Hi @Ankur Bawiskar we recently upgraded our instance to Yokohama (22nd Oct) but we have observed after upgrade also SAVE button was visible on incident form , but not now.

Yes it is visible on other forms for example Problem form we can see Save button.

Thanks,

Pooja

[Ankur Bawiskar]

@Pooja P 

then did you check if someone created a new SAVE button on incident form and inactivated that?

Did you check the OOTB UI action if someone added some condition in it?

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏