Feedback: Process Conditional Branching

Ok, so I’m starting to like the new Automation flow a bit more. I was wanting to set up a number of different reports to be emailed to the user for an inventory management app, based on a few different templates. These would all be triggered by pretty much the same thing, just with slightly different values. So I figured I’d just make a single Bot, with a single Event with a generalized condition. All good there. But then for setting up the Process, Steps, and Tasks, I feel there could be some improvement here.

So here is the Step setup graph for my single Process:

These “Branch on a Condition” Steps are only for Boolean values. An “IF()”, if you will. I feel like it’d be better to allow the editor to assign their own values to match the condition expressions, instead of the “YES” and “NO” branches, as well as allowing multiple branches per Branch Step. An “IFS()”, if you will.

Looks like someone mentioned the same thing back in December but was never responded to:


Alternatively, or perhaps in addition to the above, I feel like we should be able to specify condition expressions for Processes and/or Tasks themselves. This would be more in line with how Grouped Action are currently setup. Quite often I will run a Grouped Action when an event occurs, like a Row Select, or a Form Save. This Grouped Action will have a number of other sub-Actions to run, and each of those Actions can define its own condition.

So I’d envision a single Process for the above, then instead of using any of these “Branch on a Condition” Steps, I’d just put in both of the Tasks that I have setup, in a row. Then each of these Tasks would have its own condition to determine which one should actually execute.

Thanks for listening.

1 Like

@Marc_Dillon thanks for your feedback. We are exploring case/switch style branching vs the current two node pattern as part of our longer term roadmap.

Can you elaborate a little bit more on what you mean by “condition expressions for Processes”?

2 Likes

Ignore that part, I misspoke/brain-farted. Since you can only set a single Process to a Bot, it doesn’t make any sense. I more meant setting conditions to Tasks, like I described, so that you don’t even need the conditional branching, you just set a number of Tasks in a row serially, each with it’s own condition.

1 Like

Tasks are reusable components are meant to accomplish one specific activity, eg: send an email. Flow control (eg: conditions) are intentionally kept outside of task as these allows tasks to be used across multiple processes.

2 Likes

Ok, sure, that makes sense. I’ll eagerly await the case/switch branching.

1 Like