Storyline "review mode" breaking courses

Sep 19, 2022

Hi all,

Our company's courses typically have the following functionality:

We prevent learners from moving forward in a course until a slide is completed (either by viewing the whole screen, or by completing an interaction). We do this by creating a true/false variable for each slide, then adding a trigger to set the Next button to Disabled at the start of the slide if the variable is equal to false, then setting the variable to true when the slide is completed. That way, on revisiting the slide, you can immediately click Next to proceed.

However, we have discovered the following issue:

A learner answers a question that is part of a graded interaction (that is set to Resume Saved State). They select their answer, and click submit. They then exit the course without moving on to the next screen. When this happens, if they then restart the course from where they left off, the screen relaunches in some sort of "Review mode", where they do not see the feedback layer or a submit button, just a next and back button. However, because they did not navigate to the next screen, the state of any variables on that screen were not saved, so the next button is still set to Deactivated, because the variable is still set to False. This locks the user permanently unless they reset the course from the beginning!

I am tearing my hair out at how illogical this is. Why does it do this? Is there any way to disable this? I can't set the question to Reset to Initial State because then they could change their score by getting a different answer on relaunch; I can't just leave the next button active because then they could just proceed immediately and skip questions, which is unacceptable. Is there *any* way I can have a trigger that disables the next button on the first visit to the screen, but that will not disable it in this instance? Is there a way to force it to communicate the status of the screen on exit, so that the variable being set to true is recorded?

5 Replies
Judy Nollet

You don't need a bunch of triggers and variables to prevent the user from clicking the Next button until the timeline ends. That can be done just by using restricted navigation. (You will still need variables to control the Next button on interactive slides.) 

This post provides a demo with details: 

https://community.articulate.com/discussions/articulate-storyline/tip-controlling-the-next-button-101 

S L

Hi Judy,

The solutions you have there are essentially what we've already been doing.

The issue is that, with those triggers, a learner can get stuck forever on any question slide if they answer a question (and thus the Submit trigger fires) but then exit the course before proceeding to the next screen. When you relaunch the course, the next button will be set to inactive, because your "buttons_clicked" variable will still be set to false, because the state of that variable was never saved, because the learner did not move on to a new screen. However, the Submit button will also be gone, and the results layer not showing, because it's stuck in its "review" state.