Forum Discussion
Slide results
Good morning,
I would like to know how to display the results slide when a learner has completed all the questions in a quiz. I created a pillbox of errors. The learner clicks on the medicatio...
Do you need to track response and send a score to your LMS/LRS? If so, you need to use standard graded or freeform question slides. Here are two options for when the user clicks a medication:
- Open the question slide in a lightbox.
- Jump to the question slide. If you do this, adjust the Slide Properties, so that the only navigation option is to jump back to the previous slide.
To submit the Results to your LMS/LRS, you also need to include a Graded Results slide in your course.
FYI: This post has info about tracking responses to custom questions: TIP: Track Responses to Custom Questions or Surveys - Articulate Storyline Discussions - E-Learning Heroes
That method only tracks responses for use within the course. It doesn't work with a standard Results slide. However, this post has info about how to send variable values to an LMS/LRS: Storyline 360: How to Send the Value of a Variable to an LMS/LRS - Articulate Support
Hello, That was not the meaning of my question. I can not display the result slide when the different quizzes have been made. I disabled the feedback for each of the quizzes. is for that!
[signature]I'm still not sure I understand what you're asking.
If you want to check whether the user has clicked all the "medication" buttons before they can go to your results slide, here's a quick way to do that:
- Give each "medication" button a Visited state. (It can look like the Normal state, if you want it to. However, I think it's better to give the user a visual indication that a button has been clicked.)
- Add a trigger that allows the user to go to your results slide when state of all the "medication" buttons = Visited. For example, that trigger might change a disabled NEXT button or other navigation button to Normal.
Alternately, you could use a Disabled state instead of a Visited state. That would prevent the user from re-clicking a button.
If that doesn't solve the issue, I suggest you upload a .story file with a copy of the slide(s) that are involved. And add any notes about what's happening that shouldn't happen and/or what's not happening that should happen.
It'll be much easier for someone to troubleshoot if there's a .story file to look at.
