Multi-step workflow vs. Conditional paths

I have a workflow that I want to build that does not stop at the first conditional block it comes to that is true.

So for instance, I need to send out an email to various markets once a task is done. So if a task has been done for AU, NZ and IN, I need three separate emails to go out to each market (this information is being pull from the "Market" column). If I use conditional paths, it appears that the flow stops once the first true condition has been met - for instance if I state "send this email if AU is in the market column" it will not go to the next conditional path to see if that condition is true too for NZ or IN.

I set up a multi-step workflow (by which I mean vertically instead of horizontally in the automation) instead of a conditional path, but again it appears that it stops at the first condition and doesn't continue down the list to see the other emails that need to be sent.

Other than setting up a separate work flow for every market, is there a way to get automation to check all of the conditions and process those that are true?

TIA

Sasha

Find more posts tagged with

Workflows in Smartsheet

Accepted answers

Genevieve P.

Hi @Nesasha L

Condition Block pathways (horizontally) will stop as soon as it finds one path that is "true", as you've found. (See: Condition Blocks: Filter What Your Automated Workflows Send).

The vertical way should continue down all actions specified, but in this instance it will stop as soon as there's a blocker where the condition is not true. This stops the workflow at that point, it can't skip over that Condition since it's in the vertical path.

The way I would achieve what you're looking to do is to set up separate workflows, as you noted... one for each separate alert you'd like to send out. This will also be more manageable down the line as you add/remove markets: you can simply Clone a workflow and adjust the criteria, or delete a single workflow without editing a complex build.

Cheers,

Genevieve

All comments

Genevieve P.

Hi @Nesasha L

Condition Block pathways (horizontally) will stop as soon as it finds one path that is "true", as you've found. (See: Condition Blocks: Filter What Your Automated Workflows Send).

Cheers,

Genevieve

Kevin1158

I understand that this is how it works(now), but this is not intuitive. It is also not helpful that the 'circuit' that the user interface generates when you set up conditional paths looks like a parallel circuit. In electrical terms, and logical terms, the layout drawing generated implies that each conditional path runs at the same time, not in series. If you wanted to make the interface more intuitive, you should change the visual aids/lines in the layout to be more accurate.

Also, why wouldn't you be able to generate a parallel path option in your workflows. MANY of us have asked for that functionality rather than write duplicative workflows. I'm currently up to ~ 50 workflows in one of my sheets for what could be done in 7-8 if I didn't have to duplicate my work.

Davinci

Hi @Nesasha L @Kevin1158

This is an old post, not sure if anyone sorted it. The trick for multiple conditions is in the trigger. Your trigger should be when cell value change AA OR NZ OR IN. Then your first condition will be where Market is AU, next conditional path where market is NZ next where market is IN. This way the trigger will search for the condition and will execute that condition.

Cheers

Ryan Catling

@Davinci That does not work, it will stop at the first trigger that is met and not continue searching the other triggers. Unfortunately it seems Smartsheet has not fixed this bug yet.

I agree with Kevin, it's highly unusual Smartsheet has not fixed such an obvious issue.

Sign in to join the conversation!

Quick Links

Component react.discussion.discussions had an error.

ref must be one of: categoryID, siteSectionID, category, category/categoryID, category/name, category/description, category/url, category/allowedDiscussionTypes, locale, siteSection, siteSection/basePath, siteSection/contentLocale, siteSection/sectionGroup, siteSection/sectionID, siteSection/name, siteSection/description, siteSection/apps, siteSection/attributes, layoutViewType, discussionID, commentID, page, sort, discussion, discussion/name, tags, breadcrumbs, discussionApiParams, serverDraftID, serverDraft.