Logic on grouped action conditions

What is the logic for grouped actions with a condition plus individual conditions in the referenced actions?

It used to be that if the condition for the grouped action itself was true, it would then run and evaluate on the go the conditions for each individual actions.

But now I have a grouped action that is not showing when any of the individual refrenced actions conditions is false. Does it depends on something or is there a new logic implemented

If you are referring to an “action button” that is not showing in your app views, it is likely due to other reasons and NOT that actions inside the group have a “false” Behavior condition. However, I don’t think I have ever encountered a scenario where ALL child actions in the group are false!!

Please show more details of your use case so we can help further.

1 Like

Thanks for the reply

In my scenario I have a grouped action which has its own condition and it has 2 child actions.

If the parent action condition is true but any of the two child action’s condition returns false, the action button will disappear. But if all 3 remain true the action button appears again.

This is the first time I have encountered this, it usually just skips that specific action returning a false value. I don’t know if it has something to do with the specific conditions. Or if (I hope not) it is an update.

action.gif

Interesting! I’ve never noticed that, but I’ve also never looked for it. It’s also possible it’s a recent change.

1 Like

I really hope it is not since I have tons of for loop actions depending on this behavior.

This was a dumb mistake on my side. The child action causing the trouble was deactivating the parent grouped action button, not because of the condition but because it was a “edit this row” action type and I didn’t realize that the slice was not allowing updates.

1 Like

It happens to all of us! Good catch!

1 Like