Contributor ⭐️⭐️⭐️⭐️⭐️

Released

Reconfigure Query in Active JO (new version)

Related products:CS Journey Orchestrator

Forum|Forum|2 years ago
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.

Show previous replies

romihache

VIP ⭐️⭐️⭐️⭐️⭐️

TIL (from support):

There is a concept called "Ghosting Fields" which has been introduced in Dynamic Programs

In short, it looks like if your query contains 12 fields, you map 5 in your program and publish it, JO drops the other 7 fields (it “ghosts” the 7 fields not used), and those 7 fields can’t be mapped once the program is published.

Searching the support articles and community for “ghosted”, “ghosting” and “ghost” returns 0 results, and the Admin Guide for redesigned JO (Audience Section) has no mention to this. Perhaps I should ask Bruce Willis to take a look.

Ooof… thanks for sharing that. Not the first time we learn something when submitting a ticket for an issue that ends up being “intended behaviour not called out in the documentation”... Adding that nugget to my mental vault for the time being 😕
FYI @corey.henningsen @Molly.McQ

PS: Chapeau to The Sixth Sense’s reference 😂

Continuous improvement is better than delayed perfection

dayn.johnson

VIP ⭐️⭐️⭐️⭐️⭐️

TIL (from support):

There is a concept called "Ghosting Fields" which has been introduced in Dynamic Programs

In short, it looks like if your query contains 12 fields, you map 5 in your program and publish it, JO drops the other 7 fields (it “ghosts” the 7 fields not used), and those 7 fields can’t be mapped once the program is published.

Searching the support articles and community for “ghosted”, “ghosting” and “ghost” returns 0 results, and the Admin Guide for redesigned JO (Audience Section) has no mention to this. Perhaps I should ask Bruce Willis to take a look.

In this (living nightmare 😱) situation where JO where edits are limited once published, it’s been a (spooktacular 👻) oversight from the docs team to omit the concept of “ghosting fields” from the product/support documentation. Enough to make you Scream? A fix in Q3 you say? Hopefully before Halloween 🎃…

Oh. Oh no. Add this to the reasons I haven’t started migrating any of our existing programs yet.

Not only do we have to stop and republish if we need to change the query. Now we need to republish if we decide we want to add an included field?

But wait… is that “mapped to a token?” Since “custom field mapping” is no longer a thing, I’m curious. 🤔

Staff CS Content & Comms Manager, 2x Gainsight CS Ops Product Council Member

Stuart

Helper ⭐️⭐️

Oh. Oh no. Add this to the reasons I haven’t started migrating any of our existing programs yet.

Not only do we have to stop and republish if we need to change the query. Now we need to republish if we decide we want to add an included field?

But wait… is that “mapped to a token?” Since “custom field mapping” is no longer a thing, I’m curious. 🤔

@dayn.johnson Let’s say your query contains field “ABC” that you did not map prior to publishing. After publishing, you change your mind and want to change a token from being mapped to field “XYZ” to field “ABC”. As I understand you can’t, because “ABC” isn’t a mapped field upon the program being published, it becomes a “Ghosted Field” at the point of publication. “Ghosted Fields”, I imagine, are the delta between your last dataset in the query and the “fields used” section of the audience.

dayn.johnson

VIP ⭐️⭐️⭐️⭐️⭐️

@dayn.johnson Let’s say your query contains field “ABC” that you did not map prior to publishing. After publishing, you change your mind and want to change a token from being mapped to field “XYZ” to field “ABC”. As I understand you can’t, because “ABC” isn’t a mapped field upon the program being published, it becomes a “Ghosted Field” at the point of publication. “Ghosted Fields”, I imagine, are the delta between your last dataset in the query and the “fields used” section of the audience.

Thank you for the clarification! And this as we’re looking to scale our digital-led CS… 😥

Staff CS Content & Comms Manager, 2x Gainsight CS Ops Product Council Member

ajprince

Contributor ⭐️⭐️⭐️⭐️

It’s extremely frustrating not having this feature available within the new JO program designs. It makes using new features like this very difficult. We need feature parity!

dcassidy

Helper ⭐️⭐️

Hoo boy… back on this thread again today.

TIL (from support):

There is a concept called "Ghosting Fields" which has been introduced in Dynamic Programs

In short, it looks like if your query contains 12 fields, you map 5 in your program and publish it, JO drops the other 7 fields (it “ghosts” the 7 fields not used), and those 7 fields can’t be mapped once the program is published.

Searching the support articles and community for “ghosted”, “ghosting” and “ghost” returns 0 results, and the Admin Guide for redesigned JO (Audience Section) has no mention to this. Perhaps I should ask Bruce Willis to take a look.

In this (living nightmare 😱) situation where JO where edits are limited once published, it’s been a (spooktacular 👻) oversight from the docs team to omit the concept of “ghosting fields” from the product/support documentation. Enough to make you Scream? A fix in Q3 you say? Hopefully before Halloween 🎃…

I ran into this same issue right before the 4th Holiday weekend. L1 Support did not know about this concept, and it wasn’t in the documentation. They directed me to recreate programs from the ground up (when we already had a program started and in progress), so we had to get creative to leave that small # of participants on that program, then create the new program - only to have the same issue. He then escalated to L2 support who introduced this to me like it was some awesome new GS feature.

Incredibly frustrating!

darkknight

Expert ⭐️

Hoo boy… back on this thread again today.

TIL (from support):

There is a concept called "Ghosting Fields" which has been introduced in Dynamic Programs

In short, it looks like if your query contains 12 fields, you map 5 in your program and publish it, JO drops the other 7 fields (it “ghosts” the 7 fields not used), and those 7 fields can’t be mapped once the program is published.

Searching the support articles and community for “ghosted”, “ghosting” and “ghost” returns 0 results, and the Admin Guide for redesigned JO (Audience Section) has no mention to this. Perhaps I should ask Bruce Willis to take a look.

In this (living nightmare 😱) situation where JO where edits are limited once published, it’s been a (spooktacular 👻) oversight from the docs team to omit the concept of “ghosting fields” from the product/support documentation. Enough to make you Scream? A fix in Q3 you say? Hopefully before Halloween 🎃…