';Completed'; Versus ';Passed';
June 2, 2020 12:00 AM
I should probably know this, but I think the months of working from home is finally getting to me!
I have a simple course where at the end there are two actions:
- On Show, Modify Variable, AICC Score Set Equal To 100
- On Show, Modify Variable, AICC Lesson Status Set Equal to Completed
Completed. Set equal to COMPLETED.
When clicking the X (button) in the course to exit, it shows Completed in the LMS (Saba).
When clicking the X in the upper right corner (Chrome), it shows Passed in the LMS.
Why? And how can I fix it so that no matter how a learner exits they get Completed? Do I need to remove the AICC Score variable since all I want is Completed?
I need a drink...
Discussion (2)
It's not your fault, and you're not going crazy. Your LMS didn't update for Chrome 80. Here's the notice we got from our (now former) LMS, CSOD, back in December.
Google will release Chrome 80 on February 4, 2020. With this release, Google is making significant changes to Chrome’s Window Close behavior that will impact how online courses communicate a user’s exit and completion status to our learning platform. NOTE: There is no impact to other browsers, i.e. Firefox, Safari etc.
The impact on you
Online courses use a browser’s Window Close behavior to communicate a user’s progress and completion. With the February 4 updates, Chrome is changing this behavior which will change how this information needs to be sent to our system.
What we’re doing to help
In response to these changes, Cornerstone is updating our SCORM player to ensure that SCORM courses continue to communicate user status correctly to our system. Since AICC and xAPI courses are not hosted with Cornerstone, these providers must update their courseware to ensure that user status is updated correctly. We are also advising all Cornerstone partners to review their courseware and make the updates Google recommends.
We are also working directly with our content providers to ensure there is no impact to content that is part of these subscriptions. Though we are working directly with our providers, it is up to them to make the fix on their end so there may be issues with Chrome playback until all providers have been able to make the necessary changes.
Next Steps (recommended)
• Clients with AICC and xAPI content should reach out to their content providers to discuss how they are preparing for this change.
• If possible, delay upgrading to Chrome 80 until you have confirmed that all third-party content providers are ready.
Discussions have been disabled for this post