Forum Discussion
Force Commit during Publish in Storyline (v1) and Presenter ('13)
Hi Ashley,
Thank you for the response. We have done the debug and found the culprit in the configuration.js and lms.js files built upon publish. Both files set the Force Commit to 60,000 by default when the code states to set to 0 for no force commit. Our LMS is reading this 60,000 and sending a complete statement back every 10 minutes - whether or not our learners have actually completed the content. Therefore, if we set an attempt limit in our LMS to three and the learning component takes more than 10 minutes, the LMS shows two attempts when the learner only launched it once.
We most certainly do not want designers touching published content. We are trying to find a way to change that setting prior to publish. The js files would indicate it is possible since the remarks within the files show an option for 0.
Thoughts on what we should try? Suggestions?
Thank you!
Related Content
- 11 months ago