Attempts not recording to LMS

Good Morning, Gordon.

I definitely don't want to stir the pot on whether or not we are breaking the SCORM standard, but I think I can try to explain why we've chosen to do things the way we do them:

• One camp says that we should always set cmi.exit to normal upon completion of the SCO. This camp says that if we set cmi.exit to suspend upon completion, we are assuming that the learner has exited with the intent of returning to the SCO at a later time, and that it isn't fair for us to make this assumption. This camp also says that if we were to always set cmi.exit to normal upon completion, it would make it easier for the LMS to know that it should start a new attempt the next time the learner accesses the SCO.
• Another camp says that setting cmi.exit to suspend will ensure that the current attempt is preserved and the run-time data is not reset the next time the SCO is launched. In order for bookmarking to work, content must be exited in a suspended state. In contrast, if cmi.exit is set to normal, the learner's attempt ends, and the run-time data of the current session will not be available if the SCO is relaunched. In other words, if we want to allow the learner to resume a completed course, we must use suspend.

Essentially, by always setting cmi.exit to suspend, we've gone with the method that we feel offers the most flexibility to the LMS. This way, if the LMS offers the option to start a new attempt each time, they can go ahead and do that. If we were to always set cmi.exit to normal upon completion, we might force the LMS to start a new attempt next time, but customers with different requirements would never be able to allow their learners to resume a completed course.

I hope that helps. Have a great day!