Try before you buy? Test drive? Freeware?

All of the above, and more. If you’re not making money off of SCORM Driver, then we don’t want to charge you to use it.

It means that there will be more really conformant SCORM and AICC content packages in the world, which makes us really happy.

Check out what constitutes non-commercial use.

Support for our free SCORM Driver users is very limited, so make use of the Quickstart Guide that we made, and the rest of our SCORM Driver documentation.

You can download SCORM Driver (free for non-commercial use) from the “Add Content” page of SCORM Cloud.

SCORM Engine 2011.1.0.322 is available.  If interested in upgrading, contact us at support.scorm.com.

Changes since 2011.1.0.0

• Calculate scaled score in immediate rollup for scorm 1.2 to ensure that a rolled up score will come along with a completion if set.  Otherwise the completion would come through, but the score wouldn't be seen until termination time because the scaled score was only set within CloseOutSession().
• Javascript Package Properties editor can now send updateAllVersions parameter to apply changes to all versions.
• ScormEngineManager.UpdatePackage() will now update the title of the package (organization).
• Runtime state persistence enhancements: Make SaveData() during ScoUnloaded synchronous.  Added code to mitigate issue with double postbacks where an intermittent post back is processed after an exit postback.
• Default Integration method SetCulture() (And GetCosmeticInfo) now supports setting of the culture code explicitly with a &cc query string param or form post param at launch time.
• Java JSPs are now explicitly sessionless to prevent needless server-side session creation.
• Parser warnings are now localized when using the .NET Import Control.
• Utilize DatabaseSchema (optional configuration property) in all code, including the NoddyLMS (demo app).
• German JavaScript strings formatting fix.
• Delete from ScormRegistrationSharedData when resetting / deleting registration data -- Prevented some 4th edition courses from being deleted.
• Allow AICC to work when ScormEngineUrl is defined as a relative URL (absolute URL is constructed internally from the launch URL).
• For SCORM 1.2, immediately set score.scaled when score.raw is set rather than waiting for SCO Termination.
• Added connection pooling to JdbcDatahelper for use when a direct db connection is configured instead of a Datasource.
• Improved package delete syntax so ScormEngineManager.DeletePackage() is more efficient for bulk deletes.
• Default Package Properties Editor to use English when a bad language code is specified rather than giving JS error.
• Java SupportPackager fixed to propertly render in all browsers (changed content type to text/html).  Also added ExternalConfiguration.
• Fixed a scoring divide-by-zero error if you have all zero scores and change package property for rollup to "all non-zero scores".
• Disregard case of launch-time query string parameters -- "Registration", when uppercased, would be sent twice to the deliver page.
• Added a couple additional Java web services methods to match up with what's available .NET-side.
• Added interactions and objectives to AICC Launch History.
• And other minor internal changes and unit tests...

Starting with SCORM Engine v.2011.1 a special URL is now available for aggregating information about a specific course/registration for support purposes. It's located at <scorm engine root>/SupportPackager.aspx or if Java <scorm engine root>/SupportPackager.jsp.

Why is this needed?
So often when contacting internal support or Rustici Software the first few interactions are all about gathering documentation and debug data.  The goal here is to streamline that process so we can get the bulk of relevant information from the start.

What is in a support package .zip?

•     Activity Report - A snapshot of registration data (SCORM state) from the SCORM Engine database.
•     Package Properties - Configurable properties that define compatibility settings and other options that are useful to know when debugging.
•     Parser Warnings - Any abnormalities detected in the SCORM Manifest.
•     Launch History - A record of of each launch of the registration, including SCORM Runtime calls.
•     SCORM Manifest - the imsmanifest.xml file for the course.
•     SCORM PIF (optional) - The entire .zip of the SCORM package for recreation purposes.

Is this tool meant for Rustici Software only or can LMS vendors use it for support desk purposes?
The support package can be of great value in support desk situations.  Only when Rustici Software's own support is needed do you have to send the package to Rustici Software support.

How is the Support Packager accessed?
Simply go to the url <scorm engine root>/SupportPackager.aspx (or .jsp) and you will be presented with a form.  At present you can also access this page through the SCORM Engine client side debug log.  In the upper right corner there is a "save debug log" link.  By clicking on that you will then be shown another url to create a support package.  That link will send you to SupportPackager.aspx (.jsp) with the regisration and debug log fields pre-populated.

We have a course that fails to complete under a certain situation and I needed Rustici Software's support.  What should I do?
This is going to be one of the most common uses for the tool.  Simply go to the Support Packager url and fill it out (select "Create new Zendesk ticket") then click "Send Package to Rustici Support".  If you have a local debug log or have recreated this on cloud.scorm.com please include the debug log link.

I don't want to allow just anybody to send tickets to Rustici Software.  What can I do?
In your SCORM Engine settings file, define a key named "SupportPackagerSendKey".  The value for this is essentially a password.  If the value is empty, anybody can send a open a ticket with Rustici Software.  If you define a value like "mypass" you will need to add this query string to be able to submit to rustici software: SupportPackager.aspx?config=mypass.