Enabling Next Button After the Slide has been visited
Feb 05, 2021
Hi everyone,
I am trying to figure out how to allow the next button to remain enabled after a slide has already been viewed. I have a slide with 4 layers, I have disabled the Next button until the learner views all layers- this works fine, the learner moves onto the next slide but then realizes they want to go back to the first slide with the 4 layers. When they go back, the Next button is disabled and even if they click on all the buttons to view all the layers again, the next button remains disabled. I have tried to edit the settings in the slide with the layers to say when the learner revisits the slide it would resume its saved state and that doesn't fix the issue. Does anyone have any ideas on how to fix this? Do I need to create variables for this type of issue? I am using Storyline 360.
Thanks,
Desi
13 Replies
Hello Desi, could you try changing the Slide Properties, which can be accessed by right-clicking the slide, so that the drop-down 'When revisiting:' has the 'Resume saved state' selected?
If that doesn't work, you may also try changing the Slide Layer Properties, which can be accessed by right-clicking each relevant layer (in your sample, the 4 layers) on the Slide Layers panel, so that the drop-down 'When revisiting:' has the 'Resume saved state' selected as well.
Hi Ian,
I tried both of the suggestions and nothing worked. When I click on the "PREV" button, it takes me back to the original slide but the NEXT button on that slide is Disabled. There must be a way to fix this?!
This post was removed by the author
Thanks Desi, could you let me know what the triggers are for the NEXT button to be enabled? I'm suspecting that those triggers have not all been met, that's why the NEXT button doesn't get enabled on the revisit.
You may also attach the story so I can have a look.
Lan’s button settings are correct.
Hi There,
The triggers are:
Change state of next button to Disabled when the timeline starts on this page.
Change the state of Next Button to enabled when the state of buttons 1, 2, 3 are visited.
This works and the learner is able to progress to the next slide. The problem is when they are on the next slide and they click the PREV button to go back to the slide they just visited, the NEXT button on that slide is disabled even though the revisit settings say to continue with the resumed state and even though the buttons have already been clicked and slide layers visited.
Hi Desi,
This slide properties is very important.
Yes, I have done this already. It makes no difference. When the learner goes back to the slide, they cannot click next.
are you sure, at the basic level, everything is set like this?
Thanks for trying our suggestions, Desi. Would it be possible for you to attach the story file so we can have a look?
Hi everyone,
Thank you for taking the time to help me! The articulate team solved the issue. The problem was I lacked some variables. The resumed state was not the issue. I needed the following triggers on my main slide:
1. Add three T/F variables named "var_anatomy, var_advantages, var_limitations" (or any variables name you prefer) and set the value to FALSE.
2. On the base layer of Slide 3.27, add this trigger:
Change state of the Next Button to HIDDEN When the timeline starts on this slide IF var_anatomy = FALSE AND var_advantages = FALSE AND var_limitations = FALSE
3. On each slide layer, change the value of each variable to TRUE.
Ex. On slide layer Anatomy, add this trigger
Adjust var_anatomy = TRUE
When the timeline starts on this slide
Same with the other two slide layers, but use the other two remaining variables
4. On EACH slide layer again, add the trigger to change the state of the Next Button to Normal
Change state of Next Button to Normal
When the timeline starts on this layer
IF var_anatomy = TRUE
AND var_advantages = TRUE
AND var_limitations = TRUE
I'm glad that Ronaziel was able to help you, Desi. I appreciate you chiming in to share your solution with the community.
That seems really convoluted. There must be an easier way.
Using conditions that check variable values is probably the best way to control the NEXT button. And it is easy when you get the hang of it. Otherwise, you could have the conditions check the state of the appropriate objects (e.g., disable NEXT if any of the buttons is not Visited).
Here's a post with a demo file about controlling NEXT. Perhaps this will help:
https://community.articulate.com/discussions/articulate-storyline/tip-controlling-the-next-button-101