Disabling Next button on first visit but enabling on the second

Nov 18, 2014

Hi,

I am trying to put my head around the following functionality. On the first visit the learners will have the next button active only when they are through the content of the slide. I found this posting and am figuring out which way fits me better. http://www.articulate.com/support/storyline/how-to-disable-the-next-button-until-users-finish-interacting-with-a-slide However, I can not figure out how to work with variables  so that learners could click on next any time they want if they revisit the slide. I guess the how to on this question will also impact my choice over disabling the Next button or inserting a self-created one. Thanks a lot!

3 Replies
Nicole Legault

Hi Tamara!

You'll notice in that article you linked to that the first technique uses a simple True/False variable to make the Next button become active only when the Timeline is complete (or when a specific action has occured).

If you use this method with the variable, you don't need to do anything more to enable the learner to click "Next" immediately when they revisit the slide. When the learner revisits the slide, the Next button should be active right away, because the variable has already been adjusted.

Hope this clarifies and helps! Let us know if you have any additional questions!

Preeti Prasad

Hi, I have a follow-up question on this. The solution above works, but what about in case of screens with interactivities or layers? The above solution only works if you change slide properties to resume saved state. The problem occurs when you revisit a screen with layers, it resumes on the last visited layer, and the learner can't view the screen from the beginning. Any solution to this?

I know a long solution is to set a variable to change based on completion of all layers of a screen, so it is maintained each time they revisit, but I have a course that has over 80 screens, and that means 80+ more variables, which tends to make the course run slow. Would appreciate any more inputs.

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