Skip to main content

I’m trying to adopt the new version of Journey Orchestrator, but keep finding areas where it’s not in parity with the old version!

 

In the new version, if your participant list is based on a query, that query can’t be edited once it’s active. It can’t even be edited if you pause the journey. The only solution I see is to clone the journey, make updates in the new, and activate changes in a new program. TL;DR this is a hassle, and time consuming! This is challenging because you have to then manage different versions, potential exclusion list for the new JO to not pull in participants from an old version, you have to monitor the old to make sure everyone has complete before stopping, you have to create reports to get analytics of all versions, etc.

 

Would love to see the flexibility that the old version had, where you can adjust your queries on active JO’s. 

Any updates here?  It bit me again today when I had to rebuild 6 programs because I needed to make one tweak to the query.  In rebuilding, I just used Data Designer to do everything but the final filtering, but I’ll say again, I hate having to create a new object every time I need to create a program. 

Any updates here?  It bit me again today when I had to rebuild 6 programs because I needed to make one tweak to the query.  In rebuilding, I just used Data Designer to do everything but the final filtering, but I’ll say again, I hate having to create a new object every time I need to create a program. 

 

☝ 💯

 

Similar (but different) experience myself just yesterday, had to change one field in multiple active programs, but instead of it biting me, it was instead yet another case of “so glad we aren’t using dynamic JO yet.”

  • Each of the affected programs has multiple sources (queries)
  • I was able to directly edit the new programs without having to clone, edit, and exclude
  • I was able to map the new field so it shows up on net new participants

And we had another program ​@kstim has had to make multiple edits to (also advanced) where we’ve both said the same thing.

While I did have to make the changes on each specific query, I’d much rather have to do that than starting and stopping each of those programs to make the change.

​@heather_hansen, agreed on using Data Designer to build the queries.

Hello everyone,

We are introducing edit capabilities for active programs in the upcoming release. This includes a new edit mode that allows you to create a copy of the active or paused program that needs to be updated. All edits will take place in this copy, ensuring that the active or paused program remains unaffected and the edits are logged in the execution history.

In this release, we will only be allowing edits to the source filters so you can update the participant list for the program. This is not the full capability yet; we plan to launch options for adding new fields and case statements in the Query, followed by the ability to modify the program flow by adding or changing steps and branches along with other improvements. The release is planned in phases due to some ongoing events and the Pulse conference. The updates should have been shared via email.

Thank you for your feedback - looking forward to launching new features in the upcoming releases!

Thanks, ​@vmallya ! Can you give us an idea on timeline for the follow on items? I still haven’t seen a full outline of what all of the planned edit capabilities will be and when we’ll get them.

 

Thanks!

Terms & ConditionsCookie settingsAccessibility statement