Adobe Captivate

Watershed can receive data from any xAPI conformant Activity Provider. Many Watershed cards are flexible and you can configure Watershed to display useful visualizations and metrics from almost any xAPI data set. To help you get the most out of your data, we’re working with a number of product vendors to ensure that the data they send is optimized to produce the best possible results in Watershed. We want to help you to configure Watershed cards in the best way possible to display that data.

This guide tells you how to correctly configure and publish Adobe Captivate courses and then configure Watershed to get the best results.

This guide has 4 sections:

Configuring and publishing Captivate courses

This section outlines what you need to do within Captivate in order for it to produce the best data for Watershed to work with. If you have existing Captivate courses published without following this guidance, we recommend that you re-publish the courses following this guidance.

Important: Use the latest version

Each version of Captivate includes improvements in xAPI tracking so we recommend that you always use the latest version. This guide is written for Captivate 9 which was released in August 2015.

Give slides and objects helpful names and identifiers

The names and identifiers you use for slides and objects within Captivate will be reflected in Watershed reports, so it’s important to choose good names. Instead of “Untitled Slide”, give each slide a name. Instead of “Oval Hotspot 4”, name your hotspot according to which part of the picture it’s covering. This is a little extra work, but worthwhile so you know what’s what when it comes to looking at the reports in Watershed.

Publish to xAPI

When publishing, ensure that you’ve selected the xAPI Standard and completed all of the other settings in the Reporting section of the Publish settings. Be sure to click the Configure button next to the Standard dropdown and enter an Identifier, Title and Description for your course.

The Identifier field is the most important. This should take the form of a web address. We recommend the format https://[your oragnization’s website]/xapi/captivate/[unqiue course id]. For example, if we created an e-learning course titled ‘Using Captivate with Watershed’, it might have the id https://watershedlrs.com/xapi/captivate/using-captivate-with-watershed-10142015.

Including the date on the end helps to ensure that the id is unique within our organization. We also recommend that you keep a record of the identifiers you use within your organization to avoid using the same one twice for similar courses. Whenever you re-publish a course you should use exactly the same identifier. If you change the identifier, Watershed will treat it as a completely new course.

Making changes

If you need to make changes to a course after learners have started using it, we recommend that you make a backup of your Captivate project file before making any changes, that you make the changes carefully, and that you test the new version with you reports before releasing it to learners. Deleting and re-creating slides and objects could result in the identifiers of those slides and objects changing accidentally, which could adversely affect your reports.

Avoid the ‘Sequencing’ question type

Captivate does not report the learner’s response to sequencing type questions in the format prescribed by the xAPI specification so Watershed will not display the learner’s response to this type of question. We recommend that you avoid this question type if you want to report on learner responses.  

Launching Captivate courses

When you publish a Captivate course, the course does not know who the learner is or where to send the tracking data. The course has to be told this information when the course is launched by a training delivery system, normally an LMS. The training delivery system should handle collecting information about who the learner is, but you’ll need to configure it with your Watershed LRS credentials and endpoint. Exactly where these configuration settings are entered will depend on what system you are using.

If you find that no tracking data is being sent to Watershed, it may be that you're hitting an issue where the auth querystring parameter is not being picked up by the course. This results the authentication header being set to "null" and the requests being rejected as unauthorized by the LRS. If that's the case, you can solve this by making an edit to the scormdriver.js file. On line 1146, there's a function called parseURL which you can replace with the latest version of that function from TinCanJS

See How do I add an activity provider to Watershed? for details of where to find your endpoint and credentials in Watershed. Ask us if you need help configuring your LMS or other training delivery system, or for advice on launching content without an LMS (e.g. from an e-mail, text message or QR code).

Reporting on Captivate Data

Data from e-learning courses like those created in Captivate works especially well with the Activity Card, which offers both an overview of course usage and results, and question or learner level analysis. Depending on your questions, the data can also be used with any Watershed card, either on it’s own or in combination and comparison with data from other sources.

Completing question metadata with the Activity Editor

xAPI question data includes a list of the interaction components presented to the learner to select from, match, order or do with whatever the question demands. Watershed uses this data to display the text of the options presented to the learner and of the option they selected. Captivate omits this data, so you’ll need to use the Watershed Activity Editor to fill in the gaps.

Please note: this task requires advanced configuration and some knowledge of JSON and xAPI. Please ask us for help if you need to.

Publish your Captivate course, load it into your Watershed connected LMS and run through the course to generate data in Watershed. You can then create an Activity card for the e-learning course you just published. You’ll notice that the question options do not look quite right:

Now go to Settings and then Activity Editor. Search for the question by name and then open the Advanced tab. You’ll see a definition that looks similar to this:

{
  "description": {
    "en-US": "What is the capital of New York?"
  },
  "type": "http://adlnet.gov/expapi/activities/cmi.interaction",
  "interactionType": "choice",
  "correctResponsesPattern": [
    "urn:scormdriver:Albany%20(yes)"
  ]
}

Following the examples in the xAPI specification, complete the activity definition. Take care to ensure that the interaction component ids you use match those used by Captivate for the response and correctResponsesPattern properties or else you might see some options appear twice in your reports. The final result might look like this:

{
  "description": {
    "en-US": "What is the capital of New York?"
  },
  "type": "http://adlnet.gov/expapi/activities/cmi.interaction",
  "interactionType": "choice",
  "correctResponsesPattern": [
    "urn:scormdriver:Albany%20(yes)"
  ],
  "choices": [
      {
          "id": "urn:scormdriver:Albany%20(yes)", 
          "description": {
              "en-US": "Albany (yes)"
          }
      },
      {
          "id": "urn:scormdriver:New%20York", 
          "description": {
              "en-US": "New York"
          }
      },
      {
          "id": "urn:scormdriver:Rochester", 
          "description": {
              "en-US": "Rochester"
          }
      }
  ]
}

In your report, you’ll now see the complete list of options:

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

If you can't find what you need or you want to ask a real person a question, please contact customer support.