Issues with JavaScript in Storyline 360

Have you checked the developer console for errors? Are you calling functions that may have changed in storyline or are they functions you have written?

Hi Chris,

What type of Javascript functions were you using? Since Storyline 3 (and Storyline 360) involved a rewrite of our HTML5 output and publishing engine, some of the custom/community workarounds to access player variables will no longer work. 

If there is a specific variable or function you're looking for, we'd love hear more about what you would like to see regarding this if you're up for logging a feature request.

In the meantime, you can also find our best practices on using Javascript with Storyline 3 here. 

If you post an example, we can take a look.

One thing I've run into when moving from SL 2 to SL 3 is that for some reason the user.js file that used to be loaded at the bottom of the index.html is now loading earlier. What that means sometimes is the if you use a GetPlayer() function in your JavaScript, the player is not ready yet. This breaks everything else after in JS.

Again, without seeing the error you're getting (turn on the developer window), it's hard to tell.

Hey Guys, 

Thanks for your responses, and apologies that it has taken a short while to respond.

After having a look, I suspect this is likely a similar problem that Adam Trosper reported in the thread linked above. 

I'm embarrassed to admit that I'm not entirely sure how to implement the solutions mentioned in the aforementioned thread, into our JavaScript (I'm not really a developer, so much of this stuff goes waaay over my head).

Attached is a Storyline (3) file which has all of our troublesome JavaScript compiled onto a single slide. 

I've included a brief description of what each snippet of JS is supposed to do in the file. - Any assistance in getting this stuff SL3-ready is extremely appreciated! :)

Thanks Guys (and Gals!)

Hi Chris,

The layer that has the date function is working (as long as what you're trying to do is create a date string like 2019123 and then make a number out of this 2019123 and store it in the DateValue variable. It's not running now because the condition of DateExpire or whatever variable is false. If you turn it to, it works.

As far as the lsm goes, I'm not sure what this is, I've never seen SCORM_objAPI or methods/functions like csSetValue. 

lmsAPI.SCORM_objAPI.csSetValue(param1,varInput)