Issues with Scorm when using Google Chrome come January 2020

Just to check, I thought Scorm was okay if you have an exit button and the staff use it.  But if you have students accessing one published say inside of Moodle and they finish and close the browser it may be the issue...My apologies I do design but I don't really understand the publish/back end of things...

Hi Teresa!

We've been working closely with Rustici on this issue since the moment we heard about it.

The problem primarily impacts SCORM Engine, which is a product used by LMS vendors. Articulate also partners with Rustici on their SCORM Driver product, but this tool isn't as impacted. The exception is AICC content, and we'll be working on a fix for AICC soon. We're very confident that content published from Articulate authoring tools for SCORM and xAPI is not impacted, so we've got you covered!

Thanks Lauren, that is good news.  Can you remind me when AICC is used?  I also have a student external page of links to web published elearnings as they are no in our LMS.  They finish the elearning and print the certificate and close the browser....and we may be moving all of these to Moodle.  If in Moodle I assume we still want an exit button or a complete button to finish the scorm package and Moodle will record it, not sure if you are familiar with that.  Try to ensure I am ahead of the game as I am a self taught designer - (you know once a facilitator and then told we now need elearning so please learn lol!  but I enjoy it) so I don't always understand the technical background information.

Hi Teresa!

This webpage explains the difference between AICC and SCORM really well, and better than I could explain it too!

Yes, you'll still want an exit or complete button. I would check with Moodle support to learn more if it's affecting your courses there.

Thanks Lauren I will take a look at the article.

Can you provide an update on when the fix will be released in Articulate 360 publishing tools to address the issue  and if an updater utility will be provided to resolve issue in existing AICC courseware?

Hi Sharon!

This is a topic that our team is still investigating. If I hear of an update on the timeline, I'll relay the information in this discussion!

Following...we use SABA.

Happy Tuesday, all!

I'm excited to share that we just released Update 35 for Storyline 360. What's inside: We added support for Google Chrome 80, which no longer allows synchronous XHR when a web page is closed. This update ensures your AICC courses always communicate a final status to an LMS.

To see all the enhancements this version has to offer, follow these steps to update your software! 🎁

The information we received from our LMS vendor, Saba, was that SCORM 1.2 courses could be afftected by the Chrome 80 update if a course did not have an exit trigger or if a course did not have a quiz score that was passed to the LMS. Most of our courses are based on number of slides viewed andf there isn't a exit/finish button; the learner closes the browser to end the course. Am I to understand the Chrome update should not be a problem afterall if we are publishing to SCORM 1.2? 

I appreciate your help!  

Hi Carla,

Thank you for reaching out! As Leslie and Lauren mentioned, SCORM and Tin Can API (xAPI) courses are unaffected by Chrome's browser change. 

The potential issue discovered was for AICC courses. With the news that Katie shared, the latest update to Storyline added support for Google Chrome 80 and AICC courses. This update ensures that AICC courses always communicate a final status to an LMS.

Please let us know if you have any questions! We are happy to help! 

Thank you for the fix! Would this mean that anything on my LMS developed prior to 35 will face the completion issue? Thank you! 

Hi Emily,

Potentially if you've published to AICC format.

As we are using Tin Can API, in theory we should be OK. But should we encounter problems, once we get the software fix mentioned above, we would have to re-publish all of our content using the latest version of Storyline to get the fix? We use Valamis and they are providing site fixes for some content, but not for packages, so I am just trying think out the worst case scenario. Katie says we should update our version of Storyline, but that is only the first step, right? This would only help new development, not existing content, or am I missing something? Thanks.

Hi Rory,

That's correct! The fix in the latest update will support newly published courses, not courses that have been published beforehand. As you mentioned though, you are using Tin Can API, so you shouldn't be affected as this issue is related to courses published with AICC.

If you do run into issues and feel it may be related, you can always connect with one of our support engineers to give you a helping hand in confirming any errors!

Thank you! Yes, it was the obvious answer, but Katie's answer made it sound a little too easy! I just have to prepare my boss - just in case! Every time I say that I have to republish all of our Storyline files across multiple sites, our production schedule takes a hit. Thanks again Chrome! But at least the solution is 'simple' and does not require any new coding, etc. Thanks for that!

Another happy Tuesday, all!

For folks using Storyline 3: We just released Update 9 that offers support for the Google Chrome 80 and synchronous XHR scenario. This update ensures your AICC courses always communicate a final status to your LMS.

Here's how to update Storyline 3 to the latest version!

Does this affect Rise?

Also, will there be some kind of tool that will become available soon that can scan all of the courses made with Articulate software and "patch" the older made courses so we don't have to worry about opening up the previous made courses individually and republish?

I recall, in the past, a similar tool was pushed out by Articulate due to a previous Chrome update.

Hi there, Adam. Happy to help!

Our team is working to ensure that Rise 360/AICC courses are also fully compatible with Chrome 80.

We don't have a timeline for the next Articulate Updater yet, but I'll share your thoughts with the right team and update you on any new information around both inquiries!

Thank you so much!

Hi Katie,

We have 100's of modules that was published using previous version of Storyline 3. Considering the timeline for Chrome 80 release. Just checking to see if you have received any response from the team regarding an estimated timeline/date on when the Articulate Updater will be released for Storyline 3 to update the modules that are published using earlier version of Articulate Storyline 3.

Thanks in advance.

Hello, Karthik!

Thanks for checking in. I hear you that managing 100s of courses is a lot when being impacted by a browser change, and updated our team on its continuing impact.

We promise to keep this discussion updated on any new developments!

Thanks Katie, is it ok to assume that Articulate team is working on an releasing an Articulate Storyline updater for Chrome 80. However, the team don't have a target release date yet?