Rule Action Ordering - sort ranking by number, not string

I strongly agree with this suggestion! It’s a bit confusing to see the actions out of order even though they’ll run in the correct order.

I am not against this idea.

But man, what rules are you building that requires 10 different actions beyond a history rule?

Since you are building all those actions offer the same soure and they are all the exact same action type you should be able to collapse that down to one with using case statements and pre-filtering.

Just an FYI, the longest parts of rules are typically because of the actions. Even if you are filtering down in the action setup. Those action still have to look at every record to determine to process or not.

Thanks for the insight @Wayne, and agreed this specific rule would benefit from case statements! UI still isn’t logical though..

@Wayne The few rules where we have 10 or more actions are mostly for onboarding CTAs where each CTA name and playbook is different for each action, which is why we have so many.

Makes sense if you are using different playbooks. This should be an enhancement, as it’d cut down on so many different actions. Man I wonder if creating via API is quicker for this since you’d only need one call instead of all these actions.

But, even the CTA name can be done prior and case statement and then tokenize that case statement into your action.

I’d also debate that it might even be better to split out the filtering the action is doing into multiple transforms. So that 1 record isn’t having to be checked against X number of actions.

@Wayne Great points!

This created a confusion among us and it would be great if it is fixed in UI