UI Action visible both in standard form and Project Workspace Planning section

[Salvatore B]

Hello Community,

We are experiencing an unexpected behavior related to UI Actions defined on the sys_ui_action table.

We have created a button that is intended to be visible only on the standard form view of a Project record. The button behaves correctly in the classic form interface and is displayed as expected there.

However, we have noticed that the same button is also automatically rendered inside Project Workspace, specifically within the Planning section. From a functional and design perspective, this button should not be available in that Project Workspace.

We would like to hide these buttons specifically from Project Workspace.

I would also like to mention that we have already tested the following approaches without success

• We created a record in UI Action Visibility, but the view appears to be the same in both Workspace and the standard form, so this did not help us differentiate the contexts.

• We attempted to use gs.action.getGlideURI() as a condition in the UI Action to distinguish between Workspace and the classic form. However, the URL returned is identical in both cases, making this approach ineffective

Our goal is to keep the UI Action available in the classic form while preventing it from appearing in Project Workspace.
Has anyone experienced this behavior? Do you have any suggestions on how to prevent the button from being displayed in Project Workspace?
Thank you in advance for your support

[Ankur Bawiskar]

@Salvatore B 

screenshots please.

[surajsengar]

This behavior occurs because UI Actions defined on sys_ui_action are global and render in both classic and Workspace. To hide them from Project Workspace, you’ll need to either use gs.uiContext in the condition script to detect Workspace and return false, or redesign the action in UI Builder so it only applies to classic. UI Action Visibility and URL checks won’t differentiate the contexts. Best practice is to manage actions separately: use sys_ui_action for classic forms and UI Builder actions for Workspace.

[surajsengar]

This behavior occurs because UI Actions defined on sys_ui_action are global and render in both classic and Workspace. To hide them from Project Workspace, you’ll need to either use gs.uiContext in the condition script to detect Workspace and return false or redesign the action in UI Builder so it only applies to classic. UI Action Visibility and URL checks won’t differentiate the contexts. Best practice is to manage actions separately: use sys_ui_action for classic forms and UI Builder actions for Workspace.