- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-12-2023 10:16 AM
As the title says, my condition for visibility for a UI Action doesn't apply in Workspace despite applying outside Workspace. Do I put the condition in Workspace Client Script?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-25-2023 08:48 AM
@Dharaneetharan @Manmohan K yes I have found the solution
The solution is, the condition for workspace UI actions isn't toggled from the UI Action record
Instead, it is toggled from a record on the Action Assignment [sys_declarative_action_assignment] table
Within the record, you must click Advanced view in the related links, and you may have to configure the layout to show the 'Script Condition' field under the Conditions tab
Only here could I control visibility of UI actions in Workspace
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
The condition field on the UI Action record is evaluated in classic UI, but in Workspace the platform ignores it and defers to sys_declarative_action_assignment instead — which follows different rules entirely.
This is especially tricky with Experience Restricted: enabling it changes the scoping behavior and can cause the action to not appear at all in custom workspaces. The most reliable fix is to put your condition logic inside the Server Script and let it control visibility from there.
I documented the full behavior and the workaround here (in Spanish, Google Translate handles it well): https://breaking-trail.vercel.app/articulos/workspaces/declarative-actions-experience-restricted-dyn...
