Storyline and custom TinCan API statements

Jan 03, 2017

Hey all,

I've been struggling to find any information regarding customizing TinCan Api statements. I found this thread:

But when I chimed in it, I was informed that the thread out "out of date". So I am creating a new thread in order to discuss this. My issue with the thread is that there are no .story samples to view and learn from. Just a bunch of vague javascript code and a lot of assumptions on the knowledge of the readers. 

So I want to break this down and have a step by step instructions for real novices with this stuff.

So if one of you genius's can setup a .story, with executable javascript, something very simple, and have it spit out on the LRS side some variables we can follow and record. For example, a button that that has been clicked, or a layer that has been visited. So when we look at the LRS we can see if the user click on the button or visited the layer. Or something similar.

Let's help the community together!! Challenge has been made :)

P.S. I use Articulate 360 now, but Storyline 2 is fine. Also using Scorm Cloud for an LMS/LRS.

24 Replies
vimal singh

Hi Ros/Norm,

Your example is pretty clear, but this is not working for me. i have followed the steps he has mentioned in the notes. Also i have used the same published file provided by Norm. but it's not working. I am getting only default statements.

i have done this:

  1. Tried publish using only HTML5, and also tried with Flash with HTML5 fallback.
  2. using SL360
  3. using Tincan as published setting.
  4. Using LRS

Please help.



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