We're working on some branching courses and we thought it would be a great idea if we could eliminate the need for a user to select which business unit they are in to define the branched content. If the LMS and Storyline could "talk" to each other and identify the business unit - then Storyline could auto-direct them to their branch of content. Has anyone heard of this capability or applied it in their development? Thanks!!
Interesting concept and something I've heard other users discuss before - as it often involves passing information back and forth using Javascript which is not something staff can offer support with. You may want to begin here and see what you can figure out from that.
Thanks for the follow up Ashley! I've been doing some digging and found a couple threads that got us thinking and talking at the office. We're going to try some stuff out. If it works, it'd be really sweet.
Matthew is correct, the data available from most LMS system is quite limited. The Tin Can and xAPI industry folks might have open source libraries to help, though I don't believe I've seen organization.
5 Replies
Hi Gregory!
Sounds like you already know how to set up branching within your course and are looking for a different design.
Hopefully someone in the community will be able to chime in and assist.
Hi Gregory,
Interesting concept and something I've heard other users discuss before - as it often involves passing information back and forth using Javascript which is not something staff can offer support with. You may want to begin here and see what you can figure out from that.
Thanks for the follow up Ashley! I've been doing some digging and found a couple threads that got us thinking and talking at the office. We're going to try some stuff out. If it works, it'd be really sweet.
No problem Gregory - and definitely keep us posted!
Matthew is correct, the data available from most LMS system is quite limited. The Tin Can and xAPI industry folks might have open source libraries to help, though I don't believe I've seen organization.
This discussion is closed. You can start a new discussion or contact Articulate Support.