Declarative List Actions do not handle conditions

Rob Joy
Tera Expert

‎01-03-2024 08:57 AM

I am building a solution and, I would like buttons to only show on a list if ALL of the selected items can run the button.

RobJoy_0-1704301000255.png

 

 

You would think this would be a simple, check the right boxes, use the same rule that correctly shows and hides the button in a form and, the list would show and hide the button based on all items selected.

 

I have tried all of the options in the Action Assignment for list.

I can get the button to always show or not show at all, but I cannot get any condition applied to show the button.  If I define ANY condition ,with or without the “Experience Restricted” button checked, I get the same results.

 

I have tried:

  • Using the same script condition that works on the form.
  • Using “Requires read access”
  • Adding the Record conditions in the script condition used in the form

If I add ANY condition, the button never shows at the top of the list.

RobJoy_1-1704301000266.png

 

0 Helpfuls
  • 5,600 Views
10 REPLIES 10

Henalu
Tera Contributor

3 weeks ago

This one is a real headache. The short answer is that Dynamic Evaluation is broken in custom workspaces — it works in OOB workspaces like CSM or ITSM but silently does nothing in workspaces you create yourself. And enabling Experience Restricted often makes the action disappear entirely instead of just hiding it conditionally.

 

The workaround that actually works is moving your condition logic into the Server Script of the action itself, returning early if the condition isn't met, rather than relying on the Condition or Dynamic Evaluation fields.

 

I wrote a detailed breakdown of why this happens and how to work around it (in Spanish, Google Translate works well): https://breaking-trail.vercel.app/articulos/workspaces/declarative-actions-experience-restricted-dyn...

0 Helpfuls