Today, if we want to trigger an action on lead creation with some constraints on the field values, we have to add a filter ni addition to the "person is created" trigger.
The issue with this approach is that sometimes, due to the time taken to update the database, the filter will retrieve no value and a person will wrongly be excluded.
To workaround this, we can remove the filter, add a few minutes wait to the flow step and test in the first following flow step with choices. But this other approach has many drawbacks and flaws:
- Whatever the wait, there is always a small risk that the database update has not completed and the campaign will not process for some leads
- After a few minutes wait, some other changes might have occurred to the record, which would completely change the outcomes of the choices.
It would be much more efficient if all fields in the lead and company fields were available as constraints to the "person is created" trigger. The constraints would be evaluated from the values in memory, rather than from the values in the database, delivering more consistent results.
Some more background here: https://nation.marketo.com/message/185840-re-trigger-fires-due-to-data-value-change-but-filter-for-t...
-Greg
.png)