Storyline 2 Completed/Passed result

I have a Storyline 2 module built, the publish settings are set to 'Completed/Incomplete', yet when the module is completed it is giving me a result of 'passed'.

After going through this several times on a desktop browser and an iPad, I'm tearing my hair out trying to work out why it is pushing the wrong status. I had a quick look through the .js files built with the Storyline publish. I updated the SCORMFunctions.js as shown below.

On retesting the module, it is now showing as completed.

Why is this? Does Storyline 2 not push the correct status to the LMS? Is it a known bug?

Thanks.

Edit: This is with SCORM 1.2.

30 Replies
Chris Lambertus

Thanks so much for the response. Yes I understand that there is a solution.

My question was will this work if you edit the SCORM2004Function.js file the same way editing the SCORMFunction.js file does.
OR do you always have to edit just the SCORMFunction.js file?

Hope this helps clarify.

Vacation Alert: Friday July 29

Christine Lambertus | Designer | Career Learning Environment
Learning & Development | TD Bank Group
380 Wellington Street, 10th Floor, Twr B | London, Ontario | N6A 4S4
T: 226.927.8726

If you wish to unsubscribe from receiving commercial electronic messages from TD Bank Group, please click here or go to the following web address: www.td.com/tdoptout
Si vous souhaitez vous désabonner des messages électroniques de nature commerciale envoyés par Groupe Banque TD veuillez cliquer ici ou vous rendre à l'adresse td.com/tddesab

NOTICE: Confidential message which may be privileged. Unauthorized use/disclosure prohibited. If received in error, please go to www.td.com/legal for instructions.
AVIS : Message confidentiel dont le contenu peut être privilégié. Utilisation/divulgation interdites sans permission. Si reçu par erreur, prière d'aller au www.td.com/francais/avis

Leslie McKerchie

Hi Christine!

I will reach out to the team to inquire about your question and see if I can get an answer.

We don't support the modification of published output, so this is not something I'm super savvy at. I know I've never edited the SCORM 2004 file, but I don't publish in that format very often either.

Please note that replying to the forums via e-mail attaches your signature. You are welcome to pop in and edit if needed.

Leslie McKerchie

Hi Christine!

Just a follow-up. That specific documentation named the SCORMFunctions.js because the bug identified was only for SCORM 1.2.

If documentation was needed and it related to SCORM 2004, then that would be included.

If you are asking an 'in general' question about updating this file, then I imagine yes, but this is not something that we support.

Again, if you are having an issue related to what you have seen in this post, the fix is to install the latest update as it was corrected in Update 5.

Bastiaan Timmer

Maybe this is helpful. We created two Javascript scripts for sending the completion state to the LMS. We based our code on the SCORM2004functions.js and SCORMfunctions.js files:

It depends on which version of Storyline you are using. If you use the latest version, Storyline 360, then you might try the following Javascript code:

SCORM 1.2:

//get LMS API
var lmsAPI = parent;
//set score; the first number is the score
lmsAPI.SetScore(90, 100, 0);
//set status; possible values: "completed","incomplete", "failed", "passed"
//set status; possible values: "completed","passed", "icomplete", "failed"
SCORM_CallLMSSetValue("cmi.core.lesson_status", "complete");

SCORM 2004:

//get LMS API
var lmsAPI = parent;
//set score; the first number is the score
lmsAPI.SetScore(90, 100, 0);
//set status; possible values: "completed","incomplete", "failed", "passed"
SCORM2004_CallSetValue("cmi.completion_status", "completed");
SCORM2004_CallSetValue("cmi.success_status", "passed");

I've tested both script on SCORM Cloud and they are working as expected.

andrew daigle

Hi Bastiaan,

Thank you for sharing this script, but I am unable to get it to work. Short story shorter... I have a branching file and am trying to manually set completion at the end of each branch.

I'm running Storyline 3 (Update 4) and from reading a number of other posts, it appears update 3 (specifically the backwards compatibility patch for SL360 files) may have rendered this script invalid.

I'm using your SCORM 1.2 script. I have corrected the typo in the last argument "complete" - changed to "completed".

Have you experienced this? Do you have an updated script? Any suggestions?

Any help would be appreciated.