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

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.

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. 

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!

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.

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. 

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?

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

Thanks Franz for sharing that link here - and I'm glad that'll work for you. 

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 Bart,

I saw your reply, so I thought I'd pop in to share our current workaround for courses that need to complete on a specific slide, but don't have a scored assessment. It's pretty basic, but has worked well for us in both Flash and HTML5 in recent months.

Here are the steps to how we use a "dummy" results slide for LMS completion.

1. Create a blank results slide and keep it separate from your content slides. This is your dummy results slide and will never be seen by the users.
2. Set the passing score to 0% in the Results Slide properties, and don't check any of your quiz activities.
3. Then add a Submit Results trigger on the final slide of your course, or wherever you would like to send LMS completion.
4. When publishing, track using the result slide.

In our experience, this will always track your Completed/Passed status when the user reaches the submit results trigger. The only issue is that it may send a meaningless 0% score to the LMS too.

I would still much rather use JavaScript to send completion and scoring information as we could in Storyline 2, but this workaround has done the trick for most of our Storyline 360 projects.

Hope it helps!