Attempts not recording to LMS

Hi Phil,

I don't think that's right because if I change the tracking to be based on screen completion rather than a Results slide then new attempts are recognised as such if you fully complete a course and then reattempt it. The problem only occurs when the tracking is based on Results slides.

Also when I conduct the same tests on the SCORM cloud again the number of attempts remains at 1 but when I test other modules (created with different authoring systems) the number of attempts updates.

I therefore conclude that the Storyline SCORM handling js scripts are responsible but I agree there is no options in relation to this in Storyline and I assume that there is a bug. I have filed a bug report.

Hi Justin, thanks, that would all make sense except that my testing reveals that if the default exit type is set to Unload I am both able to resume my progress and also a new attempt is recorded.

Also your explanation doesn't explain the discrepancy between tracking via slide completion and tracking via Results slide (when the default exit type is set to resume). If tracking via slide completion then the attempt number correctly updates following full completion of the SCO. Tracking via results slide, however, never increments the attempt nuber.

Regards,

Gordon

For those of you experiencing this issue and use the Saba Platform here is what I received from their technical support:

Per review of the user communication logs as well as the result of my testing on the content, the content is passing a successful completion status, but as you stated the content exit status is in suspended state. Thus the content rollup is not completing and the class remains as In Progress.

I checked the microsite setting for "Consider Content Attempt in "Suspended" state for completion for SCORM2004 type content" and this is currently set to zero meaning the system will take the content specific value.

To resolve the issue, there are two options:

1. Update the microsite content setting to 1, so that all SCORM 2004 type content is considered for completion.

Admin > System > Configure System > Mirosite > SabaCloud > Site Properties > Content > "Consider Content Attempt in "Suspended" state for completion for SCORM2004 type content" = 1 > Save

OR

2. On the Content Details page for this content, enable the setting "Consider Content Attempt in "Suspended" state for completion" by checking the check box and saving the change.

Note: Option 2 will only set the consider suspended state for completion for that particular content.

Sounds like the course is not opening up in your LMS as a new attempt, in this case it will then always overwrite the previous attempt. This should be a setting in your LMS there is no option in Storyline to force a new attempt.

After marking as complete the LMS should open the course in open in review mode and not overwrite the score, most LMS's offer the option to start a new attempt.  Sounds like it is either not being marked complete or starting a new attempt

Which LMS are you using?

You can change the configuration.js so score can only improve doesn't help with attempts though

Hi Gordon,

I see that you've opened a support case (# 00419709 for my reference), so I'll follow along in your case as well to share any updates or information here.

Hi Phil,

Thanks again for your replies. I'm using an LMS from Seertech but the problem also occurs on the SCORM cloud. As I say, the course correctly updates attempts if tracking is based on slide completion rather than on a Results slide. I'm going to do some more testing today with a very basic 5 slide course to make sure I can replicate the problem. I'd be surprised if I was the first one to note the issue.

I've been working on this and have come up with a solution.

If I change

var DEFAULT_EXIT_TYPE = EXIT_TYPE_SUSPEND; in Configuration.js to:

var DEFAULT_EXIT_TYPE = EXIT_TYPE_UNLOAD;

then every attempt (even if the SCO hasn't been completed) is treated as a new attempt and I get a historic record of previous attempts rather than just having it overwritten.

Strictly speaking this breaks the SCORM standard because a new attempt should only occur after full completion of the SCO. Still it's better than never recording a new attempt which is the Storyline default which also breaks the SCORM standard.

Good Morning, Gordon.

I definitely don't want to stir the pot on whether or not we are breaking the SCORM standard, but I think I can try to explain why we've chosen to do things the way we do them:

• One camp says that we should always set cmi.exit to normal upon completion of the SCO. This camp says that if we set cmi.exit to suspend upon completion, we are assuming that the learner has exited with the intent of returning to the SCO at a later time, and that it isn't fair for us to make this assumption. This camp also says that if we were to always set cmi.exit to normal upon completion, it would make it easier for the LMS to know that it should start a new attempt the next time the learner accesses the SCO.
• Another camp says that setting cmi.exit to suspend will ensure that the current attempt is preserved and the run-time data is not reset the next time the SCO is launched. In order for bookmarking to work, content must be exited in a suspended state. In contrast, if cmi.exit is set to normal, the learner's attempt ends, and the run-time data of the current session will not be available if the SCO is relaunched. In other words, if we want to allow the learner to resume a completed course, we must use suspend.

Essentially, by always setting cmi.exit to suspend, we've gone with the method that we feel offers the most flexibility to the LMS. This way, if the LMS offers the option to start a new attempt each time, they can go ahead and do that. If we were to always set cmi.exit to normal upon completion, we might force the LMS to start a new attempt next time, but customers with different requirements would never be able to allow their learners to resume a completed course.

I hope that helps. Have a great day!