Using a Delegate™ to Add xAPI Support in Your LMS or to Distribute Content

Using a Delegate™ to Add xAPI Support in Your LMS or to Distribute Content

A Veracity Launch Delegate™ links a content package to a set of rules about when, how often, and for how long to make content available to another LMS. Once you've created a Delegate in Launch, you can download the package and then upload it into your other LMS in the widely-supported SCORM 1.2 format. Although it tells the other LMS it’s SCORM 1.2 on import, the Delegate can contain a package in a modern and advanced format.

Adding xAPI or cmi5 Support to Your LMS

Many people find themselves stuck with an LMS that doesn't import xAPI or cmi5 packages, or it won’t let them send xAPI data to an LRS. To solve these problems, we added the Delegate™ feature to Veracity Launch. A Delegate lets you easily add xAPI support to your LMS. The actual physical content lives in Launch (or even on an external server). Launch sends xAPI data forward to any LRS and sends SCORM data backward to your LMS. Launch simply acts as a data broker that is also an xAPI-conformant content player that records learner progress.

Notes
Delegate packages work best in a pop-up window. When you add content (or a link to external content) in Launch, set the Launch Type to Popup to ensure best compatibility. If you open content in a frame and the learner closes the browser tab or window to end the session, then you may not get completion data in the LMS, Launch, or an LRS.

Distributing Content to Multiple LMSs

Do you need to distribute your content to more than one LMS? Just set up as many Delegates as you need for that piece of content. Then you can share that content to learners in as many LMSs as you want. Since they all come from a single source in Launch, this centralization helps you control access (e.g., set expiration date) and manage maintenance (e.g., replace files).

Creating a Delegate™

Notes
The whole idea of creating a Delegate to use as a “courseware package service proxy” can seem complex. If you have any questions or issues, then please contact us.

Follow these steps to use the Delegate feature in Veracity Launch:
  1. Sign-in to Veracity Launch; and in the left menu, select ADMIN > Manage Content.

  2. In the Manage Content page, in the card for the piece of content you want to add a Delegate, click the More button () and select the Create Delegate option from the pop-up menu.



  3. In the Create Delegate form, enter the properties of the Delegate:
    1. Content ID — The pre-configured unique identifier of the Delegate and its package.

    2. Delegate Name — The short name you’ll use to refer to the Delegate.

    3. Delegate Description — A useful area to list any unique properties or requirements.

    4. Package Name — The filename of the Delegate package. Avoid using illegal characters, such as ampersands or quotes.

    5. Package Description — This is the long description visible in the LMS.

    6. Launch Date — The content will not play before this date. Leave blank for immediate access.

    7. Expires Date — The package will not play after this date. Leave blank for no expiration.

    8. Active — A useful toggle to temporarily enable/disable the Delegate.

    9. Launch Limit — Each time another LMS plays a package from the Delegate, it increments a launch counter. When the counter reaches this limit, the package will not play the content. Set the slider to 0 for unlimited launches.
Notes
If you import many packages to other LMSs that target the same Delegate, then they all increment the launch counter.
    1. Origins — A list of websites that can host this package. If the origin of the package (the host LMS) is not in this allowed list, then the package will not play. Leave blank to let it play from anywhere.
Notes
Origins should match the full protocol and domain name of the host (e.g., https://don.csod.com or http://wordpress.com). If you use a nonstandard HTTP port (other than 80 or 443), then include the port number (e.g., http://localhost:3000).
  1. When finished, click the Create button.



  2. On the card for the selected piece of content, click the More button () again, and select the Show Delegates option from the pop-up menu.



  3. In the Delegates page, in the row for the Delegate you just created, in the Actions column, click the More button (), and select the Download Delegate Package option from the pop-up menu.



  4. Open your other LMS and import this package.
Notes
Your other LMS must support SCORM 1.2 for it to import this package successfully. The content in Launch can be any format (i.e., xAPI or cmi5); the Delegate simply acts as a proxy and serves the package in SCORM 1.2 format because it’s the most common.

Now that it’s in your other LMS, learners can open and run the Delegate just like any other piece of content!