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!
TedNunes: As you've seen, a trigger can prevent NEXT from being automatically enabled when the timeline ends with Restricted navigation. In that same situation, notice that the Play button is disabled until the timeline ends. As you discovered, when you click it, the slide enables NEXT, as it would with just Restricted nav. I don't know the reasoning, but that might just be a programming oversight.
There is a workaround: Add a trigger that disables NEXT when the timeline starts*. That will run if the user clicks Play before they complete the interaction, so NEXT will stay disabled.
* A “when timeline starts” triggers runs every time the user reaches the slide—even if the Slide Properties are set to “Resume saved state.” If you don’t want the trigger to run in some situations, you need to add conditions to the trigger. For example, the conditions could check whether the state of buttons on the slide = Visited. Or a condition could check whether a T/F variable = True.