Comments on: cmi.core.exit & cmi.exit http://pipwerks.com/journal/2008/05/10/cmicoreexit-cmiexit/ Philip Hutchison's technology journal, dedicated to exploring web technologies for website and e-learning development. Tue, 06 Jan 2009 06:10:26 +0000 http://wordpress.org/?v=abc By: Philip Hutchison http://pipwerks.com/journal/2008/05/10/cmicoreexit-cmiexit/#comment-561 Philip Hutchison Sun, 11 May 2008 17:28:34 +0000 http://pipwerks.com/journal/?p=101#comment-561 @ethan good to know! personally, i avoid SCORM 2004's sequencing like the plague. @ethan

good to know! personally, i avoid SCORM 2004’s sequencing like the plague.

]]> By: ethan estes http://pipwerks.com/journal/2008/05/10/cmicoreexit-cmiexit/#comment-560 ethan estes Sun, 11 May 2008 15:39:36 +0000 http://pipwerks.com/journal/?p=101#comment-560 Not only that but cmi.exit value has an effect on the sequencing under 2004-which navigation request is used and if it's used at all. It also has an impact on what the lms sets the cmi.entry to for the sco to read on re-entry(if it's a re-entry.) I ran into a similar issue where my sco was setting the lesson_status at the end of the first screen-if a user bailed on it before it was set, under, 1.2 the LMS sets the lesson_status to completed. Which is different from 2004 where progress_measure and completion_threshold come into play. Not only that but cmi.exit value has an effect on the sequencing under 2004-which navigation request is used and if it’s used at all. It also has an impact on what the lms sets the cmi.entry to for the sco to read on re-entry(if it’s a re-entry.) I ran into a similar issue where my sco was setting the lesson_status at the end of the first screen-if a user bailed on it before it was set, under, 1.2 the LMS sets the lesson_status to completed. Which is different from 2004 where progress_measure and completion_threshold come into play.

]]>