LMS Configuration.js file not affecting HTML5 versions

Mar 06, 2018

Hello all, my company's custom-built LMS supports the AICC standard. I've been informed by our network team that our courses are logging too much AICC data to our database. 

I've configured this line in the configuration.js file in the "lms" folder of the output. The default value was sending data every 60 seconds. I set it to "0" to turn it off.

var FORCED_COMMIT_TIME = "0"; //Used to force CommitData back to the LMS at the desired interval (in milliseconds). Set to 0 (zero) to not force a commit time.

After publishing and uploading to server, I've been using Chrome and IE11's developer tools to monitor the network communication. Both browsers agree that the Flash version of the course does not send this data (as intended), but that HTML5 version of the course CONTINUES to send this data every 60 seconds. 

So, does the HTML5 version just completely ignore the configuration.js file? Is there another way to stop this communication for the HTML5 version of the course?  

 

5 Replies
Tim Marriott

Hi Ashley, the support ticket I opened did not yield any helpful info from Articulate Support. It's somewhat urgent that I get this resolved. Can you recommend anyone else I speak with about this? I just want to make clear that the issue is apparent in the browser before I even upload to LMS, so it's not an LMS issue. The AICC data is attempting to send every 60 seconds as seen in the browser's developer tools under Network logs - despite my changing the configuration.js file. This seems like some kind of bug in the software.

Crystal Horn

Hey Tim. I'm excited to let you know that we just released update 16 for Storyline 360! It includes new features and fixes - check them all out here.

One of the fixes addresses an issue where in the HTML5 output, data is sent to the LMS every 60 seconds even if set not to.

Here’s how you can update Storyline 360 to take advantage of everything the latest release has to offer. Let me know how you make out!

This discussion is closed. You can start a new discussion or contact Articulate Support.