Is it possible to install an older version of Storyline 360 build 3.38, build 3.39 onwards the content is changed in the zip file. Since the current version, it is not tracking in Saba LMS. The Saba expects "cmi.core.exit =" is left to blank not "cmi.core.exit=suspend" status in the content upon completion.
Would be great if anyone could resolve this issue.
You can reach out to our support team here to request for the installer for Storyline 360 Build 3.38.21861.0, but I should warn you that this version is 2 years old, and will not have the performance improvements and bug fixes included in the most recent version. I'd first recommend working with our support engineers to see if there is a better solution to downgrading your installation to an outdated version.
Alternatively, you can also try modifying the scormdriver.js file in your published output to see if this helps. Here's how:
8) Go back to the Publish Successful window and click Zip, then upload the zip file to your LMS for testing.
If the modified version works on your LMS and you’d like to apply this change every time you publish, you can edit Storyline 360's SCORM Driver template (scormdriver.js) in the following installation directory:
Is there a setting inside of Articulate that can set the Suspend to a null value instead of having our instructional designers do the swap out with the modified scormdriver.js file? This workaround works but its very confusing when an update occurs (as needed by the instructional designer) and then replacing the source file on the c: drive. Thank you
I'm happy to chime in! Glad to hear that this workaround works for you. There is no setting in Articulate 360 to set the suspend value automatically. I'm curious to find out if other E-Learning Heroes community members with the same concern have other suggestions!
Thank you for the reply. Would it be possible to add a trigger to execute JavaScript to send over a cmi.core.exit as a null value to override the "Suspend" that it is currently in the scormdriver.js?
5 Replies
Hello Balaji,
You can reach out to our support team here to request for the installer for Storyline 360 Build 3.38.21861.0, but I should warn you that this version is 2 years old, and will not have the performance improvements and bug fixes included in the most recent version. I'd first recommend working with our support engineers to see if there is a better solution to downgrading your installation to an outdated version.
Alternatively, you can also try modifying the scormdriver.js file in your published output to see if this helps. Here's how:
1) Publish your course for LMS distribution, then click Open Folder on the Publish Successful window.
https://community.articulate.com/series/articulate-storyline-360/articles/storyline-360-publishing-a-course-for-lms-distribution
2) Open the lms folder in your published output.
3) You'll see a scormdriver.js file. Open the file in a text editor, such as Notepad.
4) Find this line of text:
blnResult = SCORM_CallLMSSetValue("cmi.core.exit", SCORM_TranslateExitTypeToSCORM(strExitType)) && blnResult;
5) Add double forward slashes (//) at the beginning of the line:
//blnResult = SCORM_CallLMSSetValue("cmi.core.exit", SCORM_TranslateExitTypeToSCORM(strExitType)) && blnResult;
6) Add the following below this code:
blnResult = SCORM_CallLMSSetValue("cmi.core.exit", "") && blnResult;
7) Save and close the file.
8) Go back to the Publish Successful window and click Zip, then upload the zip file to your LMS for testing.
If the modified version works on your LMS and you’d like to apply this change every time you publish, you can edit Storyline 360's SCORM Driver template (scormdriver.js) in the following installation directory:
32-bit: C:\Program Files\Articulate\360\Storyline\Content\lms
64-bit: C:\Program Files (x86)\Articulate\360\Storyline\Content
Note: updating or reinstalling the app will reset these changes.
Let me know if this works for you!
This resolves the issues. It is working as expected. Thanks a lot, Joe :) For your quick response.
Hi Joe,
Is there a setting inside of Articulate that can set the Suspend to a null value instead of having our instructional designers do the swap out with the modified scormdriver.js file? This workaround works but its very confusing when an update occurs (as needed by the instructional designer) and then replacing the source file on the c: drive. Thank you
Hi Kelly,
I'm happy to chime in! Glad to hear that this workaround works for you. There is no setting in Articulate 360 to set the suspend value automatically. I'm curious to find out if other E-Learning Heroes community members with the same concern have other suggestions!
Hi Eric,
Thank you for the reply. Would it be possible to add a trigger to execute JavaScript to send over a cmi.core.exit as a null value to override the "Suspend" that it is currently in the scormdriver.js?