Intro

Seven years ago I published a blog post, describing how to create intermediate score slides in a Captivate course. You all know that one of the SCORM rules dictates that you can transfer only one score result with each course. However you are able to show scores obtained with a part of the questions to the learner, and perhaps  make decisions on such partial result.

Time to upgrade that blog post, and make it more usable. In the old post, a Review would lead to buggy results. In the new project you’ll watch, that has been solved. Review works as expected, but for the whole quiz with all the parts.

Recently a question about scored Drag & Drop slides appeared about the Review status. Contrary to normal quiz slides, a D&D slide will not offer information about the correct/incorrect answers, and doesn’t even have Review buttons. That lack of Review buttons means that during Review the learner will be stuck on that slide if you have the playbar disabled during quiz (a good practice). You will find one D&D slide in the example. It will have a Review status.

Example project

It has three parts with questions about the three main stumbling blocks for Captivate users: Timeline, Quiz and Theme. You will see the progress (score) on each quiz slide, for that part. Each part ends with a custom score slide. You can answer the different parts in any sequence, but after finishing all, you will be able to go to the final score slide. That slide is a default score slide. You are free to explore the Review status.

In the questions you’ll see that penalty, partial scoring etc have been used and are reported correctly.

Check your Captivate knowledge. There is only one attempt both on Question and on Quiz level:

Explanation

This was a tough project, will not possible to give a full overview in one blog post. I will dedicate a future post to the setup of the scores for the different parts, another one for the Review status workflow of the Drag&Drop slide. It was an interesting test case for the eternal dilemma: shared or advanced actions.  You know that I am a big fan of shared actions, but in some cases they are not a good choice as you will see. Maybe a third blog post, explaining exactly my reflections…