- Quick Win Tutorials
- Getting Started
- Modular Development (ModDev)
- Quick Guides
- Best Practices
- 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
The Training Arcade®
Rockstar Learning Platform
Can't find the answer? Ask our Customer Solutions team.
xAPI Popular Choice Lectora
***All template files are tested using modern browsers, such as Chrome and Firefox. We do not support or test using Internet Explorer.***
Have you watched the xAPI Overview for Lectora yet? Watch it Now!!!
Our popular choice game template is a hefty little Lectora file.
Not only does the game present a scorable series of questions that the user can answer multiple times, but it's pretty easily customizable on your end...oh! and it sends custom xAPI statements to your LRS.
We're going to focus just on those statements today.
Template functionality is reviewed in other videos.
On the main question screens, we've set up an xAPIStatements action group that gets run whenever a user presses enter on their keyboard, or clicks the submit button.
It sets a few variables that we'll be using in a custom statement at the end of the action stack.
You can edit any of these variables to your liking.
Action 1 sets the Object ID for the statement we'll send. This should be equal to the Activity ID you enter at publish, but you can enter anything you like here.
Action 2 records the page name to a variable - we use this, in addition to the Object ID above to create a unique ID for out statement.
Action 3 sets the verb ID in URL format.
Action 4 sets the verb display. Plain text.
Action 5 runs our custom statement.
In it, we've included an additional response element that records the user's answer each time they submit one.
On the results page, we've also included custom statements.
On the Failed Text element, we've included actions in the same pattern as on the question screen - setting variables and sending a custom statement.
In this statement, we include the score and a success = false result.
On the Pass Text element, we've included actions the same way again.
This time, we include the score and a success = true result.
All of these additional elements can be filtered and reported on in your LRS.
This article last reviewed Dec, 2018. The software may have changed since the last review.