xAPI URL Parameters- is there an easier way?

Dec 05, 2016

I've been doing some testing with content hosted on a web server trying to feed data to a LRS (SCORM Cloud or Wax).  Already read the support articles and was eventually able to set all the URL parameters so they would talk.  However that required manually:

  1. URL encoding the endpoint
  2. Base64 encoding the credentials
  3. URL encoding the actor
  4. URL encoding the activity
  5. Adding all the parameters (including a registration ID) to the URL used to launch.

I tried embedding all those settings in the tincan.xml file, no luck- had to be what is entered in the browser.  That's not very elegant, and it limits the ability to pull new registrations and actors at runtime (whether pulled from AD, user entry, etc.).

I did see someone worked on a PHP solution, so I guess my questions are:

  • Am I missing a simple place to put this info in Storyline prior/while publishing?  It seems that things like credentials and the endpoint would be simple enough at least.
  • Anyone else have experience with web server-LRS that can offer insight on a cleaner solution?

It may be that some of this has to be a feature request, I even jumped from SL 2 (at work) to SL 360 (personal) to see if there was better xAPI support but it appears the same.

 

1 Reply
Leslie McKerchie

Hi Sean!

I will not say that I fully understand what you are asking here, but if you are modifying the output, then that is not something I would be able to support. 

Hopefully someone in the community with some experience will be able to chime in and assist you here.

You are welcome to share your thoughts with our product development team here and I'm sure they will understand your need better than I could.

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