How does one incorporate TinCan Api with Articulate?

Hi Trip,

Although you don't want to use SCORM, it may be helpful to test it there to see how it behaves in an industry standard testing method. That error you shared is similar to an error you may see in SCORM Cloud that appears according to the conditions in this article. 

It's only two solutions are "You're not connected to the internet", and "You're not using a standard browser". I've definitely made sure those two were accurate.  

Thanks for the recommendation on testing on SCORM. It does work within SCORM just fine.

All the TinCan Statements are going to / rather than to my designated endpoint. This is why this error is occuring.

I need them to go to an absolute URL that would be my app. I notice that in your /tincanAPI tutorial, you provide this information which can be written into the tincan.xml file.

http://my.lms.com/TCActivityProvider/story.html

?endpoint=http://my.lms.com/lrs/endpoint/

&auth=OjFjMGY4NTYxNzUwOGI4YWY0NjFkNzU5MWUxMzE1ZGQ1

&actor={"name": ["First Last"], "mbox": ["mailto:firstlast@mycompany.com"]}

&activity_id=61XkSYC1ht2_course_id

&registration=760e3480-ba55-4991-94b0-01820dbd23a2

And you even say ..

Articulate content will report statements to the Tin Can endpoint as described under the section Cross Origin Requests in Internet Explorer in theTin Can API. To summarize, if the endpoint is http://mycompany.com/TCAPI/endpoint/, then all statements will be posted tohttp://mycompany.com/TCAPI/endpoint/statements?method=PUT. Any required headers will be added to the request data as form parameters delimited by “&.” The JSON content will also be encoded and passed in the parameter named "content." All statements will be reported in this way regardless of browser or platform.

But.. changing the endpoint in the <launch> node in the tincan.xml file does not change where the JS/JSON requests are directed. The URL always goes here to the root.

Here's some failing examples :

/statements/?method=PUT

state?method=GET

See how they're not appending after my designated endpoint "http://my.lms.com/lrs/endpoint/" ?

It should look like this :

http://my.lms.com/lrs/endpoint/statements/?method=PUT

http://my.lms.com/lrs/endpoint/state?method=GET

Any clarity on this issue would be greatly appreciated! 

< deleted and put it previous answer >

Hi Trip,

I'm certainly not a Tin Can expert, and if it's working as expected in SCORM Cloud, then there wouldn't be much else I could offer in way of support. I  hope that someone in the community who is well versed in Tin Can could take a look at what you've set up and how it's interacting with your custom LMS. 

Hey Ashley,

  As far as I'm aware, this isn't TinCan. TinCan is working fine. The tincan.xml file produced by articulate and the file that from within Articulate's flash files that activates story.js does not properly adopt the "endpoint" as *clearly* stated in your documentation about how Articulate operates.

Your documentation says :

Articulate content will report statements to the Tin Can endpoint as described under the section Cross Origin Requests in Internet Explorer in theTin Can API. To summarize, if the endpoint is http://mycompany.com/TCAPI/endpoint/, then all statements will be posted tohttp://mycompany.com/TCAPI/endpoint/statements?method=PUT. Any required headers will be added to the request data as form parameters delimited by “&.” The JSON content will also be encoded and passed in the parameter named "content." All statements will be reported in this way regardless of browser or platform.

Maybe you should remove this section from your documentation, and any references that your app is compliant with TinCan?

Hi Trip, did you get the answer to your question offline? I am wondering the same thing.