Skip to content

aNewSpring

How to export a Coassemble course as SCORM and add it to an aNewSpring course template, with completion tracked there.

Yes. Export your course from Coassemble as a SCORM package, upload it to your aNewSpring content library, then add it as a SCORM activity in a course template.

If you build learning paths in aNewSpring, you can author courses in Coassemble and deliver them there. Coassemble exports a standard SCORM package and aNewSpring accepts SCORM, so the two work together with completion tracked in aNewSpring.

Add a Coassemble course to aNewSpring

  1. In Coassemble, export your course as a Dynamic SCORM package and download the .zip file.
  2. In aNewSpring, upload the .zip to your content library.
  3. Go to the Templates tab and open the course template you want to add it to.
  4. Under the General tab, select +Activity and choose SCORM as the activity type.
  5. In the activity settings, link it to the SCORM file you uploaded to your library.

Tips

To avoid learners seeing two sets of navigation, consider hiding aNewSpring's Next and Previous buttons for that activity, so they're not navigating both aNewSpring and the Coassemble course at once.

For updates, a Dynamic SCORM package keeps a live connection to Coassemble, so publishing your changes in Coassemble updates the version in aNewSpring without touching aNewSpring at all.

Dynamic and standalone packages

A Dynamic package stays connected to Coassemble and updates in place. It is the standard export and the right choice for almost every aNewSpring setup.

A standalone package is static and runs with no connection back to Coassemble, which suits an air-gapped environment or content that has to keep working independently. Standalone SCORM is arranged by negotiation, so talk to the Coassemble team if you need it. Updating a standalone package means replacing the file in your aNewSpring content library.

Frequently asked questions

Why might learners see two sets of navigation?

Both aNewSpring and the embedded Coassemble course have their own Next and Previous controls. Hiding aNewSpring's buttons for the activity avoids a confusing double-navigation experience.

How do I update a course after adding it?

With a Dynamic package, publish your changes in Coassemble and they flow through. A standalone package has to be replaced in the aNewSpring content library.

Where do I add the SCORM file in aNewSpring?

Upload it to your content library first, then add it as a SCORM activity inside a course template and link it to that file.