This guide explains best practise for uploading Storyline 360 courses to the LXP. It covers two key areas:
1. How best to present Storyline courses in the LXP
2. Enabling xAPI or SCORM tracking for Storyline courses in the LXP
The first part is purely aesthetic. For Storyline courses to look good in the LXP, we recommend removing and hiding all elements of the Storyline player as this can look cluttered in the object viewer and a lot of the options (e.g. resources) are unnecessary.
In the xAPI section of the guide, we’ll be using Storyline’s built in Tin-Can API preset. If you would like to add custom xAPI tracking to your course, we recommend using Devlin Peck's guide which you can find by clicking here.
Note: As Learning Pool does not control the Storyline 360 authoring tool, these settings may be subject to change from time to time as Articulate release new versions of the authoring tool.
Removing the Storyline player
Click Player in the menu ribbon.
In the Features section, un-tick Resources, Menu, and Title.
Now click Colors & Effects.
Click Show advanced color editing.
Click the Edit item dropdown menu:
Select Base > Main Background from the drop down menu and set Transparency to 100%.
Now set the Transparency of Main Border to 100% too.
And do the same again for Slide Background.
Click OK and then go to the Story View.
Press [[ctrl]] + a to select all your slides.
In the side bar, untick the Previous and Next buttons. Remember, you'll need to add your own navigation buttons or automatic transitions in the course.
Publishing your course
There are a few different ways that you can publish your course for use with the LXP, we’re going to outline them all in this section of the guide.
We strongly recommend thoroughly testing each uploaded module before releasing the module to a group of live users. This will ensure the data is being tracked as intended and the module is completing as intended for the target users. The overarching process is shown below and is followed by the details of each step.
To import your Storyline 360 published content into the LXP you can publish the module to the following industry standard formats, these are:
• SCORM 1.2
• xAPI - (TinCan Launch)
These can be selected when you click Publish on the main Storyline 360 toolbar:
SCORM v xAPI publish - What’s the difference?
The SCORM 1.2 runtime model is an older standard that is still popular amongst content vendors and bespoke or inhouse authored e-learning modules. It allows the SCORM module to send back basic information to the platform such as this module is completed, incomplete, passed or failed. It also has the ability to store a small amount of state information, which is normally used by the content to provide bookmarking functionality. SCORM 1.2 can also send back an assessment score. It should be noted that the utilisation of the standard is the responsibility of the content, because a module is published to SCORM 1.2, this doesn’t automatically mean all of the data detailed above is sent to the platform. The LXP essentially intercepts the SCORM 1.2 data and converts this data to xAPI statements before sending these on to our Learning Record Store (LRS) - Data Cloud.
xAPI - (TinCan Launch) is a runtime that can send xAPI data to our LRS - Learning Locker in the xAPI format. The Experience API (or xAPI) is a much newer specification than SCORM that makes it possible to collect data about a wide range of experiences a user has. In this case we are using xAPI to track much more granular data about how a user interacts with the Storyline 360 module. If we compare this to SCORM 1.2 above - as well as the standard completed, incomplete, passed or failed verbs. xAPI can track data entered into a text area within the content for example, an assessment question response and more detailed screen by screen experience data. Again it’s the responsibility of the content to send the majority of this data.
If possible, we would always recommend publishing the Storyline 360 content to the xAPI - (TinCan Launch) method. If this is not possible, SCORM 1.2 will work. It could be the case that you can’t republish the content as this is provided pre-published by another vendor. In this scenario it’s important to ask the vendor what is triggering completion within the Storyline module. This can avoid long testing periods trying to reverse engineer what publish settings have been applied to the module.
SCORM 1.2 - tracking settings
In Storyline 360, the completion trigger you use to determine the overall module completion will dictate the type of xAPI data generated which in turn will dictate the settings needed in the LXP to ascertain if the module or learning experience should be marked as complete. Here are the settings for SCORM 1.2:
xAPI - (TinCan Launch) - tracking settings
In Storyline 360, the completion trigger you use to determine the overall module completion will dictate the type of xAPI data generated which in turn will dictate the settings needed in the LXP to ascertain if the module or learning experience should be marked as complete. Below shows the settings for xAPI - (TinCan Launch).
Locating the tracking settings in Storyline 360
The tracking settings are located under Home > Publish > Tracking within the Storyline 360 tool. These key setting determine when the module completion data is triggered and sent to the LXP.
1. When a learner has viewed: Used when a specific number of slide views triggers module completion.
2. When a learner completes a quiz: This uses the result of a quiz to dictate module completion.
3. Using triggers: Used when a completion trigger is set on a specific module slide.
SCORM 1.2 - Uploading to the LXP
Once you have set the appropriate tracking settings and published the module as a SCORM 1.2. You must then upload this to the LXP as a SCORM resource. When using the SCORM resource we strongly recommend leaving the default settings. This includes the launch in a new window setting. Unchecking this setting can cause issues with tracking so we recommend this remains checked.
xAPI - (TinCan Launch) - Uploading to the LXP
| 1. Once you have set the appropriate tracking settings and published the module as a xAPI - (TinCan Launch), you must upload this to theLXP as a xAPI - (TinCan Launch) resource. |
|
| 2. If you published your content after 15th of October 2020, you will need to change the launch title. Select index_lms.html from the dropdown menu. If you want to read more about Articulate’s changes to the launch file, you can do so here: https://articulate. com/support/article/Storyline-New-Launch-File-for-Tin- Can-API-Courses |
SCORM 1.2 - Game Settings in the LXP
Once you've uploaded the module as a resource, you need to create a learning experience in the normal way. Ensure the completion options are set to enable automatic completion. Adjust the game settings to those specified below:
xAPI - Game Settings in the LXP
Once you've uploaded the module as a resource, you need to create a learning experience in the normal way. Ensure the completion options are set to enable automatic completion. Adjust the game settings to those specified below:
And finally: test, test, test
As mentioned at the beginning of this short guide - we strongly recommend thoroughly testing each uploaded module before releasing the module to learners. This will ensure the data is being tracked as intended and the module is completing as intended for the target learners.