Guide engagement with dynamic / conditional elements?


Userlevel 1

I’m creating a dialog guide-style engagement to walkthrough a reporting feature. It works fine in accounts that have reporting data in them, but in new accounts without any data, many of the elements that I have steps for are not present. In that case, when the user clicks “Next”, PX looks for the next element, can’t find it, and the tour just stops. Is there a way to have PX go to the next element that it *can* find, instead of just stopping?


8 replies

Userlevel 1

So as a workaround I inserted an “Intro” step in the very beginning that is linked to one of the elements that only appears when the account has data. That way, the engagement never shows if the account doesn’t have any data. Still, it would be nice if we had control over the behavior when the next element can’t be found. Maybe options to wait for it, end the engagement, or skip to the next step that can be found.

Userlevel 7
Badge

Nice workaround @acheslow! I agree that having an “auto-skip” to next “available” step would be pretty nice.  Thanks for sharing your findings with our Community!

Userlevel 5

Hi @acheslow 

This is a great use case for the segmented guide based on the user’s context. It would be great to have 2 set of engagements relevant and targeted to both Group/Types of Accounts- Has Data and doesn’t have data. This can be passed to PX as an account attribute.

 

Let me know what you think.

Userlevel 1

Hi @harshibanka thanks for the idea. I think we would have to do some dev work to expose that as an attribute to PX so it wouldn’t be ideal for us. Maybe helpful to someone else though, so thanks.

Userlevel 3

This is a pretty critical issue in our workflows. I also think this should not be marked as “resolved” as a workaround that doesn’t show the engagement is not really a resolution.

This conditional stepping is a standard feature in several other workflow tools on the market. It is something that is necessary for complex system navigation like our web tools.

Userlevel 7
Badge +2

This is a pretty critical issue in our workflows. I also think this should not be marked as “resolved” as a workaround that doesn’t show the engagement is not really a resolution.

This conditional stepping is a standard feature in several other workflow tools on the market. It is something that is necessary for complex system navigation like our web tools.

@JPKelliher changed this to feature request.

I agree this is pretty standard feature 

Also - same but a bit different - if the next step was already taken, skip it and not present it 

For example, If the next step is click on a radio button, but it is already selected from some reason, do not show this step, and move to next 

Otherwise it looks a bit stupid that We have step where the user does not have to do anything 
Thanks 

Posting this similar request for visibility: 

 

 

Reply