Name action at "criteria" even if there is no criteria

That is a pain, the whole Criteria as another step has some very weird side effects too.

If you have several actions with no criteria, you can’t name the criteria, and they all have the same default criteria name, which means your actions get lumped together. If you want to edit or change the criteria for one action later, you would have to change it for all of those actions, or delete the action and create a new step and re-do that rule action. :/

Hi,

Wanted to confirm the problem again @andreammelde since I do not believe we ever had the capability of Naming actions - Are you looking at the ability to name criteria when there are no filters? 

@bradley acknowledge this problem. Will look more into this.

@rakesh you have always been able to “name” an action by adding a description. With the change, you can only add a description if you have a criteria. Before, the description, mapping, and criteria was all in one step so you always could “name” an action.

Regardless if you could or couldn’t, this is a major miss in the design. We run multiple action off of one rule to be more efficient, yet we cannot tell what we are running? I should always be able to provide a description regardless of if there is a criteria or not.

Got it.

You can still add a description in the action

and it will be visible on hover

@rakesh but then I have hover over the action to see what is happening… This is a bad user experience. It should be clear at a glance, not another click or hover, what is happening. Especially something so important as an action. What if I had multiple “Update SFDC Object” with no criteria but to different objects? I then have to hover to see which is which??

Converted this Horizon Rules Beta feedback into an Idea.

Agreed with all of the above.

Chiming in - I was just about to create my own idea post for this so glad to see it’s already been created.

We need to be able to give a name to a branch that has no criteria because this was still possible in Bionic rules. We need to be able to see the name of that branch from the view design/view actions canvas, without needing to click into the action to see the description.