1

In my Sitecore 8.2u5 instance I am implementing different engagementplans and want to assign actions like sending an EXM campaign email to outcome of condition checks between states.

It seems I can only assign actions on outcome 'yes' and not on outcome 'no'. Is there a specific reason for this that I am missing, or is this something that is wrong in my configuration?

enter image description here

As you can see I have an action after condition with outcome 'yes' where I could assign an action. I cannot do this on the No outcome, and had to introduce another weird always true condition to be able to also do an action.

Other then upgrading to Sitecore 9, any other fixes around for this?

  • This is 1000% easier in Sitecore 9.0.1. – Pete Navarra Jan 20 '18 at 0:30
3

No. You can't get around it. If you actually take a look at the Engagement Plans in the Marketing Control Panel, you'll see that a condition only has one field for Next State (when true). There's none for a false condition state. So, you have to go through another condition to allow for you to add the "false" state.

Btw, for SC9, Engagement Plans have been deprecated and replaced by Marketing Automation Plans. Besides the non-Silverlight interface, it also moves away from states, conditions, and actions, although the new concepts are very similar but simplified but also more powerful and extensible. In the Marketing Automation Plans, there's a Condition that allows for connections on both the true/false.

| improve this answer | |
  • This answer is correct. Just like driving and only turning left, if you loop enough through the Yes's, you can eventually get to a No result, using Yes's. Heh. – Pete Navarra Jan 21 '18 at 0:48

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.