Button Link Bug?
Jun 29, 2017
By
James Lavis
Hey folks,
I know people are playing with some branching elements. So I have three sections, in the first I've added a button stack. The first button links to session 2 which is a help page, and the second button links to the content in session 3.
The button links have been associated, but upon testing they both always go to session 2.
Edit: So it ties back to restricted flow for the user. Disabled restricted nav and it fixed it. But this now poses a bigger problem. If we only want to have a user experience an optional element, there is no way to handle that with a restricted flow. Anyone figure a work around for it?
Be the first to reply
This discussion is closed. You can start a new discussion or contact Articulate Support.