February 6, 2021
Remediation and Scoring for Knowledge Check slides.
Comments
(4)
February 6, 2021
Remediation and Scoring for Knowledge Check slides.
Lieve is a civil engineer (ir) and a professional musician. After years of teaching and research (project management/eLearning/instability) she is now a freelancer specializing in advanced Adobe Captivate as trainer and consultant. Her blog is popular with Captivate users worldwide. As an Adobe Community Professional and Adobe Education Leader, she has presented both online and offline. Since 2015 she is moderator on the Adobe forums and was named as Forum Legend (special category) in the Wall of Fame. In 2017 Adobe Captivate users voted for Lieve as a Top Content Experience Strategist.
Legend 215 posts
Followers: 343 people
(4)

Why?

A user in the Adobe forums asked this: “…a Knowledge Check – when an incorrect answer is selected it links you back to the slide where the content for that question is covered? Once they have reviewed the content it takes the learner forward in the training to the slide after the Knowledge Check where they left off.”

This looked like a typical use case for the Remediation feature which is available in Captivate for Quiz slides. Recently I blogged about breaking the eternal loop which normally is linked with that feature in its default setup.  I had not tested the workflow for Knowledge Check slides which share a lot of features with scored quiz slides. Since I planned since a while to explain how to score KC slides thought I could combine both in an example project. That scoring workflow could also be used in an Interactive video, where only Knowledge Check slides are allowed as overlay slides.

Example project

Try it out. The project has a title slide, three content slides, 5 Knowledge Check slides and an End slide. The topic is about ‘decisions’ in advanced/shared actions. Only 1 attempt is allowed for each KC slide. On Success you get a score, on Failure you will be navigated to the relevant content slide. Clicking the Next button on the content slide will bring you back to the Quiz, but to the next quiz slide as the user requested.

Play

Workflow

In this screenshot the Advanced Interaction panel (F9) clarifies the setup for the project. The only missing actions are those used On Enter for the 5 quiz slides:

Remediation

Default setup summarized:

  1. Each content slide (here slides 2, 3, 4) needs a Next button.
  2. The (simple) action for those buttons is ‘Return to Quiz’ (red rectangle in the Advanced Interaction panel)
  3. For each Quiz slide (slides 5-9 in the example) Attempts are set to 1, and the Failure action needs to be: ‘Jump to slide x’ where you replace ‘x’ by the content slide needed for the remediation.  You see in the screenshot that multiple quiz slides can use the same content slide.

Tweak

The user question asked to navigate the learner back to the quiz, but not the same quiz slide but to the next quiz slide. For that reason a very short action was created.

This action needs to be triggered by the On Enter event of each question slide.  For your convenience I saved it as shared action (no parameters) which makes it easy to import in any project. You can download it from this link; EnterQuest.

If you never used Shared actions, look in my blog for the Crash course about using shared actions.

Scoring

Variable

To store the score, create a user variable v_score. 

I inserted a text container on the first question slide, to show the score:
score = $$v_score$$ pt

This text is set to display for the rest of the project. It is hidden On Enter for the custom Results slide. For KC slides, since there is no score by default, the normal Results slide will not be inserted. The score will not be transferred to a LMS, is just meant for self-assessment.

Shared Action ScoreAct

This action needs to be triggered by the Success event of the KC slide (see Advanced Interaction panel in the screenshot at the beginning). The unique parameter allows to set an individual score for each of those KC slides because questions have rarely the same weight. IF you insist on having the same score for each KC slide you can easily create an advanced action using the shared action as template. Download the shared action:
ScoreAct

EnterFirstQuest action

This advanced action is created from the shared action EnterQuest, and is needed when you want the text container to show the score:

It was not necessary to replace the system variable cpInfoPrevSlide by the slide number 4. I did it to clarify the meaning of that system variable. The first question slide is slide 5. Tx_score doesn’t need to be shown when coming from a content slide for navigation. But it needs to be shown on first visit, if the user retakes the course on failure. The text will have been hidden by the action:

EnterResult

This action is needed  On Enter for the custom results slide:

You can see that I used two multistate objects: one with the Characters, one with the message. The passing score is set at 20pt (out of 25 which is 80%). The Normal state of the objects is the one corresponding with a Success, the Fail custom state is for Failure.

Tip

If you are new to using Shared actions, I have an intro course available.

  1. Intro
  2. Part 1step-by-step” OR “video
  3. Part 2 step-by-step” OR “video

Whenever you want to use an advanced action in multiple projects, it is much safer to use a shared action than copy/paste advanced actions. The copy/paste scenario is especially tricky when actions are triggered by slide events or contain references to slides.

4 Comments
2021-04-14 23:44:54
2021-04-14 23:44:54

Very informative and to the point. Thank you !

Like
(1)
>
mahtabn67697795
's comment
2021-04-15 07:53:08
2021-04-15 07:53:08
>
mahtabn67697795
's comment

You’re welcome!

Like
2021-02-14 19:31:58
2021-02-14 19:31:58

Another awesome post, thank you, Lieve! I’ll definitely try your tips on using shared actions.

Like
(1)
(1)
>
atemanyl
's comment
2021-02-14 20:47:06
2021-02-14 20:47:06
>
atemanyl
's comment

You’re welcome! Shared actions are very underestimated and unused by most developers. I never understood why.

Like
(1)
Add Comment