Repeat missed questions in Storyline

Mar 05, 2013

Greg Edwards
By Greg Edwards

My task in Storyline is to present a series of questions to the participant, track their responses, display some result, and then circle back through only the questions they missed. Repeat until all questions are answered correctly.

Now, I figure I can do this manually by assigning a variable as a token for each question, which is granted only after answering the question correctly, and then writing logic to display or skip each question in the series based on whether the participant has the token.

I'm writing here because it seems like maybe Storyline could handle something like that for me, but I'm not seeing it in the canned quiz/response slides. Can anyone provide me with an inside track on this kind of interaction? Thanks!

8 Replies
Greg Edwards
11 years ago03/11/13 at 9:55 am (UTC)

In this case, it's because they don't want the learner to simply try all the answers until they find the right one. I know, I know, there's not much difference, because the learner could just keep picking different answers each pass until they happen upon the correct one. But this is what they want, to give the learner the sense they're going through all the questions, and then cherry picking the incorrect answers to give them closer inspection. It's consistent with behavior that's been developed in a custom-built Flash engine in the past, and we want a proof-of-concept that we can do it Storyline moving forward.

I tried implementing my original idea above, which mostly worked, but I keep encountering a snag. The submit interaction process locks the associated quiz. I can circle back around and display the incorrect questions, but without resetting the quiz, I can't allow the learner to edit their previous responses. I'd almost have to build each question as a separate quiz, so that I can reset only the questions they missed.

So, I'm still looking for any "magic bullets" out there. Thanks!

Phil Mayor
11 years ago03/11/13 at 11:12 am (UTC)

I helped someone build this a while back, it is very labour intensive.  You will need to track variables and choose use a lot of hidden slides (the user will jump across a lot of these).  You would need to use complex branching to achieve s your situation does not occur.  

When I built this it was not intended to be scored, we actually tracked time spent reviewing each question.

Doing it in Storyline and reporting on this is difficult

Greg Edwards
11 years ago03/13/13 at 2:46 pm (UTC)

Peter, I reviewed Jeanette's sample. She's an e-learning MacGyver. She's basically doing the same thing I suggested in my original post. She cleverly got around the reset responses issue using her variables to re-inject the correct answers into the questions and then skip over them. I also noticed that she used only T/F questions, presumably to keep the variables simple for the example.

For multiple choice questions, I'd need additional variables to track not only whether the learner got the question correct or incorrect, but also to track their actual answer (A, B, C, D, E). If your quiz was long or contained more sophisticated question types, you could imagine it quickly getting out of hand.

So I actually pushed ahead with my follow-up strategy: I broke each question into its own separate quiz with its own results slide, and then rolled the intermediate results slides into a final results slide. I moved the intermediate results slides into a separate scene to prevent the them from being displayed after each question. I then used my question variables to reset only the quiz (question) results that are incorrect. Seems to work perfectly. I've attached my .story project file in case anyone wants to take a look at it for ideas.

Storyline is at times a frustrating product, but I'm amazed a how much flexibility it affords you as a developer. FWIW, I absolutely love the support you guys provide. It's refreshing to see a company really come up with some creative solutions to meet their clients (often bizarre) needs. Thanks!

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