Adobe Captivate Classic - Publishing Issues

I am finding the same thing on my end. My project consists of one slide that has a 22 minute MP4 video added to it. Even though my project doesn't contain a quiz, I need to enable quiz reporting and ensure the completion and success options are set to slide views, not quiz/quiz is passed. If I don't do this and publish as SCORM, it appears CpC successfully SCORMs my project, but it fails when importing to my LMS (Saba). According to ChatGPT, this is because when quiz reporting is disabled, CpC will still zip and export the project, but it's not a "true" SCORM file. It's a zipped package that looks SCORM-like. Because of this, Saba is rejecting the package because it's looking for a imsmanifest.xml (or something similar?) file that a true SCORM-ed package should contain. I'm not sure if this is accurate, but it did solve my issue. I still don't quite get it - but I guess if you don't set the preferences up this way (using the slide views as completion criteria) when the learner finishes the training, the LMS has no way to know to mark it complete?

Some LMSs allow to upload a 'package' which has Reporting not turned on, but that is not the case for all LMSs. Blackboard which I have uaed a lot, allows it: you need to iinstruct to unzip the package and to launch the index.html file.

You can publish to play the interactive without reporting or to SCORM which would be with reporting.

If you do not need to report the outcome of the interactictive activity, you can publish to the course files. Do be aware of some potential issues that you can prepare for. In Canvas with Design Tools as an extra package it includes tools to clean up the course of files that are not used. This tool Does not understand files related to displaying a webpage and will flag them as unused with a recommendation to remove them. Inform any personnel that is responsible for using this tool that they must proceed carefully with any file removal using this tool. Other LMSs may have a similar tool, so consider if this warning may apply to you. To make the interactive play, you will have to explore how your LMS will handle it. In the Current version of Canvas, you can link to it and it will open in a new window at a nice size. Alternatively, you can embed it, but it is a challenge to prevent Canvas from adding its sidebar in there with it making the interactive small. 

The other option is to publish your project as a SCORM file and upload it to your LMS as such. Not all LMSs will have a SCORM option, but most do. A SCORM file has the needed tools to communicate with the LMS what score the student got. This does reqquire setting some settings in Captivate before you publish. Look for instructions within the Captivate website and videos (there is a Captivae channel).

Setting Tip:

Something really easy to miss is the manifest configure button when you select to use SCORM output in Captivate. All the other settings are visible without having to click to open a new window and those just draw your eyes right no down to the form without you noticing this button. Be sure to give your project a name in the configure dialogue. Captivate intends for that to be the name of your project and in the past this would auto-populate with it. However, more recent updates seem to have broken this and it fills with the same default for all projects. Cornerstone has a nice support page. that describes the settings. Read on to get more of an idea about this issue and a way to fix this even if all you have are the published SCORM files and not the raw file.

Tip: When my SCORM packages come in to my courses they always show a default name instead of the name of my project. This can be a problem if you have several and you need to know what SCORM project these each are. I go into the published manifest file and make an edit to change the name. Then it comes in correctly to Canvas. I am not 100% certain if this is a Canvas issue or a Captivate issue, but since when I change the manifest file that Captivate uses away from that default name it does fine, I would say the blame leans to Captivate in creating the conditions for this problem. Possibly this is only a Mac version of Captivate issue or even specific to a particular release.

Cause:

Captivate is not pushing the name of the project to the manifest and the files for the project name.

Solution:

You can manually change this by 

• Unzip the published SCORM
• Open up VS Code (or any other code editor) and use find to locate the two files with "Captivate e-Learning Course"
• Change both locations to the correct file name (do not use special characters)
• (OPTIONAL - NO LONGER NEEDED) Remove the assets/playbar folder (prevents zip issues)
• (OPTIONAL - NO LONGER NEEDED) Remove assets/playbar from the manifest
• Rezip
• Upload to the SCORM tool in the Canvas course