New client LMS requirements

Sep 03, 2014

A client just a sprung a new LMS requirement on the SCORM courses we create for them; If an LMS connection interruption occurs after the course has already been launched, the course needs to recognize this and should not advance. Are there Publish settings for this? Or some code we can insert somewhere in the output files?

Thanks,

Ben

2 Replies
Steve Flowers

It's possible to handle this at the content end. In fact, in many cases you can notify the user more gracefully and accommodate some nifty use-cases with a SCORM content connection detector deployed within the content itself:

https://community.articulate.com/discussions/articulate-storyline/possible-to-detect-if-course-launched-via-scorm#292883

It's really pretty simple and flexible and doesn't rely on the method the LMS uses to check heartbeat (they don't all do it). And if you're looking for a content connection to the internet connector:

https://community.articulate.com/discussions/articulate-storyline/internet-connection-detection-plugin

One cool thing you can do with the LMS connector is deploy the same published package and shape the flow of the course / response block if it's not going to be tracked. Depending on your LMS, this could enable you to deep link to your content without an LMS login to use the very same content as performance support or an on-the-job resource.

This discussion is closed. You can start a new discussion or contact Articulate Support.