Having Issues Bookmarking with Captivate Content


Captivate 3 may not be setting an exit type.   When you exit the content, it should be setting cmi.exit to 'suspend', this tells the LMS that the learner intends to return to the content at the point of exit. We have a SCORM Package Property that you can use in SCORM Cloud to test this theory. It is called 'Reset Runtime Data Timing' and is located on the 'Compatibility Settings' tab in the Course Properties section. If you set this to 'Never', then relaunch the content, you should get bookmarking working from there.  The question is, how do you make this work when using the SCORM Engine...

For SCORM Engine and SCORM Cloud users, we created the "Reset RunTime Data Timing" element so that if content does not set cmi.exit...then you can make it so the runtime data never gets reset... You can set this for SCORM Engine users in a couple of ways.

1. You can reference an external metadata file from the manifest to pass other attributes to the content. At the root of the manifest, you can reference the file and it will pass the specific option you want to the be used in the SCORMPackageProperties table of the SCORM Engine. If this is the option we use, I can show you which files you need and how to change the properties.

2. You can have your LMS Administrator change the option for this specific content in the SCORMPackageProperties manually. This is a fairly simple fix, BUT you will need to do it for each package that gets imported into eLogic.

3. If you want all of your content to have this attribute, you can have your LMS Administrator use an override method that sets the default for this element to 'Never'. Every piece of content that is imported into the LMS will have this default...

The only other option is to contact Captivate support and ask them why cmi.exit is not getting set. I attached a copy of the detail tree from SCORM Cloud to show you where it is being set to 'unknown'. They also discuss it in this thread: I know this is a lot to take in.

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