Forum Discussion
SCORM 1.2 Question Text
I've noticed that our LMS, (SABA) has a field cmi.interactions.n.text that accepts the question text of a slide. Is there any way we can get Storyline2 report the question text to the LMS in this field?
Thanks
25 Replies
So glad to hear that Dustin - just one of the many reasons we keep these discussions around!
- DaveCox-67b3049Community Member
I'm so glad that this helped you Dustin.
- LauriHaganCommunity Member
I tried the SCORMFunctions.js patch above that Dave posted but it did not work for me. Previously I was using the replacement files that Vance Sumner had posted on the Saba Community site and they worked perfectly until today when I updated Storyline 360 to current version. Does anyone else have new patch or replacement files to get the question text to appear in Saba LMS when publishing to SCORM 1.2? SCORM 2004 does not work for us for the reasons cited above.
- DaveCoxCommunity Member
Hi Lauri,
A lot has changed in Storyline 360 since Storyline 2, and I haven't looked at that patch since Storyline 2. The problem stems from the fact that the SCORM 1.2 spec does not specify what to do with the question text, and therefore is was not implemented in Storyline.
I will look at it as soon as I can, to see if I can rewrite the patch for you. I'm currently in the middle of a move, so it may be a bit. I apologize for the inconveniance.
Dave
- LauriHaganCommunity Member
Articulate sent me a link so that I can revert back to Storyline 360 version 3.35.21017.0. Once I did that and applied the two replacement files recommended by Saba I can now see the question text again in Saba Cloud when publishing to SCORM 1.2.
- DustinBauman-02Community Member
I can post the working patch for SL360, I have kept them up to date as we are using Saba as well. The big thing is that SL changed from SCORMFunctions.js to SCORMDriver.js, that is probably one of the reasons it is no longer working.
Let me know if you would like the new files and where this needs to be placed and I will gladly upload. We have been successfully using q level reporting for over 2 years now with Saba.
FYI, I worked with Vance and Dave's patch to get the Saba patch you have from Vance to work in Saba.
- LauriHaganCommunity Member
Yes! It would be great if you could post the files and the Articulate 360 folders they belong in. Thank you!
=====================================================================Please note that this e-mail and any files transmitted from
Memorial Sloan Kettering Cancer Center may be privileged, confidential,
and protected from disclosure under applicable law. If the reader of
this message is not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient,
you are hereby notified that any reading, dissemination, distribution,
copying, or other use of this communication or any of its attachments
is strictly prohibited. If you have received this communication in
error, please notify the sender immediately by replying to this message
and deleting this message, any attachments, and all copies and backups
from your computer. - JustinBachmannCommunity Member
Hi Dustin,
I would be interested at looking at those file as it many help me with a issue I am working on at the moment.
Thank you
- JaridGoodwillCommunity Member
Hi, Dustin. I recently tried to implement Dave's solution on a SCORM 1.2 course and noticed the absence of the SCORMFunctions file. Would you mind sharing a sample SCORMDriver file and note where the changes were made in the code?
I know this is an old thread but having your solution would really help right now.
- DaveCoxCommunity Member
That is awesome Dustin, I do remember that change. I'm not using SABA anymore, so I quit working on it.
Dave
- IanJanes-9422fdCommunity Member
I'll just share this in the hope that it helps anyone who also stumbles across this thread and may not be aware: the cmi.interactions.n.text field is not part of the SCORM spec (either 1.2 or 2004; cmi.interactions.n.description is 2004-only), so in that sense this absolutely was a SABA issue rather than a SCORM or Storyline issue.
Related Content
- 10 years ago
- 8 months ago
- 10 months ago