SCORM reporting in Adobe Captivate has always been a cause of great frustration for a lot of people. The files that Adobe Captivate produces are filled with HTML and JavaScript errors, redundant code and produces an excessive amount of API calls to your LMS.
This has always been the case with SCORM Reporting in Adobe Captivate and the current files (and errors) have persisted through many versions of Adobe Captivate. They are still present in the latest version – Adobe Captivate 5.5.
At my job we never use the Adobe Captivate SCORM files since we have experienced lots of problems when using them. The HTML and JS errors caused the files not to work properly in all browsers. Another issue we had was when we deployed courses to a very large user base and had many simoultaneous users taking the course in the LMS, we saw that the Adobe Captivate SCORM templates flooded the LMS with SCORM calls.
Therefore we use our own HTML and JS files to handle all SCORM communication from Adobe Captivate.
Now Philip from http://www.pipwerks.com/ has done a gigantic work of re-factoring the Adobe Captivate 5.5 SCORM reporting files from scratch. Gone are all the HTML and JavaScript errors, the weird loops checking to see if the user is using IE and the excessive SCORM communications has been reduced.
This is absolutely brilliant work and I highly recommend that you try these files out if you are using Adobe Captivate 5.5. You can download the files from GitHub by following this link: https://github.com/pipwerks/Captivate-Publishing-Templates-Redux
Philip also wrote a series of posts explaining exactly what he has done step-by-step and they are a very interesting read if you would like to know more about how the Adobe Captivate SCORM reporting actually works. The first post in the series can be found here: http://pipwerks.com/2012/01/11/cleaning-up-adobe-captivates-scorm-publishing-template-part-1-introduction/
Thank you Philip for this great work!
/Michael
