Prompt to Resume in LMS

Hello,

The course we've built will not prompt to resume when restarting from our LMS.

We have tried our module in a neutral LMS called Moodle, and the prompt to resume feature worked, but the exit trigger did not. In order to get the exit button to work in our LMS, we had to change the Configuration.js settings. I can elaborate more on this if necessary.

The only way we can get the prompt to resume function to work from our LMS is if we set the Articulate settings to "Launch in a New Window". The steps this takes, then, are that the user clicks on the module from our LMS site, which opens a new "Launch" window. From the "Launch" window, the user clicks the "Launch" button and a second window opens in which the module plays. The user can exit out from the module window, and then restart by clicking on the "Launch" button on the "Launch" window. If the user does this, then the prompt to resume function works. 

However, if the user exits/closes out of the module window and the "Launch" window, when the module starts again (after the user clicks on "Launch" from the "Launch window") the module immediately starts from the very beginning.

Others who use our LMS and use Articulate are able to launch their module without a "Launch" page and also have the "Prompt to Resume" function. Therefore, it's not our LMS.

Any ideas?

Thank you,

Sara

7 Replies
Ashley Terwilliger

Hi Sara,

You mentioned you were able to get it to work in Moodle - but not your LMS, that would indicate it's more likely an LMS issue than with the file? I can't speak to the changes you've made to the configuration.js file, as we don't support modifications to the published output - but if you know of others who are using your LMS and the "prompt to resume" you may want to reach out to them specifically. Have you alread connected with your LMS team to see if they had any suggestions? 

Marc Lee

This is an old post but I just posted pretty much the same issue, only in my case, it's actually Moodle (or a version of it) where the problem exists,  In my case, if you launch in a separate window and retain the launch window (as Sara describes), resume always works.  If you close both the player window and the launch window, it works every other time....tries #1, 3, 5 etc work; tries #2, 4, 6, etc restart the course from the beginning.

I'm wondering if this is related to file size of suspend data file.

Ashley Terwilliger

Hi Marc,

If it were the suspend data I would suspect it to happen continuously after the first time it occurred - as if you've hit the data limit, and start over, proceed past the point where you left off last time you'd still be over the data limit. If that makes sense. 🙃

Are you also customizing the configuration.js file like Sara was? You may also want to look at testing this in another environment such as SCORM Cloud. 

Ashley Terwilliger

SCORM 2004 does have more resume data available. A decent amount more. Now I wonder...

On all your attempts were you leaving at the same spot - or was the 2nd attempt picking up from the first? Meaning that it would reach the limit sooner than the 1st attempt? Then on the 3rd attempt it's a reset because you'd already met the data limit, and so on...

Marc Lee

When I put the module in debug mode, a whole different set of circumstances emerged.  I can see the suspend data being sent and it's clear the amount of data is not exceeding the SCORM 1.2 limit.  What I am seeing is inability of the module to send suspend data at all after resuming once. After resuming successfully and then closing the debug trace shows the following in the last few lines....

---------------------------------------D E B U G   T R A C E--------------------------------

290:Tue May 02 2017 16:19:00 GMT-0600 (Mountain Daylight Time) - In SCORM_CallLMSFinish
291:Tue May 02 2017 16:19:00 GMT-0600 (Mountain Daylight Time) - In SCORM_GrabAPI
292:Tue May 02 2017 16:19:00 GMT-0600 (Mountain Daylight Time) - SCORM_GrabAPI, returning
293:Tue May 02 2017 16:19:00 GMT-0600 (Mountain Daylight Time) - Calling LMS Finish
294:Tue May 02 2017 16:19:00 GMT-0600 (Mountain Daylight Time) - strResult=true
295:Tue May 02 2017 16:19:00 GMT-0600 (Mountain Daylight Time) - Returning True
296:Tue May 02 2017 16:19:00 GMT-0600 (Mountain Daylight Time) - Returning true
297:Tue May 02 2017 16:19:00 GMT-0600 (Mountain Daylight Time) - In SetScore, intScore=0, intMaxScore=100, intMinScore=0
298:Tue May 02 2017 16:19:00 GMT-0600 (Mountain Daylight Time) - In ClearErrorInfo
299:Tue May 02 2017 16:19:00 GMT-0600 (Mountain Daylight Time) - In IsLoaded, returning -false
300:Tue May 02 2017 16:19:00 GMT-0600 (Mountain Daylight Time) - In SetErrorInfo - Num=7 Desc=Cannot make calls to the LMS before calling Start
301:Tue May 02 2017 16:19:00 GMT-0600 (Mountain Daylight Time) - In Unload
302:Tue May 02 2017 16:19:00 GMT-0600 (Mountain Daylight Time) - In ClearErrorInfo
303:Tue May 02 2017 16:19:00 GMT-0600 (Mountain Daylight Time) - In ExecFinish, ExiType=SUSPEND
304:Tue May 02 2017 16:19:00 GMT-0600 (Mountain Daylight Time) - In ClearErrorInfo
305:Tue May 02 2017 16:19:00 GMT-0600 (Mountain Daylight Time) - In Unload
306:Tue May 02 2017 16:19:00 GMT-0600 (Mountain Daylight Time) - In ClearErrorInfo
307:Tue May 02 2017 16:19:00 GMT-0600 (Mountain Daylight Time) - In ExecFinish, ExiType=SUSPEND
308:Tue May 02 2017 16:19:00 GMT-0600 (Mountain Daylight Time) - In ClearErrorInfo
309:Tue May 02 2017 16:19:00 GMT-0600 (Mountain Daylight Time) - In Unload
310:Tue May 02 2017 16:19:00 GMT-0600 (Mountain Daylight Time) - In ClearErrorInfo
311:Tue May 02 2017 16:19:00 GMT-0600 (Mountain Daylight Time) - In ExecFinish, ExiType=SUSPEND
312:Tue May 02 2017 16:19:00 GMT-0600 (Mountain Daylight Time) - In ClearErrorInfo
313:Tue May 02 2017 16:19:00 GMT-0600 (Mountain Daylight Time) - In Unload
314:Tue May 02 2017 16:19:00 GMT-0600 (Mountain Daylight Time) - In ClearErrorInfo
315:Tue May 02 2017 16:19:00 GMT-0600 (Mountain Daylight Time) - In ExecFinish, ExiType=SUSPEND
316:Tue May 02 2017 16:19:00 GMT-0600 (Mountain Daylight Time) - In ClearErrorInfo

-----------------------------------------------------------------------------------------------------------------

The highlighted line is what I am focusing on.  From what little I know about his message it appears to mean that the connection with the LMS has failed to take place on resuming.  Hard to say: this error is found many places in the API.js file.

I realize this has been discussed before but if anyone has resolved this issue or just add any insight as to what is going on here. 

Questions to answer:

-1-I believe we're launching from an html5 index not story,html.  Is this an html5 issue?

-2-Is this a possible bug in the LMS, which is Learnit (a customization of Moodle)

Thanks, everyone, in advance.

-Marc Lee

Ashley Terwilliger

HI Marc,

It could be a lost connection - but reading debug logs is not my speciality. If you'd like, I'd be happy to open up a case to get you working with our Support Engineers (or use that link to send them your files) and they'll be able to test the course in SCORM Cloud as well. It's a good way to confirm if it's an LMS specific issue or something in the file. 

I'd also recommend launching from the index.html for an LMS course - and then depending on the browser individuals are using, they'll be presented with the Flash or HTML5 output. 

Just let me know how you'd like to proceed!