Help learners improve their knowledge by letting them review and retry only the questions they get wrong, so they don’t have to repeat the questions they get right.
For example, let’s say you take a quiz with 20 questions, and you get one question wrong. You don’t want to cycle through all 20 questions again to find the one you got wrong. You only want to see the one that got away. Storyline 360 lets you do just that, and it’s so easy!
Step 1: Add Review and/or Retry Buttons to Your Result Slide
- Go to your quiz result slide and select the Result Tools—Design tab on the ribbon.
- Click Review Button or Retry Button, then click the slide where you want the button to appear.
- Edit the button’s appearance to match your course design.
Click here to learn more about working with result slides.
Step 2: Edit the Review and/or Retry Triggers
- Double-click the Review results trigger or the Reset results trigger in the triggers panel.
- Mark the box to Review only incorrect questions or Reset only incorrect questions, as shown below.
|Review Results Trigger|
Click to enlarge
|Reset Results Trigger|
Click to enlarge
- Click OK to save your changes.
Click here to learn more about working with triggers.
Does this feature work with question banks and branching quizzes?
Yes. Learners can review and retry questions they get wrong whether those questions are standalone slides or draws from question banks. It also works with branching quizzes.
Does this feature work with the modern player and the classic player?
Yes. It works with both player styles in HTML5, Flash, and Articulate Mobile Player output.
What happens when learners answer all the questions correctly?
If you’ve enabled the options to review and retry only incorrect questions, the review and retry buttons won’t do anything when learners answer all the questions correctly.
To give learners the best experience in this scenario, consider adding triggers to your result slide that hide or disable the review and retry buttons when the learner’s score is 100%. Here’s an example: