Forum Discussion
Force Commit during Publish in Storyline (v1) and Presenter ('13)
Our company has discovered a problem when content is published to AICC (through either Storyline 1 or Presenter '13). There is a setting within the configuation.js and lms.js files that force a commit time. This is sending an attempt to our LMS prior the learner actually completing the content. For example, we have a 15-minute module with three attempt limits (set within our LMS), but the FORCE COMMIT statement in Articulate is sending a commit every ten minutes to our LMS and the learners max out attempts on the first try.
It appears the default value for the FORCE COMMIT statement is "60000" seconds. We need to set up Presenter and Storyline to change that setting to "0" which indicates no commit time.
Has anyone encountered this? Where can I find the setting within Presenter and Storyline to correct this problem?
Thank you in advance for your assistance!
13 Replies
Sorry I want to clarify my update above. For presenter you can edit the file lms.js to change the value of the "heartbeat" variable from 60000 to what you need. If you edit the file in the installed source directory for the articulate presenter installation it will be copied into the published output which avoids the developer from having to remember to edit published content. This has worked for us for years.
