Experiencing cmi.core.exit Issue After Update
Jul 09, 2020
Hi there. We're using Storyline 360 and publishing to Saba Cloud. There has always been an issue with Saba not recieving the correct data telling the LMS that the course has been completed, hence the "suspend" you will see below:
Command Received = LMSCommit
Data sent by content to Saba LMS:
cmi.core.lesson_status = passed
cmi.core.lesson_location =
cmi.core.exit = suspend
cmi.core.score.raw = 84.21
cmi.core.score.max = 100
cmi.core.score.min = 0
We had been using a patch to fix this issue since 2017 and can be found here.
Since the most recent update, that patch no longer fixes the issue and we are back to the Suspend problem. Other notes in case someone asks: It does not occur in SCORM Cloud, this is a SABA>Storyline-only issue as far as I know. Completion is based on slide views which we have tried moving down to even just 1 slide to test and the issue persists.
Does anyone have any ideas?
4 Replies
Hello Chris,
I believe storyline is now using scormdriver.js instead of SCORMFunctions.js
I made the same change to the scormdriver.js file
I can't test this out because I don't have Saba.
Try replacing the scormdriver.js file with this one.
Thank you, I will try that and report back. Might take a few because I have to get someone from IT to do it because they hold Admin privileges.
12 Days later, our IT finally added the modified scormdriver.js file, and it worked! Thank you very much!
I'm glad that it worked. Enjoy the rest of your day.
This discussion is closed. You can start a new discussion or contact Articulate Support.