Tincan statements differ for Flash and HTML5
Dec 20, 2016
I am developing a template quiz in Storyline 2. It is a question bank with 5 multiple choice questions. Navigation between the questions is with the previous and next buttons, with only the last one having a submit button - the design calls for students being able to navigate back to questions and answer them differently if they wish, only being locked into answers for the entire quiz when they push the submit button on the final question. The student upon re-entering the quiz sees all their previous answers pre-checked, and a green or red box (with an icon) around the answer if they got the question right or wrong respectively on the previous attempt. I have a special setup on the final slide to exit the course, but re-start the quiz on the first slide when the quiz is re-launched with the state object still loaded, so resume data is retained. The question bank is linked to the results slide, which is tracked for Tincan reporting.
This almost works how I want it to, except for Tincan API statements. The issue is that at the end of the quiz when flash is enabled in the browser, there are six important Tincan API statements sent to the LRS - one for the quiz overall (passed or failed, and what score), and one for each of the five individual questions in the quiz (the question, responses, and what the student chose, and whether or not they got it right).
When flash is enabled in the browser this is exactly what I get. But when flash is disabled and the quiz is launched in HTML5, only the overall result slide Tincan API statement is sent to the LRS. The five individual Quiz question Tincan API statements are not sent at all.
I have tested this in both SCORM cloud, and the Learning Locker LRS we are using - the result is exactly the same.
Does anyone know how to overcome this issue?
(p.p.s I forgot to mention I do not use submit interaction triggers in any of the questions. Doing so would lock the question answer in which is against the design spec - students must be able to navigate previous and next between questions, and all of the questions need to be locked in all at once when the hit submit on the last question, and got to the result slide. This seems to work fine in Flash, but not HTML5 with missing Tincan API statements. Almost all other statements - such as experienced etc work fine in HTML5)
This discussion is closed. You can start a new discussion or contact Articulate Support.