- Quick Win Tutorials
- Getting Started
- Modular Development (ModDev)
- Quick Guides
- Navigating the Workplace
- Building a Title
- Importing Content
- Working With Text
- Working with Images
- Working With Objects
- Actions and Variables
- Tests, Surveys, and Questions
- Working with Web Windows or HTML Extensions
- Publishing a Title
- Creating Web-based, Accessible Content (Section 508/WCAG)
- Lectora Layouts
- Managing Titles
- Managing your Assignments
- Managing Your Notifications
- Admin Guide
- Lectora Player Skins
- Lectora Interactions and Scenarios
- Using Tracking for Progress, Status, etc
- Working with BranchTrack
- Trouble Shooting
- Working with Audio and Video
- Working with Screen Recorder
The Training Arcade®
Rockstar Learning Platform
Can't find the answer? Ask our Customer Solutions team.
Storyline xAPI 3 Column Drag & Drop
***All template files are tested using modern browsers, such as Chrome and Firefox. We do not support or test using Internet Explorer.***
In this video, we're going to take a quick look at how to use the xAPI features in this file.
There are two ways to get this file reporting the xAPI data you'd like!
First, since we've set this template up as a Storyline quiz question, you can always use Storyline's built-in xAPI reporting features to get some deep insights into your users' responses.
To do so, you'll need to have a results slide tied to this interaction.
This can be anywhere in the file, and, in fact, you could use a blank results screen, dressed up as a standard content screen if you didn't want to show any formal results to your users.
However you do it, the default statements look something like the following [SCREENSHOT of REPORTING & ANALYTICS].
Aside from the usual "experienced" statement, you'll also see an "Answered" statement coming out of SL.
This statement contains a lot of detail, including the correct answer pattern, what the user's answer was, and success, to name a few bits.
It's not super-readable though.
But, you can certainly create reports through your LRS or with the help of a developer.
We've included an additional option that's a little less compact, but more readable too.
When the state of a dropzone changes to "Drop Correct," we throw a statement: user "matched option #"
When the state of a dropzone changes to "Drop Incorrect," we throw a statement: user "failed option #"
Each of these statements are contextually related to some values you enter for the slide identifier.
This makes them easy to sort and filter, and provides some nice visualization in the analytics dashboard of your LRS.
To use our statements, make sure DISABLE_xAPI is set to FALSE.
Then, enter the details for your slide.
Make sure to check out our xAPI overview video for more details on these details.
Once you edit those values, your file is set up and ready to go.
From here, you'll need to publish and launch your files to see statements.
Check out our "publishing to xAPI" video for more detail.
This article last reviewed Nov, 2018. The software may have changed since the last review.