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:
https://community.articulate.com/discussions/articulate-storyline/how-to-send-tin-can-statements-with-javascript?page=2
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
Love the challenge Ros :) Hopefully someone will be able to chime in and assist you soon.
I was also looking for instruction of how this works from soup to nuts. I hope someone gets back to us on this!! The information out there presently is a bit generic and confusing.
Hi Joseph and welcome to E-Learning Heroes!
I'm not sure that I'm understanding what you need assistance with here? Could you elaborate on what you are asking or needing information on?
I was hoping for some clear instruction on how to implement Tin Can API in Storyline. Specifically, how to customize statements in Storyline to generate reports for specific actions inside a slide. For example, button clicks.
Thanks for the explanation Joseph. Sounds like you are wanting to set up some custom coding and reporting and that is a bit outside of my realm of support. Hopefully someone will be able to chime in and assist you here.
That's the point of the thread...
I understand Ros, just making sure I wasn't overlooking something I could have assisted Joseph with :)
I believe this got me:
I was also looking for instruction of how this works from soup to nuts.
Not terms I've ever heard of before :) Sorry for my confusion and need for clarification.
Haha, ok fair enough :)
I would also appreciate information on this and hope that at some point in this discussion somebody will be able to provide it!
I too look forward to this. I have read a bit about Tin Can but still have more questions than answers on how to implement it.
This is an intriguing topic for me as well. I wish I could contribute but am anxious to learn more...
Hi all,
A while ago I posted a sample for sending custom TinCan statements to an LRS. See:
https://community.articulate.com/discussions/articulate-storyline/how-to-send-tin-can-statements-with-javascript
Find "TinCanStorylineExample.zip" on that page. I don't have Storyline anymore, so I can't look at the sample...but if memory serves, it should be a good template.
Thanks for popping in to share Norm :)
Yes Norm, that's the link I have above. I have been dissecting it a lot. The issue is not having a working .story sample. Seeing output doesn't help much because simply, we can't see how it is done.
I just see a lot of assumptions on people's knowledge, ironically exactly what SMEs tend to do. Nothing in that thread is simple. Where gaps are, its simply assumed people know, or "go read this 300 page document", which has no relevance to Articulate Storyline.
A lot of gaps need filling. Do this day we still have no step by step instruction on custom TinCan statements inside of Articulate Storyline. So much so that staff can't help either. I'm sure even Leslie here is dying to find out :)
I'm still working on it myself, hopefully someone can chime in or I will figure this out on my free time.
Hi Ros. I'm pretty sure the file I referenced on that page ("TinCanStorylineExample.zip") has a .story file included.
If it does, I can't find it. Unless you put it in the .zip file yourself, published courses don't include the .story file.
Yes, I put it in the .zip file. There's one other file in there, the tincan javascript library, which is needed. (There's no published content in the zip.)
This post was removed by the author
This post was removed by the author
Hi Norm, I was going off of a different .zip on page 2 of that discussion, I did not see your sample buried in page 1. Thanks for the sample, I confirm it works! This has been a great learning experience. I have attached Norm's sample so people don't get confused when visiting here.
Thanks for keeping future thread visitors in mind, Ros. :) Glad you got it sorted!
I have to reopen this thread.
Using ScormCloud doing the same techniques, I cannot seems to get this to work anymore. I'm using the same files, but ScormCloud has been updated and I feel like it has screwed up these custom statements in Articulate Storyline.
Does anyone have any luck reproducing custom TinCan statements? I am now at a complete loss....
Hi Ros,
Happy to have you reopen the discussion - did you reach out to SCORM Cloud as well about the updates they may have made?
If you want to reach out to our Support Engineers, they're ready and waiting to help you here!
Hi,
I am publishing my Articulate Storyline 360 course in LMS: TinCan API standards. The course has custom xAPI statement using javascript, that sends data to Watershed LRS. If I publish the course in SCORM 1.2, everything works. If I publish to TinCan API, then there is no connectivity to the LRS. On debugging, it shows bad request server error (400). I am testing the course in SCORM Cloud. Has anyone used custom TinCan statement in Storyline course (to an LRS) and published the course in TinCan API standards with success?
Hi there, Tanmay. I replied to your other post here, so we can continue the conversation there if you'd like!
This discussion is closed. You can start a new discussion or contact Articulate Support.