Delegates provide a way to play and distribute your content to an LMSs, while keeping the actual physical course files and playback logic centralized. Need to distribute your content to more than one LMS? Delegates also allow you to share the same source content to multiple LMSs. This is ideal if you have multiple audiences, customers, users, or anyone that must receive the same content in different LMSs, while providing a single source location in Veracity Launch to issue updates and manage access control.
A delegate links a content package to set of rules about when, how often, and for how long content is available to an external LMS. Once you've created a delegate in Veracity Launch, you can download the package and then upload it into your LMS. The package is imported into the LMS as the widely supported SCORM 1.2 format. It's important to note that the content package is only using the SCORM 1.2 format for import process into the LMS. The actual physical content lives in Veracity Launch and uses Veracity Launch to record the progress as both SCORM and xAPI.
Check out the steps below to use the Delegates feature in Veracity Launch.
The delegate technology is complex. Please let us know if you experience any unexpected behavior, or have any other questions or issues.
1. To create a Delegate, first navigate to the content management page and add content to your portal by uploading a SCORM, xAPI, or cmi5 content package -OR identify an existing content package that you previously uploaded.
- If your'e using the card view to manage the content, click on the vertical ellipsis icon (three dots vertically aligned, located in lower left corner of the card) and then click "Create Delegate" from the submenu
- If you're using the list view to manage content, click on the vertical ellipsis icon (three dots vertically aligned, located under the Actions column) and then click "Create Delegate" from the submenu
2. On the next screen, update the name, description, launch limit, and other properties as desired, and then click the "Create" button. A new delegate record for the content is created. The properties on this screen are described below.
- Launch Limit - Each time any package targeting the given delegate record is played, the launch limit will increment. When the limit is reached, the packages will no longer play the content. A limit of 0 is used to represent and infinite number of launches is allowed.
- Active Date - The content will not play until the given date.
- Expires Date - The package will not play after the given date.
- Active - a temporary way to disable the delegate.
- Origins - a list of websites that can host this package. If the Origin of the package (where it is hosted) is not in the allowed list, the package will not play. Origins should match the full protocol and domain name of the host, ie "https://don.csod.com" or "http://wordpress.com". If you are using a nonstandard HTTP port (other than 80 or 443) the port number should also be included, as in "http://localhost:3000"
3. Click on the vertical ellipsis icon again for the content you identified, and click the submenu "Show Delegates"
4. A Delegates screen will be displayed, showing the delegate management interface. Under the Actions column, select the delegate you created, and then select "Download Delegate Package" from the submenu.
5. Next, import this package into your LMS. The LMS must support SCORM 1.2 for this package to import successfully. It's important to note that the delegate package is in using the SCORM 1.2 import format because that is the most common import format supported by an LMS. However, the content itself is not delivered to the LMS using the SCORM format. The delegate package acts as a proxy.
Note that multiple package files can target the same delegate record. If you distribute the package for a given delegate, they will share the total launch limit.
Delegate packages work best with popup windows. Please consider setting the launch type to popup to ensure the best compatibility. Some content can be run in a frame, which can improve the user experience. This depends on whether or not the content proactively terminates the learning session with a button. If the content relies on the window closing to terminate session, you may miss status updates when running in a frame.