I believe @Darren_Murphy worked on something like this weeks ago, but it was for moving to a specific component at the top of the screen or something like that. Probably he can help.
If I recall right, it was using visibility conditions.
I took a look at @Darren_Murphy 's post about his need and saw mention of Deep Links. Poking around a bit, I saw a suggestion that made me think (for no particular reason) that since the list is the last item on the Screen, why not just jump to another screen which is the list of stops for the particular tour. Duh.
But that still does not answer how to do the equivalent of jumping to an anchor point somewhere else on the same screen…
As far as I’m aware, there is no easy way to do this right now.
In my situation, I wanted to do the opposite - jump back to the top of the screen.
The closest I got to a working solution was to temporarily hide all components on the screen as part of an action sequence. This kind of worked, but the user experience was very confusing, so I never used it. The biggest problem with that solution is that you cannot control the sequencing of a flow of actions - they all fire at once. But it might be worth a try if you don’t have lots of components on the screen (I had in excess of 70).
This isn’t anchor tags, but I like to break parts of the screen into sections and use choice components to control visibility of components. That way I can get a lot of content on one screen, but use the choices to control what is visible at any given time.
Hi, Jeff Does it work by any chance if the components to hide are above the conditional choice list (or any trigger).
Or does order matter, like in usual programing (top to bottom computation) logic?
Thks.
I’m thinking of an anchor alternative (since obviously everybody confirms that is not doable natively like html) that could indifferently jump top as well as bottom, depending on the position we are (elevator logic).
I may consider floating buttons or action buttons as triggers to condition visibility
Yes it works no matter where your place the choice component on the screen. All the choice component does is set a value in the data, and then I hide or show components based on that value.
Pretty simple actually. In the table that the screen is attached to, I have a user specific column where I store the value from a choice component. Based on that value, I have visibility conditions on several components to hide or show them based on that selected choice.