Forum Discussion
Storyline 360 Restricted Next behavior (sanity check)
Hey TedNunes,
Happy to jump in here.
I can confirm that EricSchaffer-d1 is correct. This functionality has been present in Storyline for a while. Restricted Navigation handles it all natively.
- 'Next' auto-disables on first visit, re-enables at the end of the Timeline, and stays enabled on any revisit.
The reason you needed the extra 'disable' Trigger with unrestricted navigation is that it doesn't have any of that built-in logic, so you had to manage both ends yourself. Adding any change-state Trigger targeting 'Next' signals to Storyline that you're managing the button state manually, so it overrides the auto-enable behavior and defers to your Triggers instead.
One of our Storyline gurus (JudyNollet) shared an excellent breakdown of all the ways to control the 'Next' button if you'd like to go deeper:
Please let us know if you have any more questions!
Thanks Judy. The trigger you're describing is what we've been already been doing for years, which means we have to have two triggers (1. force NEXT to stay disabled, 2. enable it when interaction is complete.)
My original post explains how I didn't realize until just recently that NEXT would automatically stay disabled by adding a single trigger targeted it. Hurray, we can drop the extra trigger.
But then this morning I realized that it WILL enable if you just click Play. It seems like a bug--why have the behavior to prevent NEXT from enabling if a trigger is there, but then enable it if Play is clicked regardless of that trigger firing (and not having left the slide yet)?
I work with Nurse educator SMEs who don't trust their students to not skip over things, so I have to be robust in my navigation restrictions. I was excited to be able to drop a trigger or two, but alas. Thanks everybody for your input.