Rise course not resuming
Oct 21, 2020
I understand that Rise 360 courses exported to LMS should always resume, there's no option on exporting not to, and that's what we want. I run a test course in Scorm cloud and it resumes fine, I can see GetValue called for cmi.location and cmi.suspend_data in the debug log. We're exporting to Scorm 2004 2nd edition.
However we are writing our own LMS to host the content its not resuming as we want. On debugging we're finding that's probably because GetValue is not called by the course for cmi.location or cmi.suspend_data, which we've persisted to supply when requested but it never is. Debug on revisiting the course is basically this sequence:
InitializeGetValue: cmi.success_status = unknownGetLastError = 0GetValue: cmi.completion_status = unknownGetLastError = 0SetValue: cmi.completion_status: incompleteSetValue: cmi.exit: suspendGetValue: cmi.mode = normalGetLastError = 0
which matches what Scorm cloud has but then that's getting GetValue called for cmi.location and cmi.suspend_data, but we're not. The course hasn't been changed between visits.
Could anyone offer any explanation or advice?
We're evaluating Articulate and are pretty close to purchasing it to embed learning content into our software but if we can't suspend and resume course progress, we may have to look elsewhere.
7 Replies
I've had some success resuming to the last lesson visited (by setting the initial url bookmark using the persisted
cmi.location), but thecmi.suspend_datastill isn't being asked for, so all progress is lost.Which LMS are you using?
The fact that it resumes on SCORM cloud may indicate an issue with your LMS.
Resume works perfectly on our LMS, so it's not a general problem with Rise course that you are seeing.
We are writing our own LMS. We persist cmi.suspend_data to supply to the course when it asks for it, but for some reason it's not asking, so really I'm asking under what circumstances would a course NOT ask an LMS for cmi.suspend_data ?
Hi Jeremy!
In your testing, how are you closing the course? Are you manually closing the browser window, or are you clicking an Exit Course button within the course?
Also, does this problem happen in any browser you test?
Hi Alyssa, thanks for replying.
The browser is actually a WebView in a mobile app on iOS, so its Safari. It's been problematic getting the Commit & Terminate API methods to be called by the course because the browser is not 'closed' in the traditional sense, though we have tried an Exit Course button which does call Commit and Terminate, but that didn't seem to affect our ability to resume afterwards.
I have found out why. I was building a new index.html for the app and I wasn't initiating the Scorm API discovery in the right place - has to be after the scormdriver script was loaded (obviously) but crucially before the body script in the scormcontent index.html. I was doing it after the latter, by which time the initiation of the cache was tried & failed.
Hi Jeremy, great job in fixing your Rise course! Thanks for sharing the solution here!
This discussion is closed. You can start a new discussion or contact Articulate Support.