ELB Learning FAQs
ELB Learning's Frequently Asked Questions page is a central hub where its customers can always go to with their most common questions. These are the 328 most popular questions ELB Learning receives.
Frequently Asked Questions About ELB Learning
All files use fully-functional, unique slide masters to ensure editability and ease of use.
Placeholders are used as much as possible to provide you with more control over the design of your slide, should you choose to make changes or start a new slide from scratch.
To use a slide as-is, just edit over the content on stage. Object positions are already optimized for each device view for you.
To edit text, just select all and type away.
To edit imageslike characters or the background imagesyou’ll need to either delete the image that exists, then use the Captivate prompt to replace, or, simply adjust the fill of a smartshape placeholder. We use these two different methods based on what best suits the slide design at publish. We’ve included handy instructions just off stage to tip you off to the method used on a given slide.
To start a slide from scratch, navigate to the program menu, and select Insert > New Slide From, then select the master you’d like to use.
If you choose this option, you'll get placeholders for all critical elements on the stage that you can edit, resize, and/or reposition easily to match your content.
Some of the more decorative elements intended to reside above the bottom element of the master or that need to be edited on the timeline may be absent or static.
This is due to the way Captivate handles objects on the master layer.
In most cases, we’ve placed reference (decorative) items on the master for you to copy back into your working slide.
That said, the significant majority of decorative elements used throughout Course Starters are in-tool or custom SVGs that can be edited quite easily. This allows you to easily restyle, recolor, or re-use elements across a project or between projects.
View ArticleAlongside the enhanced masters, we provide a unique (and stylish) theme color palette and fonts for each design, wrapped up in a Captivate theme.
We take extra time to save out design-specific styles in the Object Style Manager (OSM), so that you can copy and paste within or between projects while both retaining the formatting you expect, AND finding and applying different styles quickly and easily.
Since we save the masters, fonts, colors, and styles in a Captivate theme, you can also apply that theme directly to a different project if you likethis can be a real life-saver in those “gotta make this look nice” update situations we’ve all encountered
View ArticleOur Course Starters use breakpoint mode in Captivate.
After working withand growing to really appreciatefluid boxes, we found that our development time wasn’t where we wanted it and our users reported similar findings.
We reverted back to the familiar breakpoint modeallowing you to target specific object positions or even slide layouts based on device dimension.
We also use a javascript portrait blocker to display a “rotate this device” message whenever a slide is being viewed in a portrait orientation. This allows you to control the display of interactions more specifically than you otherwise might be able to by simply rearranging elements based on a specific breakpoint dimension. Those “in-between” sizes can sometimes be a real chore to target, but this approach avoids that issue altogether. You can easily disable this feature by deleting two objects from the timeline.
View ArticleWe've aimed for accessibility-friendly design on all our Course Starters.
All themes have been designed with appropriate text color contrast ratios and fonts are appropriately sized to pass a minimum rating.
In general, we leave Captivate’s in-tool accessibility settings alone. But in the case of interactions, we've made some small tweaks to these settings to maximize the experience on a screen reader and enable easier xAPI reporting:
We’ve optimized tab order of all interactive objects on a slide.
This means buttons click through and interactive objects highlight in a logical order.
We’ve optimized the accessibility info for each interactive object.
Basically, this means we name all interactive objects contextually, and clearly. SmartShape_52 might instead be “Process Flow Button #3” for instance.
This not only improves the experience on a screen reader, but also ties into how we report xAPI data with Course Starters: whatever these elements are named is how they will appear in the LRS after reporting. Clear, concise, and contextual naming is key.
If you need to make changes to the accessibility settings, there are two main spots you’ll need to check:
To adjust tab order, select the slide, then the twirl-down adjacent the slide name in the properties pane.
To adjust the labeling of an object, just change its name in the properties pane and allow Captivate to auto-label. You can also manually edit if you like, by selecting the object and using the twirl down adjacent its name in the properties pane.
View ArticleAll files are grouped into 3 slide groups: layouts, interactions, and quiz.
( https://helpx.adobe.com/captivate/using/group-slides.html )
Similarly, slide masters flow from layouts to interactions and quiz.
All masters are named clearly and names correspond to their slide titles.
This persists throughout the new Course Starter familiesif you're familiar with the structure of one style, you'll be familiar with the structure of the rest.
View ArticleWe’ve taken a new approach to handling actions in Captivate: we now use Shared Actions for our interactive slides. We save and include the base advanced action for each, but rely on shared actions to do the heavy lifting in our templates. This may be a new feature to some Captivate users, and may be a breath of fresh air to those unfamiliar. Rather than hunt and peck through advanced actions and targets in the main pop-up, you can now simply highlight an object and navigate to the properties pane to affect its function.
Easily set targets with dropdowns, and ignore parameters that you don’t need to change (we’ve limited those from editing so you don’t need to worry!).
You can also re-use those actions across projects by pasting from one project’s library to another.
**In certain cases where an action will not be reused in a slide (i.e., a start button), we will use a standard advanced action.
Click to Reveals:
With rare exception, our click to reveals, timelines, pyramid interactionsbasically anything that has a "tab" and launches contentwork very, very similarly in each of our new Course Starters.
This allows for familiarity and ease of use across different filesif you know how the 4-Tab Click to Reveal works in Fira, you'll be able to easily edit the Pyramid in Montserrat.
All content for all elements is editable. Select an element and type; use the properties pane and select a new picture for images.
The best way to discover how one of these interactions works is to break apart the shared action. To do so, select a button/object, and then access the actions tab of the properties pane.
Then, press the parameters button next to the shared action for that object.
On the resulting pop-up, we’ve included a plain-English list of actions that the object is taking, along with a field you can use to edit or adjust the target of that action.
For instance, to adjust which content shows when a button is clicked, we might (in the example below) adjust the parameter value for “state change target in active content” to 02_04 instead of 01_03.
We’ve also included xAPI values for the display and ID values of verbs associated with each action. Just click and type to edit these.
Text Entry:
This is a freeform text entry interaction that uses Captivate’s text entry field to capture a learner's response. There is also a feedback object that repeats that captured response back to the learner, and provides prescriptive feedback. We also include an xAPI trigger to send that learner's statement to your LRS as an "Answered" statement with embedded response that can be charted rather easily.
To edit content, simply select a text element and type. To replace images, simply select the smart shape that contains the image and reassign the fill using the properties pane.
xAPI triggers are tied to the submit button. Edit the assigned advanced action to adjust the verb ID and display values for the statement.
Scenarios:
With rare exception, our scenarios will be set up the same way in Captivate.
To edit content, simply select a text element and type. To replace images, use the properties pane. Make sure to check all states!
All behaviors for clickable elements are tied to the action for that element. Edit via the properties pane.
To adjust which answers are correct/incorrect, access the shared action parameters in the properties pane.
Drag and Drop:
With rare exception, drag and drops will be built using Captivate’s interaction editor. This allows you to edit correct/incorrect pairings very easily, with no variables to concern yourself with.
To adjust correct answers, use the Drag and Drop > Options tab on the Properties pane.
To adjust the actions that occur when a dragger is dropped, select the dropzone, then press the Drag and Drop > Format tab, and select “Object Actions” Then adjust the advanced action for each.
There are two actions associated with this interaction: a correct and incorrect action.
Each of these control both what occurs on screen after an answer is given and the xAPI values for this interaction. Set the verb ID and verb Display values here.
View ArticleOn all Course Starter interaction slides, we include custom xAPI statements that track object-level learner actions.
Currently, Captivate only sends an "experienced" statement when a learner visits a slide.
No other data is really being sent about what they did on that slide.
We added to that by including custom statements on each of the objects in an interaction.
So if a user clicks a tab on slide 3, you'll see that in your LRS.
If they answered a text entry or chose option 2 in your scenario from slide 9, you'll see that too.
And we add context to our statements to map them back to the slide level and course-level for deeper analytics and better data display in your LRS.
Setup and approach is largely the same for all interactions.
Where elements use an advanced action for their behavior, you can access the full xAPI setup (similarly on the base versions of each of the shared actions we leave in a starter file).
Where elements use a shared action, you can access and edit the labels for the verb ID and verb display values via the shared actions parameters pane. You will not see the actions for the remaining steps in the xAPI sequence; other actions have been de-parameterized.
Almost all statements use the same Javascript.
There are a few exceptions, however.
Any interaction that includes a mastered/passed/failed interaction will include a bit more detail than a standard statement. In addition to the standard statement, we include a result element that indicates if they successfully completed the interaction or not.
The text entry statement also uses slightly different javascript for its statement. In addition to the standard statement we send, it also includes a response element that captures the full text of the learner's entry.
This response element should be fairly easy to chart in any LRS with an analytics package.
https://lrs.io/integrations/embedableCharts/?id=2fd6602c-69c0-45f3-97ce-2fa4d2412a25
Anywhere there are bigger changes to approach with xAPI, we'll note it in the interaction's instructions block at the left side of the stage.
View ArticleVariables are named specific to the interactions in the file.
For instance, the variable used to control the number of dates in our Playfair Textbox Interaction is: TextEnry_10013538.
In each variable, we include which interaction the variable belongs to, and which larger Course Starter file it belongs to (product number). Occasionally additional context about function may be included for more complicated interactions.
Variables that should not be edited by you start with a lowercase x.
For instance, xCheckbox2_Checked_10013538. This variable keeps track of whether or not box 2 of the Textbox Interaction has been selectednot something you're likely to want to worry about editing, and integral to the function of the template.
Don't change these values, or the file will probably break.
Exceptions are the xAPI variables. These do not include a product number and are global.
We keep them generic to make a few things clean and easy. Namely, minimizing the number of points where something could break with your xAPI statements.
One of the effects of keeping global variable names though, is that, if you paste slides that contain xAPI triggers between projects, you may encounter issues with naming in your advanced/shared actions. Make sure to double check (and reset as needed) these variable names after pasting between projects. We use these specific variable names in the Javascript statements we generate in interactions. If names are changed, statements will stop working.
View ArticleDid you know you can use fully-editable custom vectors - like icons, buttons, and shapes - in Storyline?
You can.
You just need to create and export them as an EMF from a graphics editing tool like Illustrator, then import them into Storyline, then break them apart, and then you can use them.
If you're getting vectors from a stock resource, they'll most likely be SVGs, in which case you'll still need to do all those things I just mentioned in order to get your vectors into Storyline.
Or, you can skip some of those steps (and the need for a vector-editing program entirely!!!) and use the nifty little hack that we use.
With every course starter, we include a PowerPoint file in the Graphic Source Files download.
This PPTx includes all the vector assets we use in that style of course starter.
It also acts as a handy middle-man to get those assets into the tool more easily.
See, if you open that PowerPoint file and navigate to the asset you'd like to import into Storyline 3/360, you can simply highlight, then copy and paste directly to the destination slide.
When you do, you'll see it's been brought over as a raster graphic (note the highlighted image icon in the timeline: "Picture 1").
If you highlight it, then press Shift + Control + G on your keyboard (or right-click and select Group > Ungroup), you'll notice that flat graphic gets broken into one or more freeform shapes.
These freeform shapes can be edited individually - change color, add or remove a stroke, or scale to your heart's content.
You can use this same trick to use vectors from our ever-expanding library too!
Don't like one of the icons we're using in a starter, or maybe just want to add something more reflective of your custom content?
Download a vector asset from eLearning Brothers, then import into PPT directly.
After that, copy, paste, and ungroup just like above.
Bingo bango.
And, to top it off, if you follow good working practices in Storyline and use a theme-based colors for all your edits, you'll notice your icons update to match your new style in case you ever switch design themes!
View Article***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/Setup video for Storyline yet?
For files released April 2019 and older, watch this video
For files released May 2019 and later, watch this video
In this video, we're going to take a quick look at how to use the xAPI features in this file.
In addition to the standard Storyline statements that fire in an xAPI publish, we've added some custom statements to give you some deep tracking on your interaction.
The setup is pretty simple really.
In this template, a user clicks one of the primary content buttons on screen, and a statement fires, indicating they did so.
The end result will look like this.
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.
View Article***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/Setup video for Storyline yet?
For files released April 2019 and older, watch this video
For files released May 2019 and later, watch this video
In this video, we're going to take a quick look at how to use the xAPI features in this file.
In addition to the standard Storyline statements that fire in an xAPI publish, we've added some custom statements to give you some deep tracking on your interaction.
The setup is pretty simple really.
In this template, a user clicks one of the primary content buttons on screen, and a statement fires, indicating they did so.
The end result will look like this.
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.
View Article***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/Setup video for Storyline yet?
For files released April 2019 and older, watch this video
For files released May 2019 and later, watch this video
In this video, we're going to take a quick look at how to use the xAPI features in this file.
In addition to the standard Storyline statements that fire in an xAPI publish, we've added some custom statements to give you some deep tracking on your interaction.
The setup is pretty simple really.
In this template, a user clicks one of the primary content buttons on screen, and a statement fires, indicating they did so.
The end result will look like this.
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.
(SHOW CONTEXT CHARTS IN DASH)
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.
View Article***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/Setup video for Storyline yet?
For files released April 2019 and older, watch this video
For files released May 2019 and later, watch this video
In this video, we're going to take a quick look at how to use the xAPI features in this file.
In addition to the standard Storyline statements that fire in an xAPI publish, we've added some custom statements to give you some deep tracking on your interaction.
The setup is pretty simple really.
In this template, a user clicks one of the primary content buttons on screen, and a statement fires, indicating they did so.
The end result will look like this.
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.
View Article***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/Setup video for Storyline yet?
For files released April 2019 and older, watch this video
For files released May 2019 and later, watch this video
In this video, we're going to take a quick look at how to use the xAPI features in this file.
In addition to the standard Storyline statements that fire in an xAPI publish, we've added some custom statements to give you some deep tracking on your interaction.
The setup is pretty simple really.
In this template, a user clicks one of the primary content buttons on screen, and a statement fires, indicating they did so.
The end result will look like this.
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.
View Article***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/Setup video for Storyline yet?
For files released April 2019 and older, watch this video
For files released May 2019 and later, watch this video
In this video, we're going to take a quick look at how to use the xAPI features in this file.
In addition to the standard Storyline statements that fire in an xAPI publish, we've added some custom statements to give you some deep tracking on your interaction.
The setup is pretty simple really.
In this template, a user clicks one of the primary content buttons on screen, and a statement fires, indicating they did so.
The end result will look like this.
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.
View Article***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/Setup video for Storyline yet?
For files released April 2019 and older, watch this video
For files released May 2019 and later, watch this video
Our Starter Layout file is very simple, when it comes to statements.
All slides except the text entry slide use Storyline's default statements only.
The text entry slide has a custom statement included that will capture your user's response in a way that can be reported and charted using an LRS' analytics package.
When the user enters information on this slide, a statement gets sent to your LRS that looks something like the following.
On it's face, that's not a super-useful statement, really.
So, someone answered something...ok. Now what?
If you look at the full JSON for this statement, however, you'll see a "response" entry here, that contains the full text the user entered.
Even better, if you use your LRS' analytics to generate reports on responses dfor a specific ID, you can visualize these answers across the entire user base.
Like this.
Pretty cool.
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.
View Article***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/Setup video for Storyline yet?
For files released April 2019 and older, watch this video
For files released May 2019 and later, watch this video
Our popular choice game is a feature-packed feud-style game that not only quizzes your users in a fun and engaging way, but captures their responses and reports them back in a way you can graph, chart, filter, organize...or whatever practical verb you choose!
In addition to the default Storyline "experienced," "attempted," and "completed" statements for this file, we've added a custom statement to the answer field.
When your user presses enter or the submit button, a statement gets sent to your LRS that looks something like the following: user "answered question."
While the display statement doesn't give you a ton of at-a-glance information, the full JSON contains the entire text the user entered.
We've included a "results > response" section in the xAPI statement for this one, that grabs the text entry box's value.
If you set up reports on responses for a specific ID, you'll get something like the following.
[ANALYTICS VIEW]
Additionally, we've included a custom statement on the results slide that captures the users score and reports on success.
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 information.
View Article***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/Setup video for Storyline yet?
For files released April 2019 and older, watch this video
For files released May 2019 and later, watch this video
In this video, we're going to take a quick look at how to use the xAPI features in this file.
In addition to the standard Storyline statements that fire in an xAPI publish, we've added some custom statements to give you some deep tracking on your interaction.
The setup is pretty simple really.
In this template, a user clicks one of the primary content buttons on screen, and a statement fires, indicating they did so.
The end result will look like this.
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.
View Article***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/Setup video for Storyline yet?
For files released April 2019 and older, watch this video
For files released May 2019 and later, watch this video
In this video, we're going to take a quick look at how to use the xAPI features in this file.
In addition to the standard Storyline statements that fire in an xAPI publish, we've added some custom statements to give you some deep tracking on your interaction.
The setup is pretty simple really.
In this template, a user clicks one of the primary content buttons on screen, and a statement fires, indicating they did so.
The end result will look like this.
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.
View Article***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/Setup video for Storyline yet?
For files released April 2019 and older, watch this video
For files released May 2019 and later, watch this video
In this video, we're going to take a quick look at how to use the xAPI features in this file.
In addition to the standard Storyline statements that fire in an xAPI publish, we've added some custom statements to give you some deep tracking on your interaction.
The setup is pretty simple really.
In this template, a user clicks one of the primary content buttons on screen, and a statement fires, indicating they did so.
The end result will look like this.
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.
View Article***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/Setup video for Storyline yet?
For files released April 2019 and older, watch this video
For files released May 2019 and later, watch this video
In this video, we're going to take a quick look at how to use the xAPI features in this file.
In addition to the standard Storyline statements that fire in an xAPI publish, we've added some custom statements to give you some deep tracking on your interaction.
The setup is pretty simple really.
In this template, a user clicks one of the primary content buttons on screen, and a statement fires, indicating they did so.
The end result will look like this.
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.
View Article***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/Setup video for Storyline yet?
For files released April 2019 and older, watch this video
For files released May 2019 and later, watch this video
In this video, we're going to take a quick look at how to use the xAPI features in this file.
In addition to the standard Storyline statements that fire in an xAPI publish, we've added some custom statements to give you some deep tracking on your interaction.
The setup is pretty simple really.
In this template, a user clicks one of the primary content buttons on screen, and a statement fires, indicating they did so.
The end result will look like this.
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.
View Article***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/Setup video for Storyline yet?
For files released April 2019 and older, watch this video
For files released May 2019 and later, watch this video
In this video, we're going to take a quick look at how to use the xAPI features in this file.
In addition to the standard Storyline statements that fire in an xAPI publish, we've added some custom statements to give you some deep tracking on your interaction.
The setup is pretty simple really.
In this template, a user clicks one of the primary content buttons on screen, and a statement fires, indicating they did so.
The end result will look like this.
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.
View Article***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/Setup video for Storyline yet?
For files released April 2019 and older, watch this video
For files released May 2019 and later, watch this video
In this video, we're going to take a quick look at how to use the xAPI features in this file.
In addition to the standard Storyline statements that fire in an xAPI publish, we've added some custom statements to give you some deep tracking on your interaction.
The setup is pretty simple really.
In this template, a user clicks one of the primary content buttons on screen, and a statement fires, indicating they did so.
The end result will look like this.
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.
View Article***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/Setup video for Storyline yet?
For files released April 2019 and older, watch this video
For files released May 2019 and later, watch this video
In this video, we're going to take a quick look at how to use the xAPI features in this file.
In addition to the standard Storyline statements that fire in an xAPI publish, we've added some custom statements to give you some deep tracking on your interaction.
The setup is pretty simple really.
In this template, a user clicks one of the primary content buttons on screen, and a statement fires, indicating they did so.
The end result will look like this.
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.
View Article***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/Setup video for Storyline yet?
For files released April 2019 and older, watch this video
For files released May 2019 and later, watch this video
Our Sorting Drag and Drop template includes several custom statements, in addition to the standard Storyline slide-level statements.
When a learner drops a dragger onto the correct drop zone, the template fires a statement like the following: user "sorted dragger #"
When the user successfully completes the activity, and is shown the Correct layer, a "Mastered" statetment, including a result = true element fires.
We've included some context in our satements that will relate them to the standard Storyline statements for reporting.
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.
View Article***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/Setup video for Storyline yet?
For files released April 2019 and older, watch this video
For files released May 2019 and later, watch this video
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.
View Article***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/Setup video for Storyline yet?
For files released April 2019 and older, watch this video
For files released May 2019 and later, watch this video
The Starter 2-Column Drag and Drop activity is a one-to-many dragger, with a correct feedback layer that shows when both columns have been matched.
It sends 3 statements total: 1 when the state of column 1 header is "Drop Correct", 1 when the state of column 2 header is "Drop Correct", and 1 when the "Correct" layer appears.
They look something like this.
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.
View Article***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/Setup video for Storyline yet?
For files released April 2019 and older, watch this video
For files released May 2019 and later, watch this video
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 on it 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 "disabled," we throw a statement: user "matched dragger #"
When the Correct feedback layer appears, we throw a statement: user "mastered the sequencing drag and drop activity"
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 info.
View Article***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/Setup video for Storyline yet?
For files released April 2019 and older, watch this video
For files released May 2019 and later, watch this video
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 on it 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 dragger #"
When the Correct feedback layer appears, we throw a statement: user "mastered the sequencing drag and drop activity"
When the Incorrect feedback layer appears, we throw a statement: user "failed the sequencing drag and drop activity"
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.
View Article***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/Setup video for Storyline yet?
For files released April 2019 and older, watch this video
For files released May 2019 and later, watch this video
Our Starter Quiz template uses default statements from Storyline to provide detail on your user's actions.
To use these statements, you'll need to make sure you're using the results slide included with the template - or another results slide of your choosing.
Then, at publish, make sure that tracking is set based on that results slide.
Publish that file out, upload it and launch, and you should have clean statements that look something like the following.
Using the analytics on your LRS, you can drill down to review student answers, scores, etc.
It's a thing of beauty.
View Article***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/Setup video for Storyline yet?
For files released April 2019 and older, watch this video
For files released May 2019 and later, watch this video
In this video, we're going to take a quick look at how to use our labels drag and drop template.
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.
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 "Correct," we throw a statement: user "matched dropzone #"
If they answer correctly, we send a "mastered" statement that includes a success = true result.
If they don't, we send a "failed" statement, with a success = false result.
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.
View Article***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/Setup video for Storyline yet?
For files released April 2019 and older, watch this video
For files released May 2019 and later, watch this video
The Timeline Slider template uses our custom xAPI statement to send a statement to your LRS whenever a content box swicthes to its ACTIVE state.
This will occur whether a learner is seeing that content for the first time, or on review.
If you'd like to trigger it to only fire on the first view, you'll need to set up some triggers and customize the template a little bit.
In either case, the statement will look something like this - user "reviewed timeline slider point #".
Those statements also list their parent as the slide the learner is currently vieweing, and the group as the activity ID for the whole course.
For more information on that, check out the deep dive on context by xapi.com (https://xapi.com/blog/deep-dive-context/)
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 info.
View Article***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/Setup video for Storyline yet?
For files released April 2019 and older, watch this video
For files released May 2019 and later, watch this video
In this video, we're going to take a quick look at how to use the xAPI features in this file.
In addition to the standard Storyline statements that fire in an xAPI publish, we've added some custom statements to give you some deep tracking on your interaction.
The setup is pretty simple really.
In this template, a user clicks one of the primary content buttons on screen, and a statement fires, indicating they did so.
The end result will look like this.
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 information.
View Article***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/Setup video for Storyline yet?
For files released April 2019 and older, watch this video
For files released May 2019 and later, watch this video
In this video, we're going to take a quick look at how to use the xAPI features in this file.
In addition to the standard Storyline statements that fire in an xAPI publish, we've added some custom statements to give you some deep tracking on your interaction.
The setup is pretty simple really.
In this template, a user clicks one of the primary content buttons on screen, and a statement fires, indicating they did so.
The end result will look like this.
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.
View Article***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/Setup video for Storyline yet?
For files released April 2019 and older, watch this video
For files released May 2019 and later, watch this video
In this video, we're going to take a quick look at how to use the xAPI features in this file.
In addition to the standard Storyline statements that fire in an xAPI publish, we've added some custom statements to give you some deep tracking on your interaction.
The scrolling text scenario presents the learner with several buttons, after scrolling through a scenario on screen.
The learner may select any of these buttons until they get a correct response.
At each button selection, a statement will be sent, indicating the user "selected scrolling text scenario 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.
View Article***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/Setup video for Storyline yet?
For files released April 2019 and older, watch this video
For files released May 2019 and later, watch this video
In this video, we're going to take a quick look at how to use the xAPI features in this file.
In addition to the standard Storyline statements that fire in an xAPI publish, we've added some custom statements to give you some deep tracking on your interaction.
When the user scrolls trough the messages shown on the device in this interaction, they will be shown 4 buttons.
Each of these buttons has a statement tied to it, that indicates the user "reviewed tablet (or mobile) scenario #"
As it is currently built, these statements fire each time a button is clicked - the user can select multiple buttons after the first is chosen, firing additional statements about their selections.
If you'd like to limit this to only a single selection, consider adding a blocker by way of a transparent shape, or hotspot with triggers removed, on top of the buttons after intiial selection.
Alternatively, apply triggers to the content layers to disable each button on the base layer to prevent additional selections.
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.
View Article***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/Setup video for Storyline yet?
For files released April 2019 and older, watch this video
For files released May 2019 and later, watch this video
In this video, we're going to take a quick look at how to use the xAPI features in our email scenario file.
In addition to the standard Storyline statements that fire in an xAPI publish, we've added some custom statements to give you some deep tracking on your interaction.
On the base layer, you'll see four groups of triggers - one for each of the tabs at left.
When the appropriate layer shows, there are two additional statements that *may* fire, depending on the user's response.
It works like this -
When the user clicks the first email tab, a statement fires indicating they "reviewed email scenario message 1."
Then, the email 1 sublayer opens.
On this layer, the user chooses between button 1 and button 2 in response to the email shown on screen.
When they make a selection, a custom statement indicating the user "selected email scenario 1 button 1" - for instance - is shown.
We've also included a "started" statement on the introduction layer that fires when the user presses the start button.
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.
View Article***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/Setup video for Storyline yet?
For files released April 2019 and older, watch this video
For files released May 2019 and later, watch this video
In this video, we're going to take a quick look at how to use the xAPI features in this file.
In addition to the standard Storyline statements that fire in an xAPI publish, we've added some custom statements to give you some deep tracking on your interaction.
On the base layer, you'll see three stacks of statement triggers - one for each of the images at bottom.
When the appropriate layer shows, there are two additional statements that *may* fire, depending on the user's response.
It works like this -
When the user clicks the "content 1" image, a statement fires indicating they "reviewed Content 1."
Then, the content 1 sublayer opens.
On this layer, the user can choose to vote up or vote down the content.
A custom statement such as user "voted up content 1" or "voted down content 1" fires, depending on which they choose.
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.
View Article***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/Setup video for Storyline yet?
For files released April 2019 and older, watch this video
For files released May 2019 and later, watch this video
Today, 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.
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 user presses the submit button, we throw a single statement indicating which button they selected.
This statement is contextually related to some values you enter for the slide identifier.
This makes it 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.
If you look closely at the triggers pane, you'll note that the actual statement only occurs once on this template.
It fires when the submit button is clicked, and sends whatever the last updated variable values were, prior to clicking that button.
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.
View Article***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/Setup video for Storyline yet?
For files released April 2019 and older, watch this video
For files released May 2019 and later, watch this video
In this video, we're going to take a quick look at how to use the xAPI features in our checkbox knowledge check template.
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.
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 user presses the submit button, we throw statements for each box they selected: "user selected checkbox 1"
If they answer correctly, we send a "mastered" statement that includes a success = true result.
If they don't, we send a "failed" statement, with a success = false result.
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.
View Article***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/Setup video for Captivate yet?
For files released April 2019 and older, watch this video
For files released May 2019 and later, watch this video
Our Layout file primarily uses standard Captivate xAPI statements.
In fact, all but 1 slide do.
When the Text Entry Response slide loads, the _load_textEntry_ action fires.
In it, we set several xAPI variables and send out some JS that will produce a statement like the following:
In addition to the actor/verb/object information, we include a response element in this statement, that captures the user's full text response.
To customize that statement, edit the xAPI variables on the first tab of the load text entry action, then publish to xAPI, and you're good to go.
View Article***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/Setup video for Captivate yet?
For files released April 2019 and older, watch this video
For files released May 2019 and later, watch this video
Our Starter Quiz mostly uses default statements from Captivate to provide detail on your user's actions.
We've included a single custom statement on question 4 (the matching dropdown question), and formatted it to match the standard Captivate statements.
That means there's nothing necessary to edit in this template, xAPI-wise.
To use these statements, you'll need to make sure you're using the results slide included with the template - or another results slide of your choosing.
Then, at publish, make sure that the following are set on the publish preferences dialogue:
Completion Criteria should be set to Slide Views and/or Quiz
Select Success Criteria and select Quiz is passed.
Finally, ensure Interaction Data is selected under the "Data to Report" section.
Publish that file out, upload it and launch, and you should have clean statements that look something like the following.
Using the analytics on your LRS, you can drill down to review student answers, scores, etc.
It's a thing of beauty.
View Article***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/Setup video for Captivate yet?
For files released April 2019 and older, watch this video
For files released May 2019 and later, watch this video
In this video, we're going to take a quick look at how to use the xAPI features in this file.
In addition to the standard Captivate statements that fire in an xAPI publish, we've added some custom statements to give you some deep tracking in your interaction.
The setup is pretty simple really.
In this template, a user clicks one of the primary content buttons on screen, and a statement fires, indicating they did so.
The end result will look like this.
Each of these statements are contextually related to some values you enter for the course 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, navigate to the "advanced actions" tab.
On each tab action, you'll see a number of variables and an Execute JS trigger.
Enter the details for your slide in the variables here, then press OK to update the action.
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
View Article***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/Setup video for Captivate yet?
For files released April 2019 and older, watch this video
For files released May 2019 and later, watch this video
In this video, we're going to take a quick look at how to use the xAPI features in this file.
In addition to the standard Captivate statements that fire in an xAPI publish, we've added some custom statements to give you some deep tracking in your interaction.
The setup is pretty simple really.
In this template, a user clicks one of the primary content buttons on screen, and a statement fires, indicating they did so.
The end result will look like this.
Each of these statements are contextually related to some values you enter for the course 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, navigate to the "advanced actions" tab.
On each tab action, you'll see a number of variables and an Execute JS trigger.
Enter the details for your slide in the variables here, then press OK to update the action.
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
View Article***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/Setup video for Captivate yet?
For files released April 2019 and older, watch this video
For files released May 2019 and later, watch this video
In this video, we're going to take a quick look at how to use the xAPI features in this file.
In addition to the standard Captivate statements that fire in an xAPI publish, we've added some custom statements to give you some deep tracking in your interaction.
The setup is pretty simple really.
In this template, a user clicks one of the primary content buttons on screen, and a statement fires, indicating they did so.
The end result will look like this.
Each of these statements are contextually related to some values you enter for the course 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, navigate to the "advanced actions" tab.
On each tab action, you'll see a number of variables and an Execute JS trigger.
Enter the details for your slide in the variables here, then press OK to update the action.
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
View Article***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/Setup video for Captivate yet?
For files released April 2019 and older, watch this video
For files released May 2019 and later, watch this video
In this video, we're going to take a quick look at how to use the xAPI features in this file.
In addition to the standard Captivate statements that fire in an xAPI publish, we've added some custom statements to give you some deep tracking in your interaction.
The setup is pretty simple really.
In this template, a user clicks one of the primary content buttons on screen, and a statement fires, indicating they did so.
The end result will look like this.
Each of these statements are contextually related to some values you enter for the course 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, navigate to the "advanced actions" tab.
On each tab action, you'll see a number of variables and an Execute JS trigger.
Enter the details for your slide in the variables here, then press OK to update the action.
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
View Article***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/Setup video for Captivate yet?
For files released April 2019 and older, watch this video
For files released May 2019 and later, watch this video
In this video, we're going to take a quick look at how to use the xAPI features in this file.
In addition to the standard Captivate statements that fire in an xAPI publish, we've added a number of custom statements to give you some deep tracking on your interaction.
There are two types of custom statements in this file: 1 type fires when each dragger is placed in the correct dropzone.
It looks like this.
The second type fires when the interaction is complete, and looks like this.
If you review the full JSON, you'll see that we've added some detail about the correct response pattern, and how the user actually responded.
Each of these statements are contextually related to some values you enter for the course identifier.
This makes them easy to sort and filter, and provides some nice visualization in the analytics dashboard of your LRS.
Since they're structured differently, each type can be filtered and reported on differently.
Each can also be disabled or edited quickly and easily.
To use our statements, navigate to the "advanced actions" tab.
On the check answer action, you'll see a number of tabs labeled 1-6 - on each of these, you'll see several xAPI variables and an Execute JS trigger.
Enter the details for your slide in the variables here, then press OK to update the action.
Make sure to check out our xAPI overview video for more details on these details.
The "answered" statement is on its own tab in this same action group. It's called xAPI-Answered.
Once you edit the values you're going to edit, 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
View Article***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/Setup video for Captivate yet?
For files released April 2019 and older, watch this video
For files released May 2019 and later, watch this video
In this video, we're going to take a quick look at how to use the xAPI features in this file.
In addition to the standard Captivate statements that fire in an xAPI publish, we've added a number of custom statements to give you some deep tracking on your interaction.
There are two types of custom statements in this file: 1 type fires when each column is matched.
It looks like this.
The second type fires when the interaction feedback shows, and looks like this.
If you review the full JSON, you'll see that we've added some detail about the correct response pattern, and how the user actually responded.
Each of these statements are contextually related to some values you enter for the course identifier.
This makes them easy to sort and filter, and provides some nice visualization in the analytics dashboard of your LRS.
Since they're structured differently, each type can be filtered and reported on differently.
Each can also be disabled or edited quickly and easily.
To use our statements, navigate to the "advanced actions" tab.
On the show feedback action, you'll see three tabs - check ans1, check ans2, and show feedback.
On each of these, you'll see several xAPI variables and an Execute JS trigger.
The statement for column 1 is on check ans1, column 2 is on check ans2, and the answered statement is on the show feedback tab.
Enter the details for your slide in the variables here, then press OK to update the action.
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
View Article***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/Setup video for Captivate yet?
For files released April 2019 and older, watch this video
For files released May 2019 and later, watch this video
In this video, we're going to take a quick look at how to use the xAPI features in this file.
In addition to the standard Captivate statements that fire in an xAPI publish, we've added some custom statements to give you some deep tracking on your interaction.
The setup is pretty simple really.
In this template, a user clicks one of the primary content buttons on screen, and a statement fires, indicating they did so.
The end result will look like this.
Each of these statements are contextually related to some values you enter for the course 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, navigate to the "advanced actions" tab.
On each of the content actions, you'll see a number of variables and an Execute JS trigger.
Enter the details for your slide in the variables here, then press OK to update the action.
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
View Article
Working at ELB Learning
ELB Learning's Competitors
Recently Asked Questions
- What are the differences between maternity and paternity leave at Parallon Business Solutions?
- How would you compare interviewing at ERPA to other places you've interviewed?
- Does Ensemble drug test or do a background check?
- What's the Sales team like at DXC Technology?
- What unique perks and benefits does Carnegie Learning provide?