Retry Quiz Button Inhibiting Previous Button Navigation

Oct 26, 2021

One of the boxes to check off when going through an eLearning checklist is the course can be navigated front-to-back and back-to-front, multiple times using only Next and Previous buttons; I'd think that would be an industry best practice when testing a online learning.

One of the triggers that must be included on a Retry button is a trigger that returns the end-user back to the Quiz Directions/Instructions slide (the slide immediately preceding Question #1 of a quiz).

If the quiz has been retried/reattempted two or more times during the first pass through the course, and the end-user gets to the end of the course and tries to navigate backwards using only the Previous button, when they arrive at the Quiz Directions/Instructions slide and click the Previous button, they will be taken to the Results slide from the most recent quiz attempt, not the preceding slide in the natural linear reverse order.

If the end-user continues to click the Previous button from the Results slide they have been taken to, they will return to the Quiz Directions/Instructions slide again.  The next click of the Previous button from that point will reveal a blank (or green) screen. The course cannot connect to the previous slide in the natural linear reverse order.

The issue can be bypassed using the menu, but that is not a viable solution for this development

What I think I may need is a variable with a condition (maybe True/False) that kills the (Quiz Directions/Instructions - Results slide) loop, created when the end-user retries/reattempts the quiz multiple time on the first pass through the course.

Weather that is a variable + condition + trigger configuration applied to the Next button on the Quiz Directions/Instructions slide, applied to the Retry button on the Results slide, or to the Results slide itself I'm not sure.

Again, seems as though anyone using a Retry Quiz button in a project built in Articulate Storyline 3 or Articulate 360 would be encountering the same issue,

This is the final roadblock in uploading a project developed in Articulate 360 to our LMS, so any help would be GREATLY appreciated!

1 Reply