+1, it's somewhat of a pain to have to duplicate and then remap/update the program every time we need to change the criteria or source.

---

Hi,



Thanks for sharing this use case. A few questions here - 



Is the use case about a mistake done in the configuration before publish and you want to modify the unique criteria ?



What do you expect we do with the participants already added in the journey and who violate the newly modified unique criteria?

  - Should we allow them to continue in the journey? - If so , then it will lead to issues where customers might think that the unique criteria is not functioning as expected.

  - Should we allow the participants to be dropped from the journey ? - Even this will lead to confusion for a change happening in the program leading to a participant getting dropped.



Thanks

Abhishek S

---

Hi Abhishek,



In my use case/example, someone used contact id and there happened to be another contact with the same email address on that account.

So the enhancement would be able to add additional criteria in order to add email address to the uniqueness criteria.



I understand the complexity here and see how changing the criteria after the fact can cause confusion. In my use case, I would expect a participant to not added in the future if they now meet the updated criteria.



So to answer your question, yes it was due to a mistake so if there are any ideas to help prevent this mistake I would be okay with those too!

---