- Quick Guides
- Getting Started
- 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
- Working with Audio and Video
Adobe Animate / Flash
Can't find the answer? Ask our Customer Solutions team.
xAPI Sequencing 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!!!
Today we'll be discussing the xAPI features of our Starter Sequencing Drag and Drop template.
In this file, as with most in a Lectora style, we've defaulted to Lectora's built-in statement options.
The way this file works is pretty simple, really.
When a learner has dropped all draggers and presses submit, we send a few statements...or don't, depending on how the learner performed.
They're all tied to the submit button.
If you select that element, you can see a number of xAPI statements that occur on mouse click.
The first 6 statement actions pertain to the draggers.
If the user successfully dropped a dragger, we send a "matched" "Dragger number" statement.
If they didn't, we don't. It uses a system variable to check if an answer was correct.
Check the conditionals here to see how we set this up.
We're also sending a mastered statement, if the user matched all draggers.
Again, there's a conditional here that's driven by a system variable.
If you select any of these actions, you can customize their values using Lectora's actions pane.
For the draggers, we've included their names, in plain text, but for the mastered statement, we've used a Lectora system variable for the page name.
Obviously, you can adjust this to anything you'd like.
After edits, you just need to publish your file to xAPI to get statements going to your LRS.