Sending Built-In Storyline 360 Variables to LRS
Nov 12, 2019
By
Tamika Base
I've built a bug-reporting slide layer that will be repeated across each slide in the course. It communicates name, email and problem description from input boxes to an LRS via xAPI, but I'd like to be able to send a javascript concatenation of the system variables as
SceneNumber . SlideNumber + SlideTitle (i.e. "2.6 Chapter Summary")
to be able to map their comments back to exactly where they were within the course when they encountered the issue. I can get these variables to appear on the slide as I want them, but does anyone know how to get them to be concatenated into a separate project variable?
5 Replies
Hello, pretty cool, I am unable make a JS suggestion for you here, but curious as to what Review 360 does not provide that you are needing?
I assume you want a more robust system that will enable you to take control of all of the data with your LRS to manage your comments?
We sometimes export the Review comments to an online Excel doc.
Hi Jeff,
This "bug report" layer would be in the finished course, not just in the initial drafts. So Review 360 seems like a great tool for reviewing (which has been a sore spot for IDs for a long time), but we're looking for something to exist in production.
The courses we're managing are for a very robust piece of internal software that is constantly changing. We need a way to allow students to self-report when there are any important discrepancies in the training we've missed because keeping up with all the changes as they roll out is not realistic.
So while I have the name, email and bug write-up communicating with the LRS, there isn't an easy way to map back to where the comment came from. I could do this by hand, (on entry to each slide, have a custom variable change to "x.x Description") but doing this as static text would make for a lot of work if slides are added/moved/subtracted. Near as I can tell, referencing the javascript would be the best, future-proof way to get this information.
Solved it!
Would you be able to post how you solved this? Thanks!
Yes!
This discussion is closed. You can start a new discussion or contact Articulate Support.