12
"Scope by" an event property in Workflows
complete
Rory Colsell
When configuring a workflow, add the ability to select an event property to scope all event logic by. This can be used to make sure the customer only receives messages that relate to a specific item or action, rather than different occurrences of the same event.
Note this was previously supported in our "Behavioural" and "Transactional" campaign types.
Activity
Newest
Oldest
Rory Colsell
complete
Good news everyone, this feature is now live and ready to use on all accounts.
You can find the scope feature in the advanced settings portion of the side panel on any workflow (as shown in the screenshot below).
When you add a scope property on a workflow, every filter and branch node is scoped by the same event property, meaning you don’t need to add the scope to each node individually.
For those of you who are not already familiar with how scoping works, head over to our help doc on scoping by event property: https://help.getvero.com/articles/using-advanced-scope-conditions-by.html
Thanks again to everyone who voted on this feature!
@Rory Colsell: Awesome news guys! Been waiting for this one. Much appreciated
Rory Colsell
in progress
Rory Colsell
Hey everyone, I have a question for everyone who needs this feature before we get started building this into Workflows.
- 1. Do you expect the 'scope by' option to be available on each filter/branch node?
- 2. OR would you expect an option at the workflow level (meaning the 'scope by' option would apply to all filter and branch nodes in the workflow)?
Option 1 offers the most flexibility but could make it harder to setup a complex campaign, and potentially makes it easier to make mistakes.
Option 2 makes it easier to setup but would not offer the same granular control.
What do you think? Would love to hear your thoughts. Thanks!
Felix Plitzko
@Rory Colsell: I think a great first step would be to scope this on workflow level (option 2) to make it compatible with the old transactional/behavioural campaign types (hence allowing us to migrate to workflows completely).
Rory Colsell
@Felix Plitzko: Thanks for this! Our initial thoughts are the same but wanted to check its not a deal breaker if we prioritise option 2 before option 1. If you have any scenarios where option 1 would be useful, keen to hear about them.
Felix Plitzko
@Rory Colsell: right now I can't think of any. most likely will when option 2 will be available and think of new ways this can be incorporated (😈) Anyways, imho opt 2 is definitely a great addon because it fixes incompatibility to the old way.
G
Gabriel Moreira
@Rory Colsell: Option 2 for us as well - can't think of a use case yet where we'd need Option 1.
Rory Colsell
@Gabriel Moreira: Thanks for letting us know! 👍
Rory Colsell
planned
M
Matt Reilly
@Rory Colsell: praise the lord 🙌
M
Matt Reilly
This is critical. Series are often insufficient.
S
Saphira Howell
This would be a game changer for us!
Felix Plitzko
we use this frequently and would need this in workflows!
Derek Clapham
This feature is pretty much CRITICAL for us. +1
Rory Colsell
under review