Fairly basic scenario. In Sales Cloud, a custom record is created or updated (boolean field equals TRUE
) it will inject the related Contact to the Journey and that's that. This specific Journey allows multiple entries.
What is the most sensible way to Exit a Contact from a Journey if same example record is changed in Sales Cloud, so that the boolean field now equals FALSE
?
It seems that the Exit Criteria is fairly limited, by allowing to check only Contact Data path which means it's not usable for Journies allowing multiple entries for the same Contacts.
Same with Decision Split activity with Attribute-to-Attribute comparison, as this does not allow to check nullable fields.
Similar question was raised in February about using SF source based entries and Exit Criterias but recieved no attention.
Any suggestions?