Articulate SCORM 1.2 module and behavior

This isn’t really going to help your current situation, but I would advise dropping SCORM and moving to xAPI. We had no end of trouble with completion and navigation of SCORM materials. So much less with xAPI.

Thanks for the prompt reply.

If we compile it as XAPI , would we require a LRS or can XAPI  report to the LMS ?

Thanks Maz

I’ve had no problems reporting to ARICademy. I do use Storyline not Rise to create my xAPI’s tho, so you may wish to do some tests before jumping in to make sure it is tracking everything you want.

If you choose to stick to SCORM……

I noticed with Rise when it first came out that if I have a long content block, the auto scrolling didn’t always behave. So I now put continue buttons instead of relying on the auto scroll. I also chunk up the content into more sections to avoid having too long of a section.

You may also have implemented all of these, but just in case.

https://help.rise.com/en/articles/2066420-control-course-navigation

@RKB Can you provide a screen shot of your publish settings? Is there any commonality between the users with respect to

• Browsers that they use
• Pages that are getting missed
• Devices that they are using (computer vs. tablet vs. smartphone)
• Are they using the mobile app?
• Have you tried other Scorm versions?

Definitely happened more often on Chrome based browsers than Firefox, but it has happened on everything at some point.

Not sure what you mean by pages being missed.

Solely computer.

No mobile.

When we did use scorm, it was 2004 3rd Edition

I did determine that when it happened, the “completion” communication never made it back to the server but this was not consistent with any particular course or configuration.

We no longer use SCORM so I can’t give you anymore info than that.

This may not be impacting the skipped lessons piece, but if your courses are long, SCORM 1.2 does not save as much bookmark progress as SCORM 2004. You definitely want to move off of SCORM 1.2 for longer courses to ensure it will save progress for the whole length of the course.   

You wouldn’t need an LRS unless you want to keep all xAPI calls from all users for all courses in one singular place.  Docebo can handle the xAPI, it will just keep all the calls separate by user/course.

+1 for the SCORM 2004 having better behavior. Also, may not be relevant, but I have had previous experiences where audiences taking training that are regularly on a VPN have significant issues with course behavior including completion due to the restriction on tracking cookies used by the platform.

My experience (with a couple of different LMS platforms) is that problems such as these generally come down to the traffic on the “link” between the course, the LMS, and the user. Scorm 1.2 has less data, but it also takes less bandwidth. In my experience this has been the best solution for getting more courses to complete more frequently. Unfortunately, Scorm 1.2 doesn’t send over all of the data that we need for exams, so we have to use Scorm 2004/v3 in those cases. This means more bandwidth, and if the user has a dodgy setup (weak wireless, working over cellular, long periods of inactivity with the course open, browsers that try to monitor unsafe traffic, VPNs that don’t send cookies (thanks @Jenna M.) ), an LMS admin can go bonkers trying to figure out why persons can’t complete courses. I’ve never tried xAPI because I didn’t want to set up an LRS (thanks @Annarose.Peterson ) but I’m going to try that next.

Right now, I support my users, where I can, by simply completing courses manually for them. (Of course, I can’t do that for compliance courses). If I can’t complete manually, then I reset the course/training material/enrollment and suggest a wired network connection, a single “sitting” to complete the course, and working in an incognito window. I also ask the person to send me a screen shot of whatever “course complete” screen is in the course so if push comes to shove I can document that bit.

We switched to SCORM 2004 a few years ago. It allows separate completion and success tracking. For example, if a user viewed all videos in your module, but failed the test, the module can report itself as Completed but Failed whereas, with SCORM 1.2, it could only be reported with one status.

With SCORM 2004, the suspend data limit was increased to over 60,000 characters which allows us to build longer packages with more complicated interactions. It also increases consistency in learner progress being tracked (bookmarking where they are in the course) for larger packages.

I saw inconsistent behavior with my SCORM 1.2 courses but then found that I had not turned the Exit Link on when publishing.