Articulate 2009 always produces a code that keeps the LMS session alive. The code is present in the lms.js file as below: setInterval("ForceCommit()", 600000); In the previous versions of the courses that we published in earlier versions of Articulate, we did not have this.
Question: Which version of the Articlate was this introduced in.
Reason: We have LMS which has session timeout of 20 minutes. Since Articulate 09 presenter course has in itself a session timeout of 10 minutes, the course never times out as per the LMS requirements. Can we change this or remove this setting in the Articulate tool as we do not need this.
Satish you could not edit the lms.js file on your machine to set the interval to 20 minutes, if you edit the version on your machine everytime you publish to scorm all packages will have the new timeout set, you could also probably delete the line, why not try it and see what happens
Thanks for the reply, firstly it is not a setting that we can alter so that all future courses published from my machine will have 20 mins as the new session timout timing. It is an edit on the LMS.js file that we can manually do.
Now coming to the actual problem, this session timeout was not present in the earlier versions of the Articulate presenter that we published with. I am not sure which was that earlier version. I am also not sure in which current / latest version this got introduced.
The problem we currently have is, the LMS is already set to timout every 20 minutes if any user is inactive for that much time. Since the course published in Articulate does a shakehand with the LMS every 10 minutes, without the user interference, these set of courses never timout and keep looping infinitely.
So what I am looking at is where in the Articulate tool is this setting available which we can ignore or escape so that no such handshake or heartbeat code comes when we package course.
Sorry, I think you misunderstand me the lms.js file generated by Studio can be edited on your machine, if you change the timeout in this file to greater than 20 mins then your lms will timeout, there is no setting in the tool to get rid of this code you would need to manually edit or remove the code involved
Thanks for the reply and I was aware of the fact you mentioned in your reply. Do you know when was this introduced, because the courses published in earlier versions do not have this code. I am not aware which earlier version was this.
4 Replies
Satish you could not edit the lms.js file on your machine to set the interval to 20 minutes, if you edit the version on your machine everytime you publish to scorm all packages will have the new timeout set, you could also probably delete the line, why not try it and see what happens
Hi Phil,
Thanks for the reply, firstly it is not a setting that we can alter so that all future courses published from my machine will have 20 mins as the new session timout timing. It is an edit on the LMS.js file that we can manually do.
Now coming to the actual problem, this session timeout was not present in the earlier versions of the Articulate presenter that we published with. I am not sure which was that earlier version. I am also not sure in which current / latest version this got introduced.
The problem we currently have is, the LMS is already set to timout every 20 minutes if any user is inactive for that much time. Since the course published in Articulate does a shakehand with the LMS every 10 minutes, without the user interference, these set of courses never timout and keep looping infinitely.
So what I am looking at is where in the Articulate tool is this setting available which we can ignore or escape so that no such handshake or heartbeat code comes when we package course.
Let me know if this helps,
Regards,
Sats
Sorry, I think you misunderstand me the lms.js file generated by Studio can be edited on your machine, if you change the timeout in this file to greater than 20 mins then your lms will timeout, there is no setting in the tool to get rid of this code you would need to manually edit or remove the code involved
Hi Phil,
Thanks for the reply and I was aware of the fact you mentioned in your reply. Do you know when was this introduced, because the courses published in earlier versions do not have this code. I am not aware which earlier version was this.
Regards,
Sats
This discussion is closed. You can start a new discussion or contact Articulate Support.