Forum Discussion
SetStatus not working for SCORM 1.2 completion - Storyline 360 HTML5 Output
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
- MattLeo-3da086aCommunity Member
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.
- 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.
- Set the passing score to 0% in the Results Slide properties, and don't check any of your quiz activities.
- Then add a Submit Results trigger on the final slide of your course, or wherever you would like to send LMS completion.
- 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!
- BartSchutteCommunity Member
Thanks Matt. I'll try this out.
- AdamMenary-0aecCommunity Member
this worked for us in Storyline 3 brilliant thanks
- MartinSanterre-Community Member
Hi Matt,
I would add ourselves to your solution.
We used the very same method to fix the problem and it worked.It still complexifies the production worklow and takes extra time to find and test the fix then apply it.
As Bart says, the problem is known since a long time and it's hard to understand why there is no solution yet.
- GeordieOxleyCommunity Member
This is really disappointing, I'm having the same issues.
The default completion options in Storyline are poor.
Until this is fixed, I'll be building new courses sin SL2. How hard is it for the devs to put in some functions we can call?
- SamanthaGrevasCommunity Member
This works for me:
var player = GetPlayer();
player.SetReachedEnd(); //for complete
player.SetPassed(); //for passedThoughts Ashley?
Hi Samantha,
I'm not much of a Javascript expert...so it's a bit of a stab in the dark for me!
Are you using Storyline 3 or 360? That's where the Javascript was reported as not working for the player variables, but if it does work for you there...magic, perhaps? 😉
If you're using Storyline 2, that Javascript should still work!
- SamanthaGrevasCommunity Member
Hi Ashley! I am using Storyline 3. The method that worked in Storyline 2 no longer works in 3:
SetStatus("completed");
The workaround is to call the methods in the SCORM API directly:
var player = GetPlayer();
player.SetReachedEnd(); //for complete
player.SetPassed(); //for passedBest,
Sam Hi Sam,
Ah, thanks for clarifying! Those system variables changed a bit in storyline 3/360 based on changes we made to our publishing engine and player for HTML5.
As such, those same Javascript codes no longer work. They were not officially supported in Storyline 2, but folks had found them through a bit of "hacking" the published output and devised some of these methods for custom set up.
We're looking at other ways to put these methods back into Storyline 3/360 or create new features that would accomplish the same set up. We'll let folks know here in the community if there are any updates on that!
Thanks for sharing Matt!
- FunctioneelBeheCommunity Member
It looks like we're facing the same status completion issues with Scorm 2004 (which we are still using, because we have bad experience with Scorm 1.2). Can anyone confirm this?
Hi Functioneel,
Are you trying to use the same code as mentioned above? Or are you using the standard SCORM outputs with completion based on a quiz results or slides viewed?
If it's issues with the code earlier in this discussion, I'd have to leave that in the hands of the community.
If you're having issues with the built in completion tracking - can you let us know what version of Storyline you're using and where you're hosting your content? To start troubleshooting I'd suggest testing the course at SCORM Cloud to see if it behaves differently there than you LMS.