5 Replies
Ashley Terwilliger

Hi Peak,

Have you checked the folder mentioned, 

  • 32-bit: C:\Program Files\Articulate\Articulate Storyline\Content\lms
  • 64-bit: C:\Program Files (x86)\Articulate\Articulate Storyline\Content\lms

to see if the Saba Patch file is still located there? If not, it may have been removed as a part of your update so then you'll want to download (if you don't have the backup copy) and reinstall.

Let us know if need anything else! 

Peak Bagger

Hi Ashley,

Thanks for your fast answer. I've checked the folder and there is a newer but smaller version of the SCORMFunctions.js file.

I wonder if this new file has been updated with the modification you guys made to make it more compatible with the SABA environment. Should I overwrite the file or is it already impleted in it, plus new functions... That's my dilemma...

Ashley Terwilliger

Hi Peak,

There was a fix in update 3 regarding the cmi.core.exit data being communicated to an LMS, so I'm thinking that the newer/smaller version of that file would be ok to use. Do you have a test file you could publish and load to Saba to see if it all works as expected? If not, I can check with a few of my colleagues who may know more about that patch and the current set up with Update 4. 

Ashley Terwilliger

Hi Randall,

We're currently on update 5 as detailed here. This support article deals directly with Saba's environment and how it handles cmi.core.exit data, and I can't speak to if the fix within update 3 dealt specifically with Saba, as I believe it was more of a general LMS issue. Have you run into an issue with a course hosted at Saba?