Forum Discussion
Help with tracking and reporting status, scores and completion
Hi everyone. I have a course with Scorm 2004 3rd edition. It has pretest, content and postest. My client wants that if the learner approves the pretest, the LMS marks "approved" and the score, but not "complete", because there are two more content slides to read and once read, now ths course is "complete". If the learner fails the pretest, he has to review several slides, pass the postest in 3 opportunities marking approved and the score, but not complete because he also needs to review the final two extra slides. What publishing configurations do you reccomend? Do I need more triggers? I know this is very specific, but there are many parameters and I am confused and maybe there are efficient ways to do it. Thank you.
2 Replies
This is not too difficult, I think. You just need to decide exactly what you want Articulate to use to "confirm" that the learner has "completed" the course.
In the Reporting and Tracking options (located under the Publish options), look at the tracking tab. The first selection options are what is actually reported to the LMS and thus used to determine what "completion" status the learner record will show.
In your case, the pretest is simply going to determine whether the learner needs to work through the rest of the material, except for the two remaining content slides (which it sounds like everyone needs to review). So I would suggest that you use the score (result) of the pretest to permit the user to skip directly to those two ("Must Read") slides. [If pretest score /> 80% (or 90% or = 100%) then go to "Must Read Slide #1" when you click Next.]
On one of those slides (probably the second), you add a button ("I understand..." or "I acknowledge..." or something similar), then to that button you add the trigger "complete course."
And in the Tracking options, select the third choice: The course is marked as complete in the LMS when the learner clicks that button to "complete the course."
Make sense?
Thank you. I´ll try this solution, though it seems that there are communication issues between my scorm and the client´s LMS (Cornerstone). But I´ll apply your suggestion, of course.
