Forum Discussion
Next Button - Enabled - Saved State
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 thre...
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!
