Connecting Articulate Storyline 3 Output to Learning Locker LRS

Feb 21, 2018

Hi,

We are trying to connect the output (answers given) of an Articulate Storyline 3 story to a "Learning Locker" LRS data store.

However, we are struggling to find any suitable documentation on how to do this. When we publish the AS3 story we can't seem to find an option to selected the LRS data store. There are options to publish for LMS and WEB etc, but nothing seems to detail how to connect the AS3 story to Learning Locker.

I have found a forum post that seems to give the URL syntax on how to do this:

https://community.articulate.com/discussions/articulate-storyline/post-tincan-statements-from-html5-output-to-lrs

but I am unable to find any official documentation (or even if this is the correct way to do things). 

Also, I am unsure how to pull any data written to Learning Locker back out again - but that would likely be a questions for Learning Locker.

Could you point me in the right direction please?!

Many thanks,

Lewis.

3 Replies
Lewis White

 
I have worked out the answer. 
 
The issue was piping the output of the Articulate Storyline 3 courses to the Learning Locker LRS via xAPI. Specifically the “launch URL”.
 
The documentation is confusing and flaky as the “launch URL” is used interchangeably between the URL the user pastes into their browser to run the course (i.e the link clicked from the LMS to run the course, depending on your implementation) and the Articulate Storyline 3 –> Publish –> Reporting and Tracking –> “Launch URL”.
 
This Launch URL (https://community.articulate.com/discussions/articulate-storyline/post-tincan-statements-from-html5-output-to-lrs) is the URL configured and used to run the course.
 
The Articulate Storyline 3 –> Publish –> Reporting and Tracking –> “Launch URL” should just be the domain or where your AS3 content will be hosted. So no authorisation parameters etc.
 
Seems simple enough, but took me a while to work this out.

Check your LL agent authorisation is correct by using postman and you can post statements to the LRS (from a machine other than localhost!).

Also, make sure your AS3 content is first published to your local C drive (not a network drive), as this causes issues. Then move to the destination hosting - serve properly via a web server, not just a link to a FILE:// resource.
  
They also recommend using SCORM cloud to check the output of the xAPI statements from the AS3 content. But I have not been there yet. I will do soon when I get into the specifics and customistaion of the xAPI statements generated.
 
Hope this helps and saves you guys a bit of pain banging heads against walls!
 

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