Force timer expire to Results page?

Feb 08, 2013

When the Storyline quiz timer expires, it allows the user to both complete the current question, and to index through remaining, unanswered questions before seeing the results.  Unfortunately, I need to at least prohibit the ability to view the unanswered questions.  In the absence of an SDK, has anyone developed a work-around where I can block this behavior and force the player to go to the results page as the timer expiration triggers?

FWIW, I've already submitted the above as a feature request; I'm just hoping for a creative solution in the interim.

11 Replies
Rusty Worden

Sounds like we are talking about two different things - I have everything working the way it needs to EXCEPT the one thing I cannot seem to control (or just don't know how to), which is the action after the timeout and the learner clicks OK to acknowledge they have timed out. If that can go right to the Results slide, I am in business.

Sam Carter

Rusty Worden said:

Sounds like we are talking about two different things - I have everything working the way it needs to EXCEPT the one thing I cannot seem to control (or just don't know how to), which is the action after the timeout and the learner clicks OK to acknowledge they have timed out. If that can go right to the Results slide, I am in business.


I understand.  In the absence of having a way to get the behavior you want in Storyline's default implementation of timed quizzes,  it might be possible to implement the functionality you are after using JavaScript to implement the entire Quiz process.

An alternate route which still requires JavaScript, but less of it, would be to not time the quiz via Storyline, but have a JavaScript timer implemented in the background.  When the timer expires, it may be possible to proceed directly to the results slide.

Rusty Worden

For me, I need to access a variable which can only be set in the results slide - the fact they don't go there first after the quiz has ended is a bit odd. I can't imagine why the user experience should be any other way in any case. Why would the learner want to have to hit next 20+ times after they can no longer answer questions anyway?

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