Forum Discussion
FORCED_COMMIT_TIME value of 60000 (60k)
When publishing a Storyline 2 course for LMS, the configuration.js file has a setting " FORCED_COMMIT_TIME " which is set to "60000". Am I safe to assume that this is the number of millisecon...
Hello,
I'm the original poster of this discussion thread. Obviously things have moved on quite a bit from when I posted it four years ago.
However, we've started noticing that Storyline 360 (latest versions) are no longer setting FORCED_COMMIT_TIME to 60000 by default but to 0 (which means no auto-commit). Furthermore, the location of this configuration option has moved from "configuration.js" to "lms/scormdriver.js".
Is there any announcement on these changes that I can read up on? I'm particularly interested in knowing why an auto-commit has been switched off by default (as we're going to need to manually set this back to 60000 after each publish).
Note: We're publishing to SCORM 1.2 and SCORM 2004 and to "html5 only".
Thanks, Chris