Hello everyone, I'm in the process of upgrading some courses to Storyline 360 to utilize the HTML5 improvements. Due to the complexity of certain courses, we've found that the best method of setting course completion on LMS has been using JavaScript via SetStatus("completed"); However, it seems that SetStatus("completed"); is not working for my SCORM 1.2 courses on SCORM Cloud when using HTML5 output. The completion status remains incomplete after the JavaScript trigger has been executed. I tried it again using the Flash output and it worked correctly. Once the trigger was executed, the course was properly marked as completed. In my past experience, SetStatus worked well for both Flash and HTML5 with Storyline 2, so this seems to be specific to Storyline 360. Does anyone have more information on this issue, and perhaps a workaround to get it working correctly for HTML5? Thanks,Matt

Hi Samantha, Thanks so much for sharing your solution! I tried it out, and it wasn't working for me initially in Storyline 360. However, it got me to dig a little deeper and it seems to be working well using the lmsAPI methods instead of the Storyline player. Here's the version that worked for me with an optional line for tracking score: //Get LMS APIfunction findLMSAPI(win) {if (win.hasOwnProperty("GetStudentID")) return win;else if (win.parent == win) return null;else return findLMSAPI(win.parent);}var lmsAPI = findLMSAPI(this);//Set Completed statuslmsAPI.SetReachedEnd();//Set Passed statuslmsAPI.SetPassed();//Set percentile score based on score variable between 0 - 100lmsAPI.SetScore(score, 100, 0); Credit for grabbing the right window with the lmsAPI goes to Adam Trosper's posts on this thread. So far this seems to be working for me in Storyline 360 in both Flash and HTML5 outputs. Thanks,Matt

Leslie, Thank you very much for your quick reply. Please give me an update when it's available.

This is also an issue for us as, like everyone else, we are migrating our courses to HTML5. We are using SL3 not 360. Again, the issue is not with the java script per se, but with the javascript under HTML5. To test this, you need to generate the module in HTML mode only, no flash fall back, and then test it in a browser with flash disabled. I've attached a test module that uses various attempts at setting the module to complete : lmsAPI.SCORM_SetCompleted(); SetStatus("completed"); lmsAPI.SCORM_SetPassed(); lmsAPI.SetReachedEnd(); And I have also used both methods for connecting the LMS : var lmsAPI = parent var lmsApi=[object Window] None of these options work under HTML5. Articulate, this is a real issue as almost all of our modules use this way of determining completion since counting slides is too simplistic, and not all modules have quizzes. This has been talked about in the forum for several years now. It's pretty inexcusable that there is not a solution.

Hi Matt, Thanks for reaching out here! It's been logged as a possible software bug. From here, I’ll meet with my team to take a closer look so we can determine next steps.Depending on priority and risk, some bugs can be fixed quickly, while others take longer to resolve. Here's more information on how we identify and tackle bugs: https://articulate.com/support/article/How-We-Tackle-Bugs I’ll let you know as soon as we have an update on this issue. Thanks so much again for letting us know about this, and I’m sorry if it’s slowing you down.

Hi Ashley, It took me a while to find this post, I was trying to figure out why SetStatus was not working for me. Is there an update on this issue? Thanks

SetStatus not working for SCORM 1.2 completion - Storyline 360 HTML5 Output

EmileeBlair
Community Member
8 years ago
Hi Crystal,

We were previously using this on Adobe Captivate Prime (with Storyline 2) and it was working great. We then moved to a new LMS, SuccessFactors, around the same time we started using Storyline 360 and now the JavaScript method is no longer working. The learners are still marked as incomplete after they reach the slide with the JavaScript trigger.

We were testing it on Articulate Online to see if it was an issue with the LMS or the actual module, since we are still getting used to using SuccessFactors.

The module that I am working with has 73 slides, but there are 4 different branches the learner can choose to go down. As a work around, we are having the module be marked complete when they complete 25 out of the 73 slides, which would be the shortest route. This isn't ideal and will work for this particular module, however, we will need JavaScript (or similar feature, suggestions?) for future modules.

Thank you!

Emilee
AshleyT-Pollard
Staff
8 years ago
Thanks Emilee - and we'll keep you posted about any changes with the functionality and behavior for Articulate 360!
MikeClark-6ca01
Community Member
8 years ago
Any update?

I know that "Automatically Decide" for slide revisit can mess with LMS communication, has anyone tested "Reset to Initial" and tested SetStatus? We use this a lot for our branching modules.
AshleyT-Pollard
Staff
8 years ago
Hi Mike,

No update on our side - the issue with the JS Code is that it was relying on undisclosed variables in Storyline 2 (a bit of a hack into the published output). As a part of our move to Articulate 360 and knowing that folks need HTML5 first we rewrote the entire publishing engine. That's what's causing the "break".

Our team is looking at what variables and elements folks were using, and how can we build that feature back into Storyline. That'll help as then you won't have to create these hacks!

We'll let folks know when those things are ready, and if you have other ideas of things that you'd like to see included don't hesitate to let us know! We do get lots of requests and ideas here in the forums and also through our feature request form.
MartinSanterre-
Community Member
8 years ago
Hi, we are having the very same problem. We are migrating many courses to HTML5. Thanks to let us know when this issue is solved!
FranzMueller
Community Member
8 years ago
Hello,

is it possible to migrate Storyline360 projects to Storyline2? We have upgraded to Storyline360 during the implementation of a big course and now this feature is no longer working. It is absolutely necessary for this customer.
AlyssaGomez
Staff
8 years ago
Hi Franz! You can open Storyline 2 files with Storyline 360, but not the other way around. Since Storyline 360 contains so many new features and upgrades, it's not backwards compatible with Storyline 2.

If you opened a Storyline 2 file with Storyline 360, a backup version of the Storyline 2 file should be available if you need to open the file with Storyline 2 in the future.
FranzMueller
Community Member
8 years ago
Hi Alyssa, thanks for your reply, but I have already finished too many slides in Storyline 360.

Russell's solution works with SCORM 1.2 in the SCORM Cloud, but it does not work with SCORM 2004. Does anyone has any idea how the completion status could be called in SCORM 2004?
FranzMueller
Community Member
8 years ago
I found a workaround posted by Zsolt Olah, that works with SCORM 2004: https://community.articulate.com/discussions/articulate-storyline/setting-scorm-status-in-articulate-storyline-360#reply-471393
AshleyT-Pollard
Staff
8 years ago
Thanks Franz for sharing that link here - and I'm glad that'll work for you.