Incomplete/Complete - Passed/Failed

Hi,

I have had 2 x instances today where I have compiled SL courses to "Completed/Incomplete" based on slide completions, and the clients have told me their LMS is seeing "Passed/Failed".

Is this something that other people have seen, and what's the best way to try and sort this?!

Is this likely to be LMS issues?

Bruce

79 Replies
Justin Wilcox

Also, if you didn't want to change the files every time you could simply copy the files from these folders:

C:\Program Files (x86)\Articulate\Articulate Storyline\Content\lms

and here:

C:\Program Files (x86)\Articulate\Articulate Storyline\Content\mobile

Modify those and then simply swap the files when you are done publishing.

Gerry Wasiluk

George Milton said:

Hello all!  Having the same challenge. 

Bruce - if I am zipping up the program to upload into the LMS can I still edit the files you identified while zipped?

Thanks for the help!


FYI:  If you open a zip archive with 7Zip, you can make simple edits to files while looking at the files in the 7Zip interface.  Just right-click on a file and choose Edit.

I only do this in an emergency.  Mostly I do Justin's method.

Jennifer St. George

Hi all,

I'm find this with all my Storyline published courses -- I tick complete/incomplete during publishing to report to the LMS and instead I end up with Incomplete or Passed or the dreaded Failed.

Uh yeah, I'm not at all comfortable opening anything and fussing with code.  Any ideas?  We're a Moodle house too.

Jennifer St. George

Justin if it means I can avoid going into the dark places (JavaScript files) I am ALL OVER holding up. 

I'll go have a cuppa now and return to importing the 25 languages (yes I really said 25) into my English master Storyline file and doing QA for the rest of the day.

Ahhh, the life of a Storyline developer.  You tell them you can handle translations and they go bonkers!

Justin Grenier

Good Afternoon, Jennifer.

Here's a quick Screencast on how to work around the problem:

For your convenience, the modified, zipped SCORMFunctions.js file is attached to this post.  You need only extract the file and place it in the \lms\ folder within your published output folder before zipping it and uploading to your LMS.

Please let us know if you have any other questions.  Thanks!

Bruce Graham

Justin,

Thanks for this.

For my "solution" (successful so far), I did this replacement in SCORMfunctions.js AND lms.js, AND SCORM2004Functions.js AND mobile > Storyline-compiled.js.

Please confirm that we ONLY need to alter this ONE LINE in ONLY the SCORMFunctions.js file.

I was just following the lead of an LMS supplier - so I have no clue what needs doing!

Appreciate your earliest confirmation.

Many thanks

Bruce

Bruce Graham

Adrian Dean said:

Hi Bruce,

From our testing, only the one line is necessary.

Adrian

Thanks - so basically the one file never changes per course, and can be inserted as a "cookie-cutter template" into all courses, or must we edit each file every time we publish?

Sorry for pushing the point, but I/we need to be absolutely sure this works.

Thanks

Bruce

Gerry Wasiluk

Justin Grenier said:

Good Afternoon, Jennifer.

Here's a quick Screencast on how to work around the problem:

For your convenience, the modified, zipped SCORMFunctions.js file is attached to this post.  You need only extract the file and place it in the \lms\ folder within your published output folder before zipping it and uploading to your LMS.

Please let us know if you have any other questions.  Thanks!


Hey, Justin!

How about for Saba users with SCORM 1.2?  You already have a replacement file for completion needs:  http://www.articulate.com/support/kb_article.php?product=st1&id=hd0cc4e9mgvm

Will that version get the new fix also?

Justin Wilcox

Hey Gerry.

We will need to figure out what the permanent fix is going to be and then we can roll out an updated file, if necessary for that article. This is kind of a band aid solution until we get Update 3 out the door. Based on what Justin modified, this doesn't look like it will be what the permanent fix is but should work if you are experiencing this issue. 

Gerry Wasiluk

Justin Wilcox said:

Hey Gerry.

We will need to figure out what the permanent fix is going to be and then we can roll out an updated file, if necessary for that article. This is kind of a band aid solution until we get Update 3 out the door. Based on what Justin modified, this doesn't look like it will be what the permanent fix is but should work if you are experiencing this issue. 


Thanks, Justin!

Or should that be Justins?

Nancy Woinoski

Adrian Dean said:

Hi Bruce,

From our testing, only the one line is necessary.

Adrian


Hey Adrian - just to make this perfectly clear - Can you confirm that you only need to make this adjustment if you are trying to send the Completed/Incomplete status to your LMS.    

Also, I was going to ask if you needed different versions of the js file for different language translations but then took a look at the file and realized those strings do not get translated. This my be a red herring but if I published a course in French shouldn't those strings be in French?

Justin Wilcox

Nancy Woinoski said:

Adrian Dean said:

Hi Bruce,

From our testing, only the one line is necessary.

Adrian


Hey Adrian - just to make this perfectly clear - Can you confirm that you only need to make this adjustment if you are trying to send the Completed/Incomplete status to your LMS.    

Also, I was going to ask if you needed different versions of the js file for different language translations but then took a look at the file and realized those strings do not get translated. This my be a red herring but if I published a course in French shouldn't those strings be in French?


You only need to make this adjustment if your LMS is having an issue with the way Storyline is communicating complete status. Not everyone will need to do this. This is only if your LMS and Storyline are not playing nicely together.

You don't need to alter those files for different languages.

Gerry Wasiluk

Bruce Graham said:

Adrian Dean said:

Hi Bruce,

From our testing, only the one line is necessary.

Adrian

Thanks - so basically the one file never changes per course, and can be inserted as a "cookie-cutter template" into all courses, or must we edit each file every time we publish?

Sorry for pushing the point, but I/we need to be absolutely sure this works.

Thanks

Bruce


Hey, Bruce!

So far the interim fix is working great in testing with my client's Saba system. 

From a Saba tool for testing content:

Justin Wilcox

Gerry Wasiluk said:

Bruce Graham said:

Adrian Dean said:

Hi Bruce,

From our testing, only the one line is necessary.

Adrian

Thanks - so basically the one file never changes per course, and can be inserted as a "cookie-cutter template" into all courses, or must we edit each file every time we publish?

Sorry for pushing the point, but I/we need to be absolutely sure this works.

Thanks

Bruce


Hey, Bruce!

So far the interim fix is working great in testing with my client's Saba system. 

From a Saba tool for testing content:


Sweet! Glad we were able to get this to you guys before the weekend!