Forum Discussion
State of Next Button
If we’ve set the “Next” button to go from disabled to normal once the slide is done, and if a learner goes back and revisits the same slide, can we make the button still normal the second time around?
4 Replies
Hi PoojaDwivedi-4d,
If you want to apply this behavior to the whole course, the most efficient way to do this is through the player settings:
- In the top menu, go to Home > Player > Menu.
- Select the gear icon towards the bottom.
- A Menu Options box will appear. Under Menu, select "Restricted" and check "Restrict Next / Previous buttons."
- Select OK.
This will make sure the behavior happens consistently on every slide.
Hope this helps!
Thank you, Rachel! Will this apply to custom made buttons?
This does not -- it would only apply to the buttons in the course player.
To make this work for a custom Next button:
- Create a distinct true/false variable for each slide with a default value of False.
- Create a trigger that adjusts the variable to True when the user clicks the custom Next button.
- Create a trigger that changes the state of the custom Next button to Normal when the timeline starts if the variable equals True.
The triggers should look something like this:
I'm not sure how you have the button set up right now, but in this setup, make sure that its initial state is Disabled.
You would need to copy and paste these triggers on each slide and adjust the true/false variable for each. Maybe someone else knows a more efficient way to do this, but this is what I know. :)
PoojaDwivedi-4d : Restricted navigation controls the Player's Next button. It doesn't affect custom buttons. (There's more info about controlling the Next button here: TIP: Controlling the NEXT Button 101 | Articulate - Community )
It sounds like you have a trigger that disables a custom next button when the timeline starts. That trigger will run every time the user returns to the slide. To prevent that from happening, add a condition (or conditions) to the trigger.
For example, suppose the trigger that enables the custom next button runs when the state of the buttons in the interaction are Visited.
In that case, the trigger that disables the custom next button could have conditions that check whether any of those buttons ≠ Visited. Here's an example:
