Dynamic SCORM: upload once, update by republishing
A dynamic SCORM 1.2 or 2004 package is uploaded to your LMS once and loads the version of the course you last published each time a learner opens it. What it needs from your network, what stays in your LMS, and what happens if you revoke it or your plan ends.
Last updated 5 min read
Every fix to a course means exporting a new package and replacing it in the LMS.
Step by step
Publish the course
A dynamic package shows learners the published version, never a draft, so publish first. The first package of a course also needs every change published.
Make the package
Open Export and choose Dynamic SCORM 1.2 or Dynamic SCORM 2004. A zip downloads.
Upload it once
Upload the zip to your LMS as you would any SCORM package, and launch it once to check it opens.
Republish to update
When you change the course, publish it again. Learners get the new version the next time they open it, usually within a minute.
What a dynamic package is
A static package carries the whole course: change a word and you export a new zip and replace the old one in every LMS that has it. A dynamic package carries only what talks to the LMS (the manifest and the same SCORM driver a static package uses) and a small launcher. Each time a learner opens the course, the launcher fetches the version you last published from Scormbusters and runs it.
- Republish to update. Fixes, new lessons and new questions reach learners on their next launch, in every LMS the package is in.
- Published only. Edits you have saved but not published are never shown.
- Block and Scenes courses, as SCORM 1.2 or SCORM 2004. cmi5 and xAPI packages are static only.
Dynamic packages are part of the Enterprise plan. Other plans see the option in the Export menu, disabled.
Tracking stays in your LMS
Scores, completion, pass or fail, bookmarks and question results go from the package to your LMS exactly as they do from a static package. No learner name, ID, score or progress is sent to Scormbusters: the only request is for the course content, and it carries the package's key and nothing else. As with any web request, our hosting providers see the browser's IP address and type. Pictures, audio and video load from media.scormbusters.com.
When the course changes, a learner's saved place follows it: lessons they completed stay completed if they still exist, a bookmark on a lesson you removed moves to the next one, and a result the LMS already holds is never lowered. A learner part-way through a course you rewrote heavily may see questions they already answered marked as unanswered in the new lessons.
What your network and LMS need
Learners' browsers must be able to reach scormbusters.com and media.scormbusters.com over https. Some networks, firewalls and LMSs block content from other sites; if yours does, ask your IT team to allow both. When the content cannot be reached, learners see a "Can't reach the course content" screen with a Try again button, and nothing is recorded in the LMS.
The course name and pass mark in the LMS are the ones in the package when you downloaded it. If you change the pass mark later, download a new package and replace the old one; the course's Settings → Dynamic SCORM packages list says when a package's pass mark differs.
Note: Test a dynamic package in your LMS with a test learner before you assign it: some LMSs restrict what launched content may load.
Revoking a package, unpublishing, and when your plan ends
The course's Settings → Dynamic SCORM packages (in a Scenes course, Export → Manage dynamic packages) lists every package you have made, when it was made and when it was last launched. Revoke retires one: from their next launch its learners see "This course has been retired — contact your learning administrator". The same screen appears while the course is unpublished or after it is deleted, and if the workspace leaves the Enterprise plan.
A retired package says nothing to the LMS, so completions and scores already recorded stay as they are. To keep a course running without Scormbusters, export a static SCORM package (every plan, and for at least the keep-your-courses period after a subscription ends) and replace the dynamic one with it. See Export a course to your LMS.
Privacy and security
Each package has its own unguessable key, stored by Scormbusters only in scrambled form. Anyone who has the package can open the published course, as anyone who has a static package can; answer keys are in the content for the same reason they are in every SCORM package. Revoke a package that has been shared where it should not be. Making a dynamic package of an imported course counts as a migration, exactly as a static export does; learners opening it never count.
Part of the documentation: Deliver.
Found something here that does not match what the product does? That is a bug in the guide — see all guides or tell us from the Help Center.