Issue with LMS Commit

Hi guys,

Wondering if anyone has experienced the same or similar issue?

  • We have a client where we have forced their packages to run on html5.
  • The client is using a Success Factors LMS. They having trouble in IE9 and Google Chrome of the package recording a result in the LMS.
  • The scenario involves completing the course for the first time and failing the test, then hitting the (custom) RETRY button.  When you attempt the test again, no matter what score you get(Pass, Fail), no score is recorded in the LMS.  If you close the test and re-initialise from the beginning, then go to the test and complete it, the score is recorded correctly (Pass, Fail)
  • We have tested this in Scorm Cloud and can't replicate the issue. However we tested this in ADL Test Suite and can replicate this issue.

My questions:

Where in the Storyline 2 package does the LMS commit signal come from and what happens with a retry button?

Also forcing the package to run html5 only has made drag and drop interactions buggy and gifs that you can click on are now no longer clickable. Why would this happen?

Thanks

Amy

5 Replies
Ashley Terwilliger

Hi Amy,

Thanks for reaching out here - and I hope folks from the community who also use Success Factors are able to chime in here, as if it works in SCORM Cloud than it may be something specific within your LMS. You could look at enabling LMS debug mode to see when and how the data is being passes back and forth between the two environments. 

Also, you mentioned the HTML5 output and using IE9, and I just wanted to offer a reminder that it isn't a supported browser per our requirements here. 

Amy Price

Hi Ashley,

The thing is Scorm Cloud is a pretty forgiving LMS. ADL Test Suite is a more rigorous LMS and this is where we could replicate the issue. 

Basically each time the retry button is clicked Storyline is not re-committing the result to the LMS. However if the user retries and fails and closes the module down, then a result is recorded. However a user should be able to retry, retry and retry and the failed result record each time.

We will try the enabling debug mode, but is there any way to force the LMS commit signal or manually invoke the LMS result call?

 

Thanks

Amy 

Amy Price

Hi Ashley,

Thank you for your help, but isn't this a bug that Storyline can look into? The file should be committing a result every time the user is retrying. Seems to be only an issue in html5. 

It works in flash correctly. The other thing is I thought Storyline is meant to switch between html5 and flash depending on the users environment settings and Storylines compatability with browsers? But the those all the correct settings then html5 should work as flash does.

Does that make sense? 

Amy 

Ashley Terwilliger

Hi Amy,

You mentioned it working in SCORM Cloud, which is the industry standard we defer to. If you have debug logs of your LMS and SCORM Cloud, we're happy to take a look and help compare. You'll also want to make sure you're using a supported HTML5 browser which if you're only seeing this in IE9, is not something we offer support for. 

Storyline will show the Flash or HTML5 output based on how the user accesses the course as described here. There was a previous issue that has since been fixed in Storyline 2, where resuming a course on an iPad that was started on a desktop caused some issues with states in the course - so if you're running into issues with resuming elements you'll also want to confirm that you're using the latest update of Storyline 2, Update 7.