You know how annoying it is to have a massive rule with a lot of “ands” or a lot of “ors” for the same condition (e.g. state is Georgia, Florida, or North Carolina)? That used to be three separate lines in the rules builder. No more! Now you can simply separate those values with a semicolon (much like you would do in salesforce.com) and do it all on one line. This should save a lot of clicking and keep your rules a lot less tall! You can now use this in automation rules, dynamic lists, and segmentation rules.

Semicolon Separated Values

 

 

 

Note: The text field is still limited to 255 characters currently so you couldn’t put a massive list in there (the Fortune 500 for example). You would have to split that into a few lines. This should cover most cases though.

Adam Blitzer

Posts Google+

19 responses to Automation, Segmentation, and Dynamic Lists: add many rule conditions in one line

  1. Great change! Will save a lot of time when building rules

  2. YES! This is an awesome change!

  3. I was looking for this from Day 1 and now its here…sweet, thanks guys! This will make things TONS easier and I am just beginning a new AR where this will really come in handy!

    Now if I could just get those cool funnel reports I saw at Elevate…hmm…hint hint ;)

    • Glad to hear it Terence!

      We are making awesome progress on the lifecycles reports (waterfall, velocity, etc.). I think you will like it a lot and we’ll have more on it soon.

  4. Oh, and one more thing…next step is an expert mode for these logic statements similar to SFDC. The ability to just specify the individual lines and then specify the logic of how they relate with AND, OR, NOT, and (). This is much easier to use for those of us that unfortunately had to take boolean logic in school a long, long time ago. :)

  5. Great addition! Can this only be done in a field which has the “Other” choice in the drop down, or can it be used in all fields? And how do you determine if it’s an “and” or “or” statement in the string?

    Thanks for always improving the system,
    Julie

    • Julie,

      Yep – it should work fine with the “Other” choice in a dropdown!

      And, the fields are always or’ed together. So a rule like: “Prospect default field state is: ‘GA;FL,AL’” is equivalent to “Prospect default field state is ‘GA’ or ‘FL’ or ‘AL’”.

      Let me know if you have any more questions!

  6. Fantastic enhancement – thank you Adam and Pardot team!

  7. One more question – does coding the rules this way have any performance implications as well – i.e., does it make Pardot process the rule faster?

    (Wondering if I should convert legacy rules over to new format or just leave things as is.)

    • Hi Anita — this change doesn’t affect the backend. Rules still get processed the same way so you don’t need to change any of your existing/old rules.

      In an unrelated note, we DID make some other changes that have a positive impact on performance. That is all behind the scenes though and not something you need to worry about as it relates to rule construction.

  8. Does the 255-character limit still apply? I’d like to use multiple variables to filter out some email addresses from a segmentation list, but those email addresses reach the character limit pretty quickly.

    • Ah — unfortunately it still does Barry so you’d need multiple lines in that case in suppose. Are you trying to suppress certain email domains? If that is the case, maybe we can make a better solution.

  9. I’m just getting back involved in helping out with Pardot after not having used it in a year. This is a great feature.