I am currently working on a multi-sco course, where each Storyline module is it's own sco. On the last page of a module, I would like to be able to prompt the user to continue to the next sco.
So far I've added a button that executes the following JavaScript:
I haven't had any luck with this so far. Is there a better to go about doing this, or has anyone had any luck using sequencing with storyline? Any pointers would be greatly appreciated!
I believe my problem right now is not being able to execute calls to the LMS from inside of Storyline. I am finding this thread here very useful so far: http://community.articulate.com/forums/t/20251.aspx
I will post in this thread If I have any luck with my problem!
Hi Kath. Sorry for the late response in getting back to you - but to keep a long story short, I didn't have much success.
Part of the problem I had was sending external calls manually to the LMS, and the other part is that there is not much support for SCORM 2004 4th Edition in general. I believe the best approach to take would be to load up single SCO courses and make your LMS handle how each SCO is unlocked.
Sorry for digging up an old post, but I was having this exact same issue and had to figure it out myself in Storyline 2. The javascript code is very close to what Andrew attempted:
For my team's project, this was added as a trigger on the next button at the last screen, followed immediately by a trigger to exit, properly telling our LMS to run the next SCO.
No worries Kenneth! I appreciate you popping in to share your solution and experience :) It may not help the users that were already here, but it could certainly assist someone that runs across this thread in the future.
Hi Kenneth. Glad you were able to figure it out! I love the concept of having easily navigable multi-sco courses, but it's difficult to find an LMS that supports all those features.
Hopefully your fix will help anyone else jumping down this rabbit hole!
10 Replies
HI Andrew and welcome to Heroes!
You may want to look into the methods in this article on tracking multiple SCO's although they are not officially supported by Articulate.
Thank you for your response and the link Ashley.
I believe my problem right now is not being able to execute calls to the LMS from inside of Storyline. I am finding this thread here very useful so far: http://community.articulate.com/forums/t/20251.aspx
I will post in this thread If I have any luck with my problem!
Sounds good Andrew and please keep us posted!
Hi Andrew, did you ever manage to get your mult sco package sequencing?
Hi Kath! This thread is a bit dated as well, but as I mentioned here, you may want to reach out directly.
Welcome to E-Learning Heroes by the way.
Hi Kath. Sorry for the late response in getting back to you - but to keep a long story short, I didn't have much success.
Part of the problem I had was sending external calls manually to the LMS, and the other part is that there is not much support for SCORM 2004 4th Edition in general. I believe the best approach to take would be to load up single SCO courses and make your LMS handle how each SCO is unlocked.
Thanks for popping in Andrew :)
Sorry for digging up an old post, but I was having this exact same issue and had to figure it out myself in Storyline 2. The javascript code is very close to what Andrew attempted:
parent.SCORM2004_CallSetValue('adl.nav.request','continue');
For my team's project, this was added as a trigger on the next button at the last screen, followed immediately by a trigger to exit, properly telling our LMS to run the next SCO.
Hope this helps!
No worries Kenneth! I appreciate you popping in to share your solution and experience :) It may not help the users that were already here, but it could certainly assist someone that runs across this thread in the future.
Hi Kenneth. Glad you were able to figure it out! I love the concept of having easily navigable multi-sco courses, but it's difficult to find an LMS that supports all those features.
Hopefully your fix will help anyone else jumping down this rabbit hole!
This discussion is closed. You can start a new discussion or contact Articulate Support.