I am building workflows as a workaround to required columns at status changes. It’s a fairly simple process - I set the status to MISSING DATA if specific columns are empty. This is simple to do in Workflows and in Automations, however it requires a separate tree for each empty column in a workflow or a separate automation for each column in Automations.
It would save SO MUCH WORK if I could combine all empty columns into a step: “If any of the selected columns are empty” - it could have an AND/OR selection to determine if one empty is sufficient or if all empty is the trigger.
Workflows has a multibranching option that allows multiple selections but it only works for status, there are no other trigger options.
I agree with this. The Workflow builder, as a “no-code” solution, leaves people like me (and likely you), who have some actual coding knowledge, without the tried-and-true solutions for branching workflows and using combinations of and/or logic.
I’m also frustrated that each branch becomes its own workflow that requires its own end block, rather than being able to work on a condition and go back to the main branch to end with only one or two blocks at the end of the whole thing. If we were able to copy/paste action blocks and move them around, it may not be quite as frustrating to me, personally.
Yes! I think I created another feature request (or maybe upvoted another one) for allowing a branch to return to the main workflow. It makes no sense that you have to create all the separate tentacles unnecessarily!
Hello,
Interesting post!! I’m agree on the impementation of And/Or logics in workflows and automations. I also need this logic for triggers.
And I also find that coming back to the main branching let us same lots of time instead of duplicates all common remaing steps.
Agree! These current constraints lead to excess computational time and slow automations where complex!
Other commenters may be interested in upvoting the related feature request: