- 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.
***All template files are tested using modern browsers, such as Chrome and Firefox. We do not support or test using Internet Explorer.***
Today we'll be discussing the xAPI features of our Starter Layout template.
As with most in a Lectora style, we've defaulted to Lectora's built-in statement options for the majority of statements in the file.
The one exception, however, is the text entry layout.
On this one, when a user enters a response into the text entry field and presses submit, a feedback group will appear.
When this group appears, the user's response will be displayed back to them, as well as submitted to your LRS through a custom statement.
Let's look at that statement now.
If you access the text block element of the feedback group, you'll see several actions.
The second through last of these handle our xAPI statements.
Action 2 captures the user response in a new variable.
Action 3 sets a variable we'll be using for the object name in the custom statement.
Action 4 sets the verb display.
Action 5 sets the verb ID.
Action 6 sets the activity ID for the statement - enter the same value here you'd enter at publish.
The last action is our custom statement. Here, we take the values in those xAPI variables, and pull them together into some JS to send off a custom statement like the following.
Beyond just the statement you can review in your LRS, you can also filter on response with this one for some more sophisticated reporting.
If you make any edits, just be sure to check against the variable names in the custom statement JS to make sure nothing breaks.
After edits, you just need to publish your file to xAPI to get statements going to your LRS.
This article last reviewed Jan, 2019. The software may have changed since the last review.