Forum Discussion
RESOURCE: Full Guide to xAPI and Storyline
Hello lovely Articulate Storyline users!
I've been working on an in-depth guide to sending custom xAPI statements from Articulate Storyline courses for over a year now, and the full guide is final...
Hi Devlin,
Great work on the guide. For others who are working on xAPI in Storyline, you can include the tincan-min.js file in a web object that is then automatically imported to the published package. Add the JS file in the same folder as the HTML. Add the JS to the HTML as an "object" - <object>...</object> (not as a script) to a non-displaying slide. This forces the web object builder to include the JS file. You can then add the JS file to a master slide where you need it by creating the "script" DOM element and attaching it to the document. That is done through custom javascript on the slide master. The script can then be referenced by your xAPI custom javascript on the slides that use that master slide.
Why do it this way? Because the tincan-min.js file is too large to just include in a custom javascript object directly in Storyline. It also means you don't have to manually modify the story.html file. Works great if you publish a Storyline interaction directly to Review 360 and then include it in a Rise document.
I just wanted to thank you - and credit you. You've helped me. Thanks!
Paul, honestly most of what you wrote is out of my current depth, but this statement stood out as it's one of the thorny issues we'll be dealing with as we implement xAPI. Would you happen to have any samples of this approach you could share, or perhaps touch base offline?
Paul, would you be willing to share a working example of this approach? I'm having a little trouble following it, and we're dealing with the exact issue you mentioned around the inclusion of Storyline blocks in a Rise course.
