We received reports on Friday that learners the modules they were taking weren't reporting as complete to our LMS. At this time, it is my best guess that it is a browser issue. I wanted to ask if anyone else is running into this issue. I will continue my research and update this tread with what I find out. I can replicate this issue and my current set up is...
Hello, fellow Richmonder. Sorry you and your learners are hitting this snag!
Have you tried testing in another LMS environment like SCORM Cloud (an industry-standard LMS testing tool) to see if you can replicate the completion issue there? The outcome will tell us if the problem lies within your Storyline or LMS' output.
Hope you get community feedback from other Cornerstone users, and we're here if you need a hand with testing!
Yes I have. It worked in SCORM Cloud using Chrome. I ran the debug scripts and nothing looked out of place. I was able to determine that it must be something with the interaction between Chrome v73 and Cornerstone for Salesforce. For now we are recommending that our learners use IE to complete their training.
I too am seeing this when using the 'Course Complete' trigger with 360 on this latest version of Chrome. The slide count trigger and quiz results trigger appear to function correctly. It's great that Charles' LMS provider is working on a fix. Can we assume an update is coming from Articulate as well to address this?
As of 4/17 we were told the fix was to put Exit buttons on all of our course modules. This does work, however we have 100+ modules and that is going to take for ever.
Great news. We just tested the latest patch deployed by the CFS team and it works! We will not have to update every course module with an Exit button as feared.
Around the same time Charles was seeing the problem, we began seeing a handful of employees making the same type of report. The employee completes the course, but the EXIT button doesn't work (we were already using EXIT buttons), and the user doesn't receive completion credit in Cornerstone. The course also didn't bookmark: when the user relaunched, the course started at the beginning with no option to resume.
Not all users were affected. But it did seem to happen in both IE and Chrome.
Recently, the issue cropped up for about 30 percent of users for another module (published and launched a couple months ago).
We use Cornerstone On Demand (CSOD). I've requested information about whether the patch used for CFS has been applied to CSOD. Will return with an update.
Hi, does anyone have an update on this? I think we're experiencing a similar issue. Ever since the latest Chrome update, our Storyline 360 and Rise courses are not registering as complete on our LMS.
We have a workaround that's a bit messy. If the trainee keeps the course window open and then goes back to the LMS page and tried to launch the course again, it will now complete.
I've sent MANY emails to our LMS provider (Net Dimensions) who have responded for 2 months that they are "looking into it".
It's driving me crazy and I'm now holding up training courses until there's a fix. Any ideas???
10 Replies
Hello, fellow Richmonder. Sorry you and your learners are hitting this snag!
Have you tried testing in another LMS environment like SCORM Cloud (an industry-standard LMS testing tool) to see if you can replicate the completion issue there? The outcome will tell us if the problem lies within your Storyline or LMS' output.
Hope you get community feedback from other Cornerstone users, and we're here if you need a hand with testing!
Hi Katie,
Yes I have. It worked in SCORM Cloud using Chrome. I ran the debug scripts and nothing looked out of place. I was able to determine that it must be something with the interaction between Chrome v73 and Cornerstone for Salesforce. For now we are recommending that our learners use IE to complete their training.
Thanks for checking in with me.
Best,
Charles
Appreciate you keeping us in the know, Charles. If there's anything we can help with, don't hesitate to give us a shout!
I too am seeing this when using the 'Course Complete' trigger with 360 on this latest version of Chrome. The slide count trigger and quiz results trigger appear to function correctly. It's great that Charles' LMS provider is working on a fix. Can we assume an update is coming from Articulate as well to address this?
As of 4/17 we were told the fix was to put Exit buttons on all of our course modules. This does work, however we have 100+ modules and that is going to take for ever.
Great news. We just tested the latest patch deployed by the CFS team and it works! We will not have to update every course module with an Exit button as feared.
I appreciate you keeping us up to date, Charles :)
Around the same time Charles was seeing the problem, we began seeing a handful of employees making the same type of report. The employee completes the course, but the EXIT button doesn't work (we were already using EXIT buttons), and the user doesn't receive completion credit in Cornerstone. The course also didn't bookmark: when the user relaunched, the course started at the beginning with no option to resume.
Not all users were affected. But it did seem to happen in both IE and Chrome.
Recently, the issue cropped up for about 30 percent of users for another module (published and launched a couple months ago).
We use Cornerstone On Demand (CSOD). I've requested information about whether the patch used for CFS has been applied to CSOD. Will return with an update.
Hi, does anyone have an update on this? I think we're experiencing a similar issue. Ever since the latest Chrome update, our Storyline 360 and Rise courses are not registering as complete on our LMS.
We have a workaround that's a bit messy. If the trainee keeps the course window open and then goes back to the LMS page and tried to launch the course again, it will now complete.
I've sent MANY emails to our LMS provider (Net Dimensions) who have responded for 2 months that they are "looking into it".
It's driving me crazy and I'm now holding up training courses until there's a fix. Any ideas???
This discussion is closed. You can start a new discussion or contact Articulate Support.