Skip to main content
New Idea

You should not be able to delete mapped participant fields that have a dependency

Related products:CS Journey Orchestrator, Email & Notifications
  • July 12, 2022
  • 1 reply
  • 15 views
  • danielwal_coco

kelly
  • Helper ⭐️⭐️⭐️
  • 312 replies

This issue where changes to a picklist value do not propagate to all JO features is really biting me this week when a user deleted and readded the mapping in order for the picklist values to appear. This results in the conditional wait step breaking (as in, it doesn’t load) but variant filters do load. Replicating the program carries the same behavior.

I now have to delete the conditional wait step and all preceding steps to rebuild them with some emails having 18 variants to be filtered. 

You should not be able to deleted a mapped participant field that has a dependency within the program given the repercussions it creates.

1 reply

matthew_lind
Forum|alt.badge.img+11
  • VIP ⭐️⭐️⭐️⭐️⭐️
  • 651 replies
  • July 12, 2022

Anything that strengthens the reliability of Journey Orchestrator is a +1 from me.

With Journey Orchestrator being a key component of digital-led journeys, there’s serious value in more guardrails to ensure it isn’t inadvertently disrupted by a seemingly innocent change elsewhere.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings