Missing SCORMfunctions.js file
Jun 03, 2020
Hi everyone,
We are still using the december revision of storyline (3.35....) because of all the trouble with accessibility.
Today, when working with a client who updated to the latest version, we noticed some issues with completions status in our LMS (which is SABA). When we looked we noticed that the SCORMfunctions.js file seems to be missing in the files published via the newest revision (3.40).
I tried to publish with passed/incomplete which is our usual made of completion whether its slide count or a quiz. I also tried completed/incompleted and it had no effect.
Has anyone else seen this? Does anyone else know more about this?
To be sure: it seems that the course was triggering a complete BEFORE it should, which is obviously not at all optimal for all the obvious reasons.
7 Replies
Hi Seth,
Thanks for reaching out! We simplified the published output in Storyline 360 builds 3.39.21985.0 and later. We combined the following JavaScript files from older versions of Storyline 360 into a single scormdriver.js file.
• AICCFunctions.js
• API.js
• APIConstants.js
• Configuration.js
• lms.js
• LMSAPI.js
• NONEFunctions.js
• SCORM2004Functions.js
• SCORMFunctions.js
• UtilityFunctions.js
You can still modify your published output as you did before. You'll find all the same code from the legacy files above in the new scormdriver.js file.
Leslie,
I'm using Storyline 3 update 11 and recently discovered the new scormdriver.js file. I'm a bit confused because the separate javascript files are still in the lms folder alongside the new one. Are these separate files still used? Or just leftover?
I'm just wondering because some of the support articles say to make changes in both Configuration.js and scormdriver.js when needed. I have to modify a few things to get Storyline courses to work with our LMS, and if I only need to worry about scormdriver.js, then I'd prefer to not have to mirror everything over to the other files.
Hello Chad!
I'm happy to help! I see this in the LMS folder: link I've published a course from Storyline 3 update 11 as well.
It sounds like you might be seeing something different. If that is the case, I'd like to enlist our Support Engineers to help! Use this link to connect with a Support Engineer so that we can see exactly what changes need to be made to make sure your courses work as expected in your LMS.
Lauren,
Thank you for the info. Unfortunately I wasn't clear about which lms folder I was talking about. I was referring to the lms folder in the installation directory. I can confirm that upon publish, only the scormdriver.js file makes it to the published output lms folder. I'm just wondering if the other files in the installation directory lms folder serve any purpose because some of those support articles I linked above mention both the old files and the new consolidated scormdriver.js file.
Hello Chad!
Thank you for those extra details! You should only need to customize the scormdriver.js file rather than our previous method of customizing both scormdriver.js and configuration.js.
Let us know if you run into any snags!
Thanks, Lauren!
Lauren,
I'm trying manually via javascript on a button, write cmi.interaction parameters to SCORM Cloud. Can you tell me why the SetScore() function works fine and yet the SCORM_GrabAPI(); function returns null?
I've tried SCORM_objAPI.LMSInitialize(); and SCORM_CallLMSInitialize(); and keep hitting a dead end. I know an API connection to SCORM Cloud exists (or SetScore wouldn't work), so why wouldn't other SCORM2004 functions work?
Thanks