Anyone out there attempting to publish your Storyline course as Tin Can but then wrap that package in a SCORM1.2 API to communicate back to LMS?
Our LMS doesn't support xAPI yet. So I'm trying to publish the course as Tin Can to send to our LRS but also report Completion, Scores, etc. back to our LMS. The course will be hosted on the LMS. Any one have success doing that or know of a solution?
I think a Scorm Dispatch wraps courses into a SCORM 1.2 container, but I'm not sure it will help you. It may be worth investigating and you can test it with a free trial account. https://scorm.com/scorm-solved/scorm-dispatch/
When constructing your actor string, the script might not be pulling the name properly from HTML5 output. In Chrome, when running your SCO click the address bar then hit CTRL-SHIFT-I. The console will probably display the error that is stopping up the script.
The error is likely kicking up when you are pulling the student name from the LMS to form up the agent. This works great in Flash:
lmsAPI=parent;
var username=lmsAPI.GetStudentName();
In HTML5, I've seen this fail. Few ways I've dealt with this. First is simply to set it up this way:
var username=GetStudentName();
If this fails to work in Flash, then a conditional should get it:
Thanks for the quick reply, Steve. I was hopefully but there were no errors
in the console. I'm console.logging the URL with the endpoint and other
parameters and everything looks good. I didn't even a username variable in
the lms.js file.
Any other recommendations? I'm really stuck here. Again, I'm publishing to
both SCORM and TinCan and then setting tincan to True and copying over the
tincan.xml file to the package. Works great in Flash but no tincan
statements being sent using HTML5 version. SCORM is still being tracked in
HTML5 version.
5 Replies
I think a Scorm Dispatch wraps courses into a SCORM 1.2 container, but I'm not sure it will help you. It may be worth investigating and you can test it with a free trial account. https://scorm.com/scorm-solved/scorm-dispatch/
Thanks for the info, Michael. That's not going to work for my scenario.
Hoping others are doing something similar. Anyone?
Update: It's now working while flash based but not as HTML5. We are no longer supporting Flash so HTML5 is a requirement.
Anybody else run into issues sending to LRS when using HTML5?
Hi, Dave -
When constructing your actor string, the script might not be pulling the name properly from HTML5 output. In Chrome, when running your SCO click the address bar then hit CTRL-SHIFT-I. The console will probably display the error that is stopping up the script.
The error is likely kicking up when you are pulling the student name from the LMS to form up the agent. This works great in Flash:
lmsAPI=parent;
var username=lmsAPI.GetStudentName();
In HTML5, I've seen this fail. Few ways I've dealt with this. First is simply to set it up this way:
var username=GetStudentName();
If this fails to work in Flash, then a conditional should get it:
lmsAPI=parent;
var username;
if(typeof lmsAPI.GetStudentName=="function"){
username=lmsAPI.GetStudentName();
}else{
username=GetStudentName();
}
Thanks for the quick reply, Steve. I was hopefully but there were no errors
in the console. I'm console.logging the URL with the endpoint and other
parameters and everything looks good. I didn't even a username variable in
the lms.js file.
Any other recommendations? I'm really stuck here. Again, I'm publishing to
both SCORM and TinCan and then setting tincan to True and copying over the
tincan.xml file to the package. Works great in Flash but no tincan
statements being sent using HTML5 version. SCORM is still being tracked in
HTML5 version.
Many thanks!
dave
This discussion is closed. You can start a new discussion or contact Articulate Support.