If/Then Branches in Workflows Based on Property Value

[LaurenWittschen]

Hello!

I am creating a workflow that has branches based on the value of a property with multiple selections. 

Am I correct in assuming the workflow will enroll contacts in multiple actions for multiple property values? 

Say someone selects Virtual Session #1 and Virtual Session #2 - will they be enrolled into all of the actions that follow for each value? These actions will be logistics emails, sent the day before each of these sessions - I'm wanting to make sure someone who signs up for multiple sessions will receive each logistics email. 

I don't see anything indicating otherwise...but wanting to confirm! Thank you in advance! 

[karstenkoehler · Accepted solution]

Hi @LaurenWittschen,

Records will always go down the first branch they meet the criteria of. Even if they meet multiple branches' criteria, they'll go down the first one. A record will never go down multiple branches.

If that's the behavior you're looking for you have two options:

• Create one workflow per current branch
• Nest branches (check for first option, if it is met, execute your desired action, then jump to next branch, if it is not met, jump to next branch immediately)

Also keep in mind that value-equals branches don't work well for multiple checkboxes properties. If a contact checks multiple boxes, none of the branch criteria check as true. You would have to use an And/or branch – or (my recommendation) separate workflows.

Let me know if you have any follow-up questions!

[LaurenWittschen]

This makes sense - thank you!

[Jnix284]

@LaurenWittschen Happy to help clarify the logic of if/then branches, unfortunately your assumption is not correct - if someone selects Virtual Session #1 and Virtual Session #2, they would flow through the branch for Virtual Session #1, and unless you have an action that takes them back to check for Virtual Session #2, it would stop after that branch's actions are complete.

Essentially, the workflow will check the contact against the property value in order, once the value is a match, that is where the contact will flow through the workflow.

You can add an action to go back and check for subsequent values, but that's not automatic. Imagine the contact flowing through the workflow from top to bottom like a rafter on a river, once they've progressed down a branch, there's nothing that can take them upstream again unless you make a path for that.

[DSurman]

Super helpful, Jennifer - what is the action that would ask the workflow to go back and check for subsequent values?

[LaurenWittschen]

Hi @DSurman ! I have found a workaround that fits our needs - Use the "Go to Action" to redirect the workflow to check for an additional value(s) when the condition is not met for the first value. 

So basically, you have to nest the branches using the AND/OR feature like Karsten mentions above. Typing out the logic is a little weird and I'm not sure if it will be helpful, but it moves like this:

If RSVP is Session 1, add to webinar (or whatever your action is), then create a nesting branch to move on to check if RSVP is Session 2. If RSVP does not match Session 1 (the "none met" condition), select "Go to Action" and direct the workflow to jump into the nested branch to check the RSVP for Session 2, and so on and so on. 🙂 

[DSurman]

Ahhh, I've got it. Thank you!

[LaurenWittschen]

Thank you so much!

[modgilaapk51]

i am also thankful for this.

[Jnix284]

you're welcome @modgilaapk51, I'm glad it was helpful for you as well!