Opus support for SCORM is straightforward with the inclusion of SCORM functions as standard Opus actions – no more ifddling with scripts, simply select the action you need as you would any other Opus action.
Note for Users of Previous Versions:
There is no longer any need to choose SCORM as a separate publication type. When publishing Flex (Adobe Flash) or HTML5 publications the publishing wizard will now offer you the chance to output these as SCORM publications.
Our SCORM support has been developed and tested with real world projects with real world customers for over two years to ensure all possible wrinkles are ironed out. Opus now offers built-in functionality greater than any comparable product. There is full control of the SCORM manifest and you can build the complete final SCORM package directly from within the publishing process.
SCORM publications can be created using both Plexus and Flex. With many of the limitations of Flex now removed you can be confident of creating SCORM-conformant material in industry-standard Flash format with greater power and sophistication than is provided even in Flash itself.
Both SCORM v1.2 and SCORM 2004 are supported and there is a dedicated introduction to SCORM in the Help and a special Opus publication to learn and test SCORM support and provide debug information.
We also know from our experience developing the support that some LMS systems have specific non-SCORM requirements and so we also provide a SCORM compatibility support service. If you have problems getting your publication to run in an LMS because there are specific non-standard requirements we can provide extended guidance and even write custom HTML wrappers.
SCORM Actions
|
|
|
| Initialize SCORM | Trigger this at the beginning of every SCORM publication to start the communication with the LMS. It is mandatory to call this once and only once in a SCORM-conformant package, |
| Get SCORM Value | Allows you to get data from the LMS and put it into an Opus variable for use in the publication. You can choose SCORM1.2 or SCORM 2004 values or you can type in a custom data model name. |
| Set SCORM Value | Allows you to send a specific piece of text or number, or data from any Opus variable to a specific SCORM data model in the LMS. You can choose SCORM1.2 or SCORM 2004 values or you can type in a custom data model name. |
| SCORM Commit | This action allows you to update the LMS as you progress so that if the connection is lost the LMS has the most recent information for that user. This is particularly important when using SCORM on mobile devices. |
| SCORM FInish | Trigger this at the exit point of every SCORM publication to finalise the communication with the LMS. It is mandatory to call this once and only once in a SCORM-conformant package. Make sure you have finished communicating other values – such as score and progress – before ending the communication. |
|
|
|
Recent SCORM Improvements
|
|
|
| Improved API code | The fundamental functions required to find the SCORM API is now improved and more robust. |
| Key Functions | The essential functions to initialize and end communication with the LMS have been rewritten to be more direct and robust. |
| HTML Wrapper | The HTML wrapper used to launch your publication has been overhauled to improve performance. |
| Ready made variables | For speed of development and ease-of-use convenience, additional ready made variables are now included providing Opus versions of commonly-used SCORM data models |
Related Topics