4.1.2

Added options for supporting Sequence and Navigation calls in SCORM 2004 content. This gives you the added capability of setting a default 'adl.navigation.request' if you want to automatically continue, or exit for example after the SCO Terminates. Typical behavior (depending on the LMS platform) may be to leave your SCO just hanging out after Terminate is called. Unless you actually visually build something that informs the student their information is no longer tracked, it could and has confused students. So the short bonus is, you could actually exit the content.
The deeper strategy:
SCORM 2004 Implementations typically allow you to request a navigation request like continue, previous, choice, exit, exitAll, abandon, abandonAll, suspendAll. You should familiarize yourself with what these all do, as they may make your content 'less friendly' too students if for example you keep calling 'exitAll' and it kicks them out of the entire lesson.
You can make decisions about implementing your own strategies about remediation, or skipping content based on performance. You could call 'previous' to make the student go backwards and re-take something. You could request '{target=INTRO}choice' to jump to a sibling identifier. This does however put more ownership on making your content more aware of its surroundings in a bundled lesson. You could place extra parameters in launch data to dynamically inject some of that vs. hard coding it (for example). SCOBot may include a decision engine based on more parameters at a later date. It will mainly require expanded imsmanifest.xml construction which can have dependancies on a packaging system, or hand coding XML. So if a strategy is built out, it would have to coincide with added features to the SCOBot Packager or a manual adjustment in XML.