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...
I'm with you Chris! The switch from SCORMFunctions.js to scormdriver.js is really throwing us for a loop. The new scormdriver.js is the same code base that is used for Articulate Rise. When I expressed dismay over the lack of functionality for the FORCED_COMMIT_TIME variable in the Rise code base, it sounded to me like there was no remediation planned. But hopefully if it gets fixed for Storyline, the fix can be translated to Rise as well.
This is a major issue for our company with over 200,000 employees who are now faced with a greater likelihood that their progress through a course may be lost if there is a network error. And we have over 200 Storyline developers who are producing projects .