7 Replies Latest reply on May 18, 2018 1:04 PM by Grégoire Michel

    What is the "reason" constraint supposed to contain in a "Data Value Changes" trigger ?

    Denise Greenberg

      The picklists come up empty for both "source" and "reason" in the Data Value Changes constraint. This thread started by Grégoire Michel discusses the same thing but focuses on the "source" constraint - and concludes that the list of acceptable values are the same as those for the Source Type (such as in the "Person is Created" trigger) - and that those values are documented here: Understanding System Managed Fields - Marketo Docs - Product Documentation


      Does anyone know what the reason constraint is supposed to contain?


      Its seems like these two constraints could be useful for documenting the source for GDPR (or CASL) opt-in.


      Thank you!