Another improvement in Adobe Captivate 5.5 is in the SCORM Reporting area. While this area does need quite a lot of more work if you ask me, then a couple of things have been implemented to make life easier with Adobe Captivate 5.5
The areas in Adobe Captivate 5.5’s SCORM reporting that have changed are:
- imsManifest issues – I’m not entirely sure what have been fixed here so I’ll need to do some testing in this area first.
- Customizable LMS Initializing text. This is a much needed feature, which allows you to modify the text that appears when Adobe Captivate 5.5 first starts to communicate with your LMS.
- New SCORM Template (SendTrackingDataAtEnd) has been added.
I’d like to go into a few more details to explain the last part about the new SCORM template.
Currently the default template in Adobe Captivate 5 and Adobe Captivate 5.5 sends the data to the LMS continously. Now this is normally not an issue but Adobe Captivate basically bombards your LMS with information. If you try and run an Adobe Captivate course in your LMS in FireFox with FireBug enabled you will be able to see the amount of data (and data requests) being sent to the LMS. Under normal circumstances this should not be a problem but it can actually create big problems in two cases:
1) If you have a large amount of users taking the course in your LMS at the same time then there is a real risk of your LMS being flooded with requests and that might result in data being lost or poor performance for the users.
2) If you have a user that skips through the course quickly and finally exits the course then there is a risk that the large amount of data that Captivate sends to your LMS is backlogged and once the users exists your course the LMS will not recieve the crucial commit and terminate commands resulting in your course not being set as completed.
This new template should fix these issues.