Ability to quickly move around custom journey setup screens.
Support received the following enhancement request from an Admin.
They would like if you could click on the steps along the top of the journey set up page ("Describe your journey", "Build your journey", "Target journey to audience(s)", "Review and publish journey", and "Journey available to learners") could be clicked on to quickly jump to that section instead of having to click the Next button to navigate one step forward at a time. An account would be while on the "Describe your journey" page/step, they could click the "Target journey to audience(s)" to jump to that page instead of having to click the Next button to go to "Build your journey" and then the Next button again in order to get to the "Target journey to audience(s)" step.
They would like if you could click on the steps along the top of the journey set up page ("Describe your journey", "Build your journey", "Target journey to audience(s)", "Review and publish journey", and "Journey available to learners") could be clicked on to quickly jump to that section instead of having to click the Next button to navigate one step forward at a time. An account would be while on the "Describe your journey" page/step, they could click the "Target journey to audience(s)" to jump to that page instead of having to click the Next button to go to "Build your journey" and then the Next button again in order to get to the "Target journey to audience(s)" step.
1
Comments
-
-
Hi @Joseph Duthie,
We did consider and discuss linking the steps with our UX team while building out the custom journey workflow. What we found is that it sounds good in theory but is harder to implement as a good user experience. Custom journey creation and editing is broken up into those steps because certain information is required in each step in order to have a publishable journey at the end. An example of what I mean is: if the steps are linked, an admin can skip between steps, and completely skip a step, without scrolling down to verify that all the data necessary for the journey is present in the form on each step. They could get to the end and not be able to publish, without a clear indication of why. We discussed linking some steps based on whether we have all the info we need for that step, but again, it wouldn't necessarily be clear why some steps could be skipped and some couldn't. This would be true in other areas where we use the stepper, such as the journey creation process. If we linked eligible steps in the edit workflow, the expectation is that the stepper would work the same way wherever the component is used. Except that we couldn't link any steps in the creation workflow because all of the journey data is needed before moving on to each step. Hopefully all these potential issues make sense. In the end we decided that trying to link the steps would create a more confusing user experience than it would be useful.0