Captivate 8 assessment will not pass failure to LMS

Signaler · Feb 16, 2015

I have a simple 10 question Captivate assessment; if passed, it will update the LMS to Pass; if failed, the LMS continues to show status of in progress and does not flip to failed. Any ideas?

Signaler · Feb 16, 2015

Do you have a result slide? What is it telling? Make sure it is not the last slide, add an extra slide. For the rest: it depends also on the LMS. Try testing your published project on SCORM Cloud, if it is working correctly there, you have to talk with the LMS manufacturer.

Signaler · Feb 16, 2015

Yes, there is a result slide; there is a continue button on that slide followed by another slide before they exit the course; I have never used the SCORM cloud; is there a cost associated with that? Our LMS is Mzinga.

Thanks for the response.

Signaler · Feb 16, 2015

No, you can have a limited number of free tests. Have a look: Scorm Cloud Testing Content with SCORM Cloud » SCORM -

Signaler · Feb 17, 2015

So unfortunately, I received this reply from our support staff...

"In this case, the LMS does not see a Fail Status as a Terminal Status within their rules. Thus the course remains on the To-Do list until either the learner is able to complete the content or the LMS Administrator removes the content from their To-Do list by changing the user's status to Fail. I know this doesn't make any sense, but unfortunately that's the workflow that our LMS vendor has decided is the appropriate route. Also,

the LMS doesn't recognize the Pass/Fail or Complete/Incomplete status as one which will reflect that the learner has not successfully passed the requirements within the course. Ultimately Mzinga does not follow normal logic and implement a "Pass-Fail" or "Completed-Incomplete" status to reflect these instances where SCORM rules would apply."

Signaler · Feb 17, 2015

What version of SCORM are you using?

Signaler · Feb 17, 2015

SCORM 1.2

Signaler · Feb 17, 2015

Have you tried SCORM 2004. Seems this is NOT a compliant LMS. Read some of these issues.

http://community.omnisocial.mzinga.com/exp/Customer_Experience_Community10000/blog/Solution_Center/l...

Signaler · Jul 18, 2016

I'm having a similar issue and would like to know if anyone else has found a solution.

We're publishing in Captivate 9.0.1.320. Our LMS is provided by SAP, and we are publishing to SCORM 1.2. Before anyone asks, no, we're not going to SCORM 2004. Our LMS is scheduled for an update in 2-3 quarters that will incorporate Experience API (XAPI), a.k.a Tin Can, so they LMS administrators are not going to change anything right now with respect to SCORM standards.

The behavior we're noticing in our LMS is:

The Pass Scenario

If a learner has a passing score on the quiz in a course, then exits the course, the Captivate content appears to have no problem with handing off a status of "Passed" and the passing quiz score to the LMS. No issue here.

The Fail or Quit Scenario

If a learner has a failing score on the quiz in a course, then exits the course, then the LMS does not seem to be able to record the current status at all, and takes the learner back to an enrollment page instead of showing a status of "Failed" or the quiz score. This is a page in the LMS where the learner clicks on a button to book and launch the course.

We're trying to document this thoroughly enough to convince the LMS vendor to investigate from their end of things.

We Created a Test Course

To that end, we created a test course in Captivate with a short quiz in it. We published that to SCORM 1.2, and loaded the same set of files into both our LMS and to SCORM Cloud. In SCORM Cloud the Captivate content appears to work normally in both scenarios. That is, when you fail the quiz and exit the course then SCORM Cloud shows that you have a "Failed" status, and shows the failing quiz score. It also works normally in the Pass Scenario. In our LMS it does not work. It behaves as described above.

So we have Captivate working fine in SCORM Cloud, but not working fine on our SAP LMS. It must be something with the LMS, correct? Here's the problem, the LMS has no problem in either scenario with courses that are published in another authoring tool, namely Trivantis Lectora. So then maybe there is something special about Captivate's output that prevents the LMS from recognizing its SCORM data in the Fail Scenario?

If we can't get this resolved then our LMS team is going to ixnay any courses published in Captivate, and tell us that we can only publish courses in the other authoring tool.

So if anyone has seen this issue before, can tell me where to look to resolve the issue, or can give me some information that allows me to speak intelligently with our LMS administrators and vendor, then I'd really appreciate it. I don't want to have to publish all of our content in that other authoring tool.

Signaler · Aug 12, 2016

We are in the same exact boat as you. I have tried 15 different test courses with our LMS (it is Peopelsoft) and identical results in regards to Passing scenarios vs Failed scenarios. Did you hear any response outside this thread?

We too may have to give up Captivate in order for us to publish successfully.

Signaler · Aug 18, 2016

I'll provide a partial update, but the issue is not fully resolved.

We presented our findings to the team that manages our LMS, showing them that Captivate works fine on SCORM Cloud, and they agreed to look more deeply into the matter. It turns out that the servers on which our LMS is hosted underwent an upgrade (Unix to Linux), and our LMS software underwent an update relatively recently to accommodate that.

The team were able to find another, test environment server that had not been involved in these updates, and was still running an older version of the LMS. They tested our Captivate output on that server and found that it worked normally there. That tells us that the issue we're seeing is:

A problem with the LMS coding, not with Captivate's output.
A problem with the updated LMS coding, not with the older version of it.

It is now out of their domain, as well as outside the domain of the LMS management team, as well as outside the domain of our instructional designers and local Captivate experts. It has been handed off to the developers, and that probably is also going back to SAP, the vendor that provides our LMS.

So it keeps going deeper and deeper, and the pace glacial. We have courses that were developed in Captivate, and for which the "fail scenario" must work correctly, and these courses are backing up, and driving us all crazy.

But the short of it is that it's something going on with the LMS, its coding, and how it handles the SCORM information in the fail scenario. Since that's the case, it seems as if our LMS is not so SCORM-compliant as we thought. It's not Captivate's output at all.

I'm hoping it does get resolved. The thing I'm afraid of is the developers coming back and saying "we can't figure it out, just use your other authoring tool instead." If they do resolve it, I'll try to get some indication of what they found and post that here, although I doubt it will be a detailed description.

Signaler · Aug 18, 2016

Thanks for the reply and details. It really sounds like we are in same situation. The other thing I tried was uploading my test course to scormcloud.com and it tested perfectly. I reported back to my LMS team so waiting to hear what they say. I will keep this thread in mind when I learn more.

Signaler · Sep 19, 2016

I wanted to update this posting to document that we did get a solution to this, after lots of testing and escalating, until we finally got a developer who made a change, and now it is working.

The Short Version

Something needed to be changed in the LMS, nothing needed to be changed in Captivate or in our publish settings. Now that the change is applied, the course reports the fail scenario correctly.

The More Detailed Version

I mentioned above that the LMS we are using is SAP. I don't load the courses into SAP myself, we have a team of people with SAP accounts who do that, and we hand off published files to them for posting to the LMS. Those administrators need to make a change in the process, and what follows means nothing to me, frankly, but it may to someone else who has this issue.

From our LMS administrators:

The solution is a re-configuration of the IT5008 transaction in SAP.

There is a field that references Completion Specifications/Follow-up Options.

The Fix is to set the "Include Completed Learning Objects as Success Criterion" to zero and leave it unchecked.

The current Default setting is to have "Include Completed Learning Objects as Success Criterion" checked and set to 100%.

Signaler · Sep 19, 2016

Surprise, surprise. The problem yet again turns out to be something that needed to change on the LMS instead of in the Captivate output. I'd love a dollar for every time I've seen or heard this. I could retire on it.

Signaler · Sep 22, 2016

Yes, and the real challenge was convincing the LMS administrators and developers of that fact. Their first three reactions to the situation were (in order):

You published it wrong.
Something's wrong with Captivate.
Why don't you use this other authoring tool that nobody has a problem with?

It took lots of careful testing and documentation to get them to take a look at their own systems.