
Not only is this quicker and easier to set up, but it leaves your programs looking neater and cleaner, and it is much easier to add later if you decide to make changes to a program to add a condition to an existing step.
Build your program as you normally would, but in the Action details for your step, you will now (or as of the coming release) see an Action Condition option. That is where you add the rule for whether the step is to be run or not.
Clicking "Add" brings up a configuration box for the condition. You have a full set of options here similar to your set of options in building a Decision Rule. You can look at data that is known

Once you decide how you want to define this condition, you have a set of configuration options, again similar to the options on Decision Rules. In our case, we're going to send Email 2 if Email 1 was not clicked on, so we select that option and choose the specific email we're looking at.

I look forward to your comments on this feature once you've had a chance to try it after the February 22nd release.
3 comments:
That could be a handy addition. Will it allow you to define multiple conditions on a step and chain them together with binary operators?
Derek, great question. It is a single condition only. If you're looking to do any chained/complex decision rules, the best bet is to continue to use decision rules to build the logic.
My apologies, this (and the wait step) did not end up making it out for the Winter release. Apologies for that. We'll have a new release date soon.
Post a Comment