I am looking to publish a Rise course to xApi, and then test it in SCORMcloud or Watershed. With other authoring tools, I have added the LRS endpoint, key and secret, details at the point of publishing. Where do I add this information for a Rise published course? Do I need to edit one of the published files?
If the information there isn't exactly what you're looking for, our Support Engineers would be happy to help you get the answers you need! You can reach out to the team by clicking here.
Not OP but this is causing us headaches too. We have 15-20 people globally that are not super technically adept and asking them modify tincan.xml is not the right solution. Is there any plan to just add endpoint/secret input to the export dialogue? Right now it's way easier for us to just use Adapt.
5 Replies
Hi David!
You may have already come across this helpful article, but I thought I'd share it in case you haven't seen it:
Implementing Tin Can API to Support Articulate Content
If the information there isn't exactly what you're looking for, our Support Engineers would be happy to help you get the answers you need! You can reach out to the team by clicking here.
Not OP but this is causing us headaches too. We have 15-20 people globally that are not super technically adept and asking them modify tincan.xml is not the right solution. Is there any plan to just add endpoint/secret input to the export dialogue? Right now it's way easier for us to just use Adapt.
Thank you for sharing, Simon. We're tracking requests for this function. I'll make sure this discussion gets updated if we add those fields.
Hi Alyssa.
Thanks for responding to my post, and the link suggestion. I will reach out to your support engineers.
Regards
Dave
Hi Simon,
I'm not sure if you have seen these videos from Mel Milloway? I found them really useful.
Using xAPI to Track Page Views and Clicks in Rise 1/2
https://youtu.be/XVmz7r6m3XQ
Using xAPI to Track Page Views and Clicks in Rise 2/2
https://youtu.be/bGGCMiBt-Ao
Hope this helps.
Regards
Dave
This discussion is closed. You can start a new discussion or contact Articulate Support.