SCORM 1.2 Marked Completed When Actually Incomplete

  • 1
  • Problem
  • Updated 1 month ago
  • (Edited)
Hello,

We are running Camtasia 2019.0.8 and publishing out SCORM 1.2 packages that work with Rustici Engine 2019. We are expecting participants to watch 100% of the video before completion and credit is granted. We've observed that the completion status is set to UNKNOWN initially or while the video is launching. And if the user ends up watching ~2% of the video, the completion status gets updated to INCOMPLETE and seems to stay that way until they watch the entire video. The issue we are observing is if the user closes out the video before hitting that 2% mark, there are two completion status updates pushed. The first is COMPLETED and the second is INCOMPLETE. Our application responds to any completion status of COMPLETE or COMPLETED and gives the user credit for the video. Why would Camtasia be reporting a COMPLETED completion status for that first message when it really is meant to be INCOMPLETE?

Thanks!
Photo of naf12

naf12

  • 2 Posts
  • 1 Reply Like

Posted 2 months ago

  • 1
Photo of Ben Rhodes

Ben Rhodes, Employee

  • 329 Posts
  • 132 Reply Likes
@naf12,

I've tried to reproduce what you described using Camtasia 2019 with SCORM Cloud.  The video does send the unknown status when video is first launched.  But closing the video before reaching 2% of the video only sends incomplete as a status.  I'm looking at the call logs and the player is not sending a complete status until the user has watched the entire video (which is what I've set as a requirement for my test video).

Are there any additional steps you could provide to help reproduce what you are seeing?

Thanks,
Ben
Photo of naf12

naf12

  • 2 Posts
  • 1 Reply Like
Hi Ben,

I actually opened a ticket (Request #661600) and worked through it there and with Rustici.

After working with Rustici, we did find a solution that didn't require a change to the Camtasia SCORM package. The issue we were experiencing is due to a non-communicative SCORM package and how Rustici Engine handles that. The solution was to update a system setting. By setting PlayerForceObjectiveCompletionSetByContent to true (default false), Engine would report incomplete for non-communicative SCORM packages.

This can be considered resolved.

Thanks for your help!