We have a lengthy (1 hour+) eLearning course coded in SCORM 1.2 and that we host on an LMS. We're having an issue where the LMS will only track an attendees progress if they click on a gray "X" in the upper right hand corner of the screen. The "X" is part of the LMS and not our SCORM file. This raises the issue of an attendee losing all of their progress if they lose internet connectivity or they forget to click on the "X."
Is there any way we could set it so that the LMS automatically records an attendee's progress for each slide that they complete? Perhaps by incorporating whatever code is in the "X" into a button in Storyline?
I would reach out to your LMS and find out their system's capabilities. I'm thinking it may be specific to their progress tracking (or lack of) capabilities
Looks like Brian has popped in to assist you here. A great test would be to see if you can recreate the issue via SCORM Cloud. This helps identify if the issue lies within the course or the LMS.
As the maker of an enterprise LMS that hosts Storyline files in our learning Modules, we've encountered a new issue where our TinCan parser, which works flawlessly with Storyline v2.9, is now squawking about the extensive changes in v3.6 (storyline 360). We're currently debugging it.
The 360 content files do play just fine in the SCORM cloud, so we know it's not something "wrong" with them... it's the v2 parsers and logic that has to be modified to support the scenario-based learning paths present in the newer 360 format.
Have you looked to enable LMS debug mode? That may help you spot something that could be different between the Storyline 360 or Storyline 2 versions. You could also take a look at what's being communicated in SCORM Cloud vs. in your LMS?
6 Replies
I would reach out to your LMS and find out their system's capabilities. I'm thinking it may be specific to their progress tracking (or lack of) capabilities
Hi Justin and welcome to E-Learning Heroes :)
Looks like Brian has popped in to assist you here. A great test would be to see if you can recreate the issue via SCORM Cloud. This helps identify if the issue lies within the course or the LMS.
Hi Justin,
As the maker of an enterprise LMS that hosts Storyline files in our learning Modules, we've encountered a new issue where our TinCan parser, which works flawlessly with Storyline v2.9, is now squawking about the extensive changes in v3.6 (storyline 360). We're currently debugging it.
The 360 content files do play just fine in the SCORM cloud, so we know it's not something "wrong" with them... it's the v2 parsers and logic that has to be modified to support the scenario-based learning paths present in the newer 360 format.
Any help appreciated!
Hi Paul,
Have you looked to enable LMS debug mode? That may help you spot something that could be different between the Storyline 360 or Storyline 2 versions. You could also take a look at what's being communicated in SCORM Cloud vs. in your LMS?
That's a great idea, Ashley, thank you -- it should help!
Let us know Paul!
This discussion is closed. You can start a new discussion or contact Articulate Support.