I was afraid it was something like that, Jim. Do you have any advice or approaches to pull off something similar that have worked in the past?
I assume you've asked this question here:
I asked a similar question here:
Philip gave you sound advice. You'll have to hijack/re-purpose the comments or the suspend data. I was successful in using SCORM comments in a Moodle system to store extra data I needed for a customer. It's not ideal, but it gets the job done. Here's a thread about that:
If you use suspend data, you have to watch out for a few things:
1. It's base 64 encoded... so any data you append to what Captivate outputs will need to be in base 64 (that's a good practice anyway since the data has to be serialized).
2. On course re-entry, you'll need to capture the suspend data before it hits Cp to strip off / read your needed data. If the suspend data isn't in the format Cp expects, you'll get a nice white screen of death.
Ideally, it would be nice to be able to dynamically create user variables for purposes like this... and it's been requested in Cp 6.... we'll see if it gets added (not holding my breath). Until then, I'd use cmi.comments.
Yep, that was me! I just figured I'd check for a second opinion before I cut open the patient.
I had considered hijacking the suspend_data as you suggested, but as you also mentioned it seems like it could be pretty brittle.
Thanks for the advice. I'll give cmi.comments, and thanks for the heads up about Cp6!