Restricted Navigation and Next Button State

Feb 23, 2016


I'm using a Restricted navigation for my project so learner must view all slide content before can click Next to go to the next screen. By default, the Next button, although not functional until all content is viewed, appears to always be active.

Is there a way to use Restricted navigation and have the Next button appear to be disabled (greyed out) until the end of the timeline - without having to add triggers to every slide?


11 Replies
Bryce Gilbert

Hey, thanks Walt. Yes that solution works, but if you view a slide, go to the next slide, and then back to previous, the next remains greyed out so have to view the whole slide again instead of being able to click Next right away. Even if I set to Resume Saved State. Can it be made active on 2nd view? (without adding more triggers/variables).

Because I am using the side menu and want users to view all content of the slide before can go to the next slide, I've selected Storyline's Restricted navigation option. This works fine and when user goes back to replay a previously viewed slide, can click Next button at any time to go to next side. Only issue is client is complaining that the Next button always looks enabled, so would like the Next button to appear disabled on first view.

Trying to keep this as simple as possible without having to add a bunch of Triggers at this point. I wish by selecting the Restricted navigation option, that Storyline would make the Next button appear as disabled on first slide view.


Walt Hamilton
Hugh Betcha

Can it be made active on 2nd view? (without adding more triggers/variables).


Sorry, not that I know of. The problem is that you need to track each slide individually to know if it already has been visited or not. The menu appears to be able to do that. but if you and I want to do it, we have to build variables and triggers for each slide.

Bryce Gilbert

Yes, that's what I thought. Going to avoid creating triggers for each slide. Can perhaps break project down into sections so will need to create fewer variables to check completion, but slides can be skipped thru after a section has been completed.

If Storyline's Restricted navigation option made the Next button appear to be disabled instead of active, wouldn't have this issue.

Christie Pollick

Hi, Hugh -- Just wanted to share as you had mentioned "If Storyline's Restricted navigation option made the Next button appear to be disabled instead of active, wouldn't have this issue.", you are always welcome and encouraged to share your thoughts or ideas for functionality you would like to see with our Product staff by using this form. :)

Amy Lewis

Hi Hugh, not sure if you're still running into this problem but I thought I'd post my solution in case anyone else stumbles across this thread.  It's not elegant since it requires a ton of variables in the project and 3 triggers per slide, but it works.  

First, I make a True/False variable for every slide in my training, set to False by default.  I tend to number them 0101 for Scene 1 Slide 1, 0102 for Scene 1 Slide 2, etc to keep them straight, but use whatever system works for you.  For this example I'll refer to the variable 0101 for Slide 1 Scene 1, but replace that with the variable for every slide you adjust.

I then add a trigger to every slide for "Set 0101 equal to TRUE when the timeline ends" (Substitute 0101 with whatever slide you're on.  So for Scene 6 Slide 5 I would write Set 0605 equal to TRUE when the timeline ends.)

Then add a trigger for "Change state of the Next button to Disabled when the timeline starts if 0101 is equal to FALSE".  This means that the first time you visit a slide the next button will appear disabled, since the slide variable 0101 is FALSE initially.  However, once the user completes the slide the variable 0101 will be set to TRUE, and then each time they revisit the slide the Next button will NOT change to a disabled state.

Finally, add a trigger for "Change state of the Next button to Normal when the timeline ends."  No need to specify any conditions or any slide-based variables.

I tend to do this in conjunction with a Restricted Navigation, since there's a glitch in the way transitions work that would let users skip slides if they clicked 'Next' super fast during the transition before the Disabled state kicks in the first time.  Restricted Navigation keeps them from taking advantage of the glitch.

Hope this helps!

Ashley Terwilliger-Pollard

Hi all,

Great news!  We just released another update for Articulate 360, and included a few important fixes and new features that you'll see in the release notes here.  

The item you may be interested in is how when you restrict or lock navigation, you can now choose whether it impacts just the course menu or also disables the Previous and Next buttons. And you can use triggers to override restricted navigation for individual slides.

Just launch the Articulate 360 desktop app on your computer and click the Update button. Details here.

Please let us know if you have any questions, either here or by reaching out to our Support Engineers directly. 

Amy Lewis

This is great news - and for anyone else reading this, the update includes a visual 'disabled' state on restricted/locked 'next' buttons automatically.  The 'Next' button appears grayed out/disabled when the slide is still restricted, and then automatically updates to 'Normal' when the timeline ends. Thank you for finally relieving this frustration!

This discussion is closed. You can start a new discussion or contact Articulate Support.