Skip to main content
New Idea

Dynamic Program - End points and path's need to be more clear in the UI

  • September 10, 2024
  • 7 replies
  • 50 views

**Posting on behalf of a customer**

 

When creating a Dynamic Program (redesigned advanced programs) it should be more clear where the end point is and when there is a break in the path’s that connect one step to the next. We have run into instances where one step appears to be connected but it is not and after publishing, that now disconnected path ends the journey when it shouldn’t. 

 

The image below is to show an example that it looks like it could be connected but it is not.

 

There needs to be a more clear cut requirement to “End the Journey” at a spot instead of just leaving a path open. At the very least we need to make it where it is MUCH EASIER to see when a path is not connected since you have the ability to publish programs with them not being connected, as said above, leaving it open is our current process on how to end the journey. 

7 replies

I would vote for this as well.


anitat
Forum|alt.badge.img
  • Contributor ⭐️⭐️⭐️
  • 14 replies
  • September 12, 2024

As someone who was burned by this, thank you for posting! Upvoted.


TMaier
Forum|alt.badge.img+5
  • Helper ⭐️
  • 175 replies
  • September 12, 2024

Nothing wrong with the old UI’s GIANT STOP SIGN to reflect the end of the path, consider bringing that back. It’s ok if it’s obnoxiously in-your-face, it kind of should be.

 

I think the other issue here is that it is crazy easy to have these paths gets scrambled up as you work. I’ve seen overlaps that reveal a gap when dragged apart (what I believe was being shown in the OP here) and branch lines that move freely when you scroll the window. Those kind of display issues with UI elements are especially dangerous with the heavier focus on building through the new UI.


dayn.johnson
Forum|alt.badge.img+6
  • VIP ⭐️⭐️⭐️⭐️⭐️
  • 636 replies
  • September 13, 2024
TMaier wrote:

Nothing wrong with the old UI’s GIANT STOP SIGN to reflect the end of the path, consider bringing that back. It’s ok if it’s obnoxiously in-your-face, it kind of should be.

 

I think the other issue here is that it is crazy easy to have these paths gets scrambled up as you work. I’ve seen overlaps that reveal a gap when dragged apart (what I believe was being shown in the OP here) and branch lines that move freely when you scroll the window. Those kind of display issues with UI elements are especially dangerous with the heavier focus on building through the new UI.

 

 

Couple examples of what the Eloqua campaign builder looked like (circa 2019). Note the pretty colored lines depending on what they were doing (with the arrows indicating participant movement). And yes -- those lines move as you move the connected object.

This. This is what I dream of being possible in dynamic JO.

 

Program I created -- different numbers for different steps (000 for audience, 100 level for the first intersection, 200 level for the next, and so on), with the exit clearly labeled.
Another example (found elsewhere) with multiple endpoints also clearly labeled by what each endpoint represented.

 


dan_wiegert
Forum|alt.badge.img+3
  • Gainsight Employee ⭐️⭐️
  • 71 replies
  • September 16, 2024

Initially this was a bigger deal because New JO programs didn’t have a UI element for tree termination, but I agree that the current experience when in draft can take a mind of its own, especially if you’re building a larger multi-step program. 

I will say that I do think there is too much variability in where you can place program elements. When building a very large, complicated, multi-step program it is surprisingly easy for interconnected steps to get tangled up until they resemble that rats nest of Christmas lights that you know you’ll never going to unknot… it would be fantastic if there was some sort of “snapback” option for New JO that would essentially reel in all of the stretched out items into a more manageable hierarchical chart.

In the interim, this is why I am very fastidious about implicit step naming. I do this in JO, DD and Query Builder as well. 


anitat
Forum|alt.badge.img
  • Contributor ⭐️⭐️⭐️
  • 14 replies
  • September 16, 2024
TMaier wrote:

I think the other issue here is that it is crazy easy to have these paths gets scrambled up as you work. I’ve seen overlaps that reveal a gap when dragged apart (what I believe was being shown in the OP here)...

it’s my program and yep, I had no idea this happened and accidentally put GS Support on blast when it was a scooby doo mystery (me) all along


anitat
Forum|alt.badge.img
  • Contributor ⭐️⭐️⭐️
  • 14 replies
  • September 16, 2024
dayn.johnson wrote:

 

Couple examples of what the Eloqua campaign builder looked like (circa 2019). 

 

idk whether it was rude or brilliant to share this… maybe I’m just annoyed that JO doesn’t already look this aesthetic :D


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