Connected SCORM

How a connected package works

A package is a snapshot: the experience and its media are copied into the package when it is exported, together with a web player. Each time a learner launches it, the package checks with Uptale that the experience can still be played. As a result:

• changes made to the experience afterwards only reach the LMS once a new package is exported and uploaded;
• the learner's device needs internet access to reach Uptale at every launch: packages don't play offline;
• a package stops playing if the experience is unpublished or deleted, if Connected SCORM is turned off, or if your organisation's Uptale environment no longer has access to Uptale.

Connected SCORM is self-service: your organisation's Environment Administrator turns it on alone, with nothing to configure and no setup by Uptale. The other LMS options, including Moodle LTI (also self-service), are listed in Connect to your LMS.

Requirements

On the Uptale side

• An Environment Administrator of your Uptale environment, to turn on the integration once.
• Someone who can export the experience: an Environment Administrator, a Workspace Administrator, a Creator or a Trainer.
• A published experience: draft experiences can't be exported. See Publish an experience.

On the LMS side (check with your LMS administrator)

• The LMS accepts SCORM 1.2 or SCORM 2004 courses.
• It serves these file types: .html, .js, .css, .json, .svg, .obj, .mtl; fonts .ttf, .fnt, .woff, .woff2; video .mp4; images .png, .jpg, .jpeg, .gif; audio .mp3, .wav; 3D objects .glb, .gltf.
• It accepts the size of the package: immersive experiences are usually larger than classic e-learning courses.
• The course can connect to Uptale (https://*.uptale.io), if your LMS or network restricts outgoing connections.

Conversations with AI also work in a package: the package sends them to Uptale, so the learner's device must be online.

Turn on Connected SCORM

An Environment Administrator turns it on once for the whole environment. There is nothing to fill in.

1. Open the Administration menu and click the Integration tab.
2. On the Connected SCORM card, in the LMS category, click Open details. The page shows No configuration required, you can activate this integration right away.
3. Switch on Configuration activation. The State changes from Deactivated to Activated.

From then on, the SCORM Export button appears on the experience pages for Environment Administrators, Workspace Administrators, Creators and Trainers.

Export a package

1. Make sure the experience is published.
2. On the experience page, in the Download the experience card, click SCORM Export.
3. In the Export Connected SCORM dialog, choose the Version: your LMS supports: Scorm 1.2 (selected by default) or Scorm 2004.
4. If the experience has several languages, choose the Exported languages. The experience's default language is selected first. Each language gives its own SCORM package: with several languages, you get one zip file per language, grouped in a single zip.
5. Click Export. If the experience has errors, you see This experience contains errors that need to be fixed before export. Please fix them in studio or proceed despite the risk of errors.: click Go back to studio to fix them, or Proceed to export anyway.
6. Wait while the dialog shows Creating your package., then click Download package. If the dialog tells you that you will be notified, you can close it: you receive an email when the package is ready.

Add the package to your LMS

Upload the zip file to your LMS as a SCORM course, choosing the SCORM version that was exported. With several languages, first unzip the outer zip, then upload each language's package as its own course. Nothing else needs to be set up on the Uptale side: no account, key or URL to enter in the LMS.

Update an experience

Content is not synchronised automatically. To bring a change to your LMS:

1. Edit the experience in Uptale and publish it again.
2. Export a new package.
3. Replace the previous package in your LMS.

What learners see

Learners open the course in your LMS, like any other course. The experience plays in their web browser, inside the LMS. They don't need an Uptale account and none is created for them.

What your LMS receives

The package sends the results to the LMS every 5 seconds and when the learner closes the page.

• Score: the stars won. The minimum is 0 and the maximum is the number of stars to win. SCORM 2004 also receives a scaled score (stars won divided by stars to win). There is no percentage.
• Status: with SCORM 1.2, incomplete, then passed, failed or completed. With SCORM 2004, a completion status (incomplete or completed) and a success status (unknown, passed or failed).
• Session time.

Passed or failed comes from the experience's own success criteria: the package doesn't set a passing score in the LMS. See Objectives, stars & success score.

Note: If the experience has no success criteria, the LMS marks it as completed almost as soon as the learner launches it.

Results in Uptale

Each session also appears in the experience's reports in Uptale, with all the details (answers, events, session report):

• when the LMS shares the learner's ID, the session shows LMS User with that ID;
• otherwise, it shows Anonymous user.

See Data tracked & LMS data and Experience report.

Uptale Player compatibility

Plays in a web browser only, inside your LMS

A SCORM package can't be handed over to the Uptale Player app or to a VR headset. For headsets, give learners access in Uptale instead (see All the ways to give access), or ask Uptale about another LMS integration (see Connect to your LMS).

Limits

• No automatic update: each change needs a new export and upload.
• Online only: every launch checks with Uptale.
• One language per package: learners can't change the language at launch. To offer several languages, add each language's package to your LMS. See Translate an experience.
• Web browser only: no Uptale Player app, no VR headset.
• Programs: SCORM sessions don't count towards Uptale programs; a program only counts the sessions launched from the program itself.
• What stops a package: the package shows an error instead of the experience when the experience was unpublished (back to draft) or deleted, when an Environment Administrator turned off Connected SCORM, or when your environment no longer has access to Uptale. Publishing the experience again or turning Connected SCORM back on makes existing packages work again. A deleted experience can't be played anymore: remove its package from your LMS.