Next Button - Enabled - Saved State
Feb 24, 2022
Hi, I'm using 360. I have disabled the next button on the start of a slide. After the learner clicks/reviews each of 3 topics (information on 3 layers) the states change to visited. Once all three states are visited the next button is enabled. (trigger is 'change state of Next button to normal when the state of all the pictures is visited') This all works fine.
When I advance to the next slide and then hit 'previous' the original slide is back to it's initial state (and the next button is disabled again). Even if I change the slide properties to "resume save state" or "automatically decide" the next button is still disabled.
Any suggestions on how to get the next button enabled when revisiting the slide without creating a variable on each slide? (Update - I tried using a variable and the next button still does not enable when revisiting the slide - I have the slide properties set to 'resume saved state').
7 Replies
Instead of deleting my post, i'm going to put the link to this article that helped me solve the problem. Instead of disabling when the timeline starts i had to change it to when the variable is false. https://community.articulate.com/discussions/building-better-courses/create-a-custom-menu-slide
Hi, D.
Thank you for sharing how you solved this issue, as I'm sure it will be helpful to other community members who might come across this discussion!
I am having the same issue. I feel like the situation you described is a very common one, and that based on the setting you selected for the slide (resume saved state) and "next" enabled once something happens, that the slide next button should be accessible once the page is revisited. The fact that the "saved state" functionality doesn't work as described seems to be an error on the Articulate side. I don't feel like we should have to build variables for each slide to mimic functionality that supposedly already exists out of the box. What's the use of the "saved state" option if it doesn't actually work?
Hello Cas,
Happy to help!
One possible explanation for the behavior you're experiencing is the fact that triggers are still activated even if a slide makes use of the Resume saved state setting in Slide Properties. This means that a trigger like the one below will cause the 'Next' button to return to its disabled state even after becoming enabled via a different trigger:
I've attached a sample project file so you can see one solution that you can use to get around this behavior. In case the situation above isn't applicable to your project file, would you be willing to share a copy of your project file here or in private by opening a support case so I can take a look at what you have currently setup? We'll delete it when we're done testing!
Thank you Joe. I reviewed the file you posted and submitted a case, as this doesn't seem to apply to the problem our learners are having.
Good call on opening a support case! I can see that my colleague Jan already shared the results of his investigation there. Please let us know if you need help with anything else!
"Resume saved state" is set in Slide Properties. It only applies to objects on the slide. The Next button is in the Player. In other words, "Resume saved state" doesn't control the Next button.
When using triggers to disable and then enable Next on an interactive slide, it's best to add a condition to the disable-Next trigger. For example, have that trigger run only if a T/F variable = False. Then add a separate trigger that changes the variable to True whenever the interaction is done.