Output Options in Captivate – Part 2: Overview
The tracking options in the Quiz manager dialog box (see Figure 1) are very similar to what was available in previous versions of RoboDemo. However, the architecture of the communication has been modified to better support the AICC standard and additional tracking mechanisms. The support now includes two-way content communication, where the Captivate content is capable of both sending and receiving information from an AICC-compliant LMS. Previous versions of RoboDemo content only sent AICC-formatted data to an AICC-compliant LMS.
The tracking options available in Captivate are:
- QuestionMark Perception
This article focuses on AICC-tracking. I will cover other tracking mechanisms in parts three and four.
Using the Sample Files
This section briefly discusses the sample files that you can download.
AICC Course Structure Files
This folder contains a sample set of AICC Course Structure files that you can use to import your courses into your LMS. You can use the four files in that folder as a template that you can modify for your own courses and course structures.
This folder contains two additional files for creating and opening your Captivate files from a frameset. While Captivate does not require your content to be opened from a frameset for two-way tracking to occur, there may be instances (such as hosting your content in a different domain from your LMS) that may require you to use framesets to support any level of tracking (even one-way tracking).
The Captivate folder contains both source and packaged files of Captivate content created for AICC tracking. This gives you an idea of what the source files look like and what packaged files you’ll need to deploy for successful integration with your AICC-compliant LMS. The packaged folder contains both the typical published Captivate content, as well as content hosted in a frameset, using the AICC frameset files.
Cross-domain Policy file
This contains a sample cross-domain policy file that allows posts from Flash files from any domain. You must host this file at the root of the LMS web server (not the content server). We do not recommend allowing posts from Flash files hosted on any domain; it’s a very simple example file that you can modify to allow posts from specific domains that host your Flash-based content. You can find more information on the Flash Player security restrictions in Security Changes in Flash Player 7.