Adding Custom Parameters to a launch link [ Storyline 3 ]

Jul 19, 2018

Howdy, we used to be able to add custom parameters to the launch link for Storyline 1 and Storyline 2. Looks like this breaks the Storyline 3 though. 

Articulate says :

You can also add custom parameters to the launch link’s query string. Any additional parameters will be echoed back when the content reports statements to the LMS.

Oh whaaaaa? No way, if I append this to the end of my launch link :

&quiz_id=123

This will cause Storyline 3 to not launch at all ..

Oh but there's more! If I do this..

&quiz_id=12

Works just fine! In fact any two digit number is OK. If I put anything past 3 digits though, the whole of Articulate Storyline will not work.

Here's the part where I lose my mind.. if you add 7 digits ( I tested to 13 digits and it works fine )!, it works again..

&quiz_id=1234567

< mind_blown.gif >

Oh and ALL OTHER NAMES FOR CUSTOM PARAMS WORK. Just the word "quiz_id" breaks if there is only 3 - 6 digits.

And yes, I tested this in SCORM. Doesn't work there either.

 

 

 

4 Replies
Crystal Horn

Hi there, Trip.  It sounds like you're following this protocol for your Tin Can content.

It is possible that the LMS or server you're using is already making use of a quiz_id=(3 - 6 digits) parameter.  Have you checked to with the LMS or server administrators about what parameters are acceptable or if there are any limitations?  You mentioned that the same parameter works with a SL1 or 2 file -- does that include the 3 to 6 digit window?

We would be happy to have a look at your edited output files and test on our end, too.  Our support team has the best resources for this testing, so feel free to share those files with us here.  You can reference this discussion for context.

Thanks!

Trip Levine

> It is possible that the LMS or server you're using is already making use of a quiz_id=(3 - 6 digits) parameter. Have you checked to with the LMS or server administrators about what parameters are acceptable or if there are any limitations?

The Articulate Storyline file breaks before it speaks to the LRS. The issue is that 

The issue stems from this method in app.min.js :

triggerNavEvent: function(e, t) {
var i = u.getCurrentWindow().getCurrentSlide();
i.get("slideLock") || c.trigger("presentation:onobjectevent", e + "_pressed")
},

Where `u.getCurrentWindow().getCurrentSlide();` returns `null`.

For some reason, passing `quiz_id` with a value of digits between 3-6 will cause that to be `null`. Otherwise, it works.

> You mentioned that the same parameter works with a SL1 or 2 file -- does that include the 3 to 6 digit window?

Yes, SL1 and SL2 worked fine with this parameter..

Will attach the file. It's a small 17mb.

 

 

 

This discussion is closed. You can start a new discussion or contact Articulate Support.