UI actions in workspace disappeared after upgrade from washingtondc to Yokohama
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-06-2025 05:57 PM
We have many custom applications under CSM and we have 3 workspaces too. Few applications use CSM configurable workspace, but 2 apps for example "App1" use "App1 workspace" and "App2" uses "App2 workspace". When instance got upgraded to Yokohama the UI actions in "App1 workspace" and "App2 workspace" replaced with new set of buttons and they are not functioning. While searching community found a solution that create a record in the "sys_ux_form_action_layout" table for the corresponding tables of App1 and App2. When I created the records a set of UI action came back to the workspace but it functions differently than the one present in washingtondc version. For example please see the below image, when clicked on "Compose Email" button the below appears:
why the buttons are different in two versions? Where can i find the configurations for these buttons?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-06-2025 08:55 PM
I believe you will have to debug this from your side as this is a customization and ServiceNow won't help much even after raising a case.
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-10-2025 12:04 PM
I'm experiencing the same issue — after the upgrade, my custom button no longer appears in the Workspace. However, it still functions correctly in the Classic view.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-10-2025 03:22 PM
I was able to resolve the issue by deactivating Front-line Case Actions in the sys_ux_form_action_layout table. It was causing conflicts with the UI Actions in my case