Skip to main content
Contributor ⭐️⭐️⭐️⭐️⭐️
June 3, 2024
Released

Reconfigure Query in Active JO (new version)

Related products:CS Journey Orchestrator
  • June 3, 2024
  • 56 replies
  • 1382 views

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. 

56 replies

heather_hansen
VIP ⭐️⭐️⭐️⭐️⭐️
June 3, 2024

+1. We frequently need to update queries after publishing, and this is causing us to have to create brand new programs which then complicates reporting and everything else as @Elana Cipin described. 

romihache
VIP ⭐️⭐️⭐️⭐️⭐️
June 3, 2024

We have been asking our CSM for updates, as this is a huge pain point and we got this:

The product manager, Vijay, returned a brief response 
"This is a work in progress and we should be making a release in July."

We are lighting a candle praying for that release, we have so many clones just for one program that is a headache to manage...

Continuous improvement is better than delayed perfection
dayn.johnson
VIP ⭐️⭐️⭐️⭐️⭐️
June 3, 2024

Wow… and to think I’ve been building a new query in a new dynamic JO. Was really hoping to launch this week, and hoped I wouldn’t have to build this net-new program in advanced JO and migrate it later…

But our date ranges frequently change for this program (and others like it) -- and it’s not worth a individual data design (one-off query to send an internal program).

Could we please get this on the roadmap for a launch in advance of the forced migration? This absolutely should have been part of the original query launch in dynamic JO.

Two steps forward, one step back. 🙄

Staff CS Content & Comms Manager, 2x Gainsight CS Ops Product Council Member
dayn.johnson
VIP ⭐️⭐️⭐️⭐️⭐️
June 3, 2024

We are lighting a candle praying for that release, we have so many clones just for one program that is a headache to manage...

I literally created a set of folders for new dynamic JOs, so I can create the new programs in new folders and keep all the old advanced programs in a set of “z_insert folder name here” folders as I begin stopping and migrating old programs over.

Talking to our CSM tomorrow, and will be linking this post straight into our meeting agenda!

Staff CS Content & Comms Manager, 2x Gainsight CS Ops Product Council Member
sarahmiracle
VIP ⭐️⭐️⭐️⭐️⭐️
June 3, 2024

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.

 

What?!?!??! 😩 😰 This is … essential...

Customer Success Systems Admin @ Amplitude, 3x Gainsight CS Ops Product Council Member
Padolfi
Contributor ⭐️⭐️⭐️⭐️
June 3, 2024

+1… this is killing me… I’m trying very hard to adopt the new JO but every step of the way is a pain. I keep on needing to duplicate programs every time I need a minor change. And every single time it´s redoing all of it, building the logic to avoid spamming users from previous programs, and adding the new program ID to the post analysis… 

Padolfi
romihache
VIP ⭐️⭐️⭐️⭐️⭐️
June 3, 2024

 

Two steps forward, one step back. 🙄

That’s exactly how it feels. Query builder was (is) one of the key features of JO but it wasn’t (fully) included in the first launch? Wild that an improved feature is missing functionality that is used left and right in the “old JO” 😐

Continuous improvement is better than delayed perfection
corey.henningsen
Helper ⭐️
June 3, 2024

Couldn’t agree more with everyone here. This is an essential component that’s currently missing from the new JO programs. I love the new UI, but it’s been such a headache any time there are changes needed to active programs. Please Gainsight, don’t push this essential feature out any further than July!!!! 

alizee
VIP ⭐️⭐️⭐️⭐️⭐️
June 6, 2024

Haven’t yet banged my head against that wall, great to find out before I do. Note to self: keep onboarding on a data design. 

The most expensive part of building is the mistakes. That's true in construction. Not so much in CSOps. So ask questions, make mistakes and learn. All views expressed here are my own.
silasramsden
Contributor ⭐️⭐️⭐️
June 21, 2024

This is an absolute must. We have URLs in case expressions added into a multi-step journey and those URLs are changing. So we’re left with the option of:

  1. Cloning the JO and using exclusion lists, meaning people who were mid-journey miss out on the end of their journey
  2. Dead links in email templates

Both of these have a direct end-customer impact.