Incomplete/Complete - Passed/Failed

Hi George.

In the publish window you have the option to open the folder that contains your published output. I would do that, keeping the publish window open, modify the files and then choose the zip option after you are done modifying the files.

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.

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.

I just use Wordpad each time before zipping, simple enough.

Bruce

Well, that explains some oddness when trying to get completion status stuff to work correctly in Moodle.

Are you adding the content as a new course so that you aren't viewing a cached version? I haven't personally tried the workaround that was mentioned here but someone who has might want to look at your files or offer the files they modified to you.

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.

HI Jennifer

Yes - this is known, (hence this thread).

No fix currently - you need to correct the code in the 4 x JavaScript files - very simple really - just like editing a Notepad/Wordpad document.

Bruce

Hi Jennifer.

If you hold on, I have requested my team to set this up so all you have to do is use the files we supply you. So if you can please be patient we should have something posted here by the end of the day.

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!

Yep. We will have something for you soon.

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!

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

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

You are correct. You should be able to insert it into all courses (SCORM 1.2) and it will work as the screencast mentions.

Adrian

Thanks all!  I'm just polishing off an internal document about best practices for Storyline publishing/testing and I'll add this info to that.

Great news and a nice n easy fix.

Jennifer

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?

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?

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.

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!