I think this really has more to do with how your lesson is sending the status. It's the lesson that, ultimately, should decide if the lesson is complete or not. However, that status is not 'definite' until the LMS.commit function is called. Once that's called, then any data that's been sent back to the LMS is official.
So ideally, your CP lesson should not send a Completed status until the user has finished whatever tasks are required to gain that status (all pages viewed, certain interactions finished, etc)...then when the user exits the lesson, CP sends the Commit and Finish calls and the LMS finalizes that lesson.
It sounds like this LMS is doing some sort of default action where, perhaps, if communication is lost with the lesson or a timeout is reached, it automatically commits the status (which CP should have sent). So first:
1. Is your CP lesson sending the status properly? Is it sending Completed as soon as it opens? That's a common issue... If so, the LMS could be receiving the status correctly, but acting on it incorrectly by commiting that status when it should not be.
2. Is the LMS taking a default action, like setting a status to Completed, when the API communication is lost? Which, I agree, sounds like a bad assumption to make and is doubtfully a SCORM requirement.
HTH
Erik
6
Replies
AdChoices