Regression Issues

I have a client who has asked me to build a rather large course for them and publish to SCORM. The total amount of slides is 500, with audio found on almost every slide.

They are facing a lot of issues where the data is not saving, and the users progress is regressing. The regression is never all the way to the beginning of the course, but back to some random section. The regressions takes place when the learner exits and reopens the course. Each section needs to be viewed in order so when they close the course and reopen the course, it acts as if the last 3 or 5 or however many sections were never viewed.

I have not had the same issues with other LMS' I use, such as SCORM Cloud or TalentLMS. I have published to both SCORM 1.2 and 2004 4th edition. 

SCORM 2004 seemed to have less issues, but still some of the users in their LMS are suffering from progress regression.

I have a feeling a large part of the problem is the LMS the client is using. The LMS is called Axcelerate. Problem is the support team at Axcelerate don't seem to understand their own platform and just outsource the issue to a SCORM consulting company where the issues are obviously not replicated because they use a totally different LMS....

If anyone has any suggestions please let me know. Even if it is a setting change we should make on the LMS. Attached is a 1 slide example of the module where you can view the publish settings we are using. 

4 Replies
Joseph Francis

Thinking about the learner's experience, a 500-slide with audio course is a significant amount of time they would need to set aside.

Could the course be broken into chapters which are individual SCORM files? You could either deliver them as a Multi SCO (using a tool like Adobe's Multi SCO Packager, which is tucked in with Captivate) or create a many SCO course that the LMS delivers as "chapters" within the course shell.

Matthew Adams

Hi Joseph,

Thanks for your comment. The module is split into 26 sections. It is the clients wish that all content is placed into one module. The intent is not that the user completes the module in 1 sitting. It is roughly a 4 hour course.

However, when the user exits the course and then reopens it later that day/week, there is a regression. What makes the regression weird is that it doesn't start back from the beginning, but instead will wipe several sections, and pretend that the user only made it 30% through the course, instead of being 60% through the course when they exited.

Due to the chosen LMS, splitting the course into 26 separate SCORM files is an awkward solution, and not preferred. I am also not familiar with Multi SCO tools. Is there one compatible with Articulate?



Joseph Francis

Ugh, a 4-hour eLearning course is brutal enough, having to complete it in one sitting would be borderline-sadistic.

One train of thought is that the connection to the LMS may be timing out. You could keep it "alive" by sending a regular "ping" to the LMS from within Storyline using JavaScript. If you have the course broken into scenes, on the last slide of each scene, insert this JavaScript in a new Trigger (after creating a new Storyline text variable titled lmsStatus):

var player = GetPlayer();

function findLMSAPI(win) {
     if (win.hasOwnProperty("GetStudentID")) return win;
     else if (win.parent == win) return null;
     else return findLMSAPI(win.parent);
var lmsAPI = findLMSAPI(this);

var lmsStatus = lmsAPI.GetStatus();
player.SetVar("lmsStatus", lmsStatus);

A Multi-SCO packager allows you to take individual modules which have been published and ZIPped as SCORM and combine them into a single deliverable. You can then either force the learner to go though the modules in sequence, or allow them to go through the modules in whatever order they wish (similar to an LMS where multiple SCOs are delivered in a curriculum; the learner is either required to go through them in sequence or in any order).

Adobe Captivate includes a Multi-SCO Packager. I've also seen one from JCA Solutions (now part of Rustici) called Simple SCORM Packager. Both are development tool-neutral, which makes it easy to combine SCOs which were created in different tools. As long as they're all the same version of SCORM, and have a standard manifest file, you can create a Multi-SCO course.

Katherine Willis

Hi MAtthew, I'm about to publish a similar course onto aXcelerate and have not successfully been able to get the course to mark as complete. Did you experience the same problem? If so, were you able to come up with a fix? I'm publishing to Tin Can but could choose 2004 or 2001. They're not ready to start reading tin can data at this organisation yet.