Brian Rogers
posted this on April 19, 2010 01:04 pm
The SCORM Engine has a built in way to _globally_ set how new package versions are delivered once updated. More about this can be read about here http://scorm.zendesk.com/entries/35948-versioning-in-scorm-engine-2008-1.
A more advanced way to handle this is to decide upon launch if the learner will continue on with the old version or if a new registration will be created for them using the new version. This is done by passing a configuration setting in on launch and evaluating that value based on this chart.
1 = "never"2 = "when existing registration is complete and newer package version exists"3 = "when newer package version exists"4 = "when existing registration is complete"5 = "when existing registration is satisfied"6 = "when existing registration is satisfied and newer package version exists"9 = "always"0 = "use what the config file says"
First you will need to add a custom externalConfiguration property to your CLIENTNAMEExternalConfiguration class file.