Copy link to clipboard
Copied
Hello,
I have a bunch of modules I am creating in Captivate, all of which are to be accessed from within Captivate Prime. What I would like to do is have a button at the end of each module, that when clicked, opens the next module. Is this possible? I know you can open a file or another Captivate project by clicking a button, but I don't think this will work.
Any ideas?
Under the SCORM standard, any SCO should NOT be directly calling another SCO. The LMS should be in control of which SCO gets launched next so that it can be sure to track the learner interaction.
So what you are proposing is not recommended by the SCORM standard. That's not to say it is not possible. Just that it is not a valid SCORM behaviour.
Copy link to clipboard
Copied
I have no experience whatsoever with Prime, only with other LMS's. So I wonder if it wouldn't be more appropriate to post this in the Prime forum, because I suspect it is more linked with Prime's functionality/limitations than with Captivate's? Let me know, I can move the thread.
Copy link to clipboard
Copied
Hi , yes please if you wouldn't mind. I'm guessing it's a bit of both, as the button functionality would be done in Captivate.
Copy link to clipboard
Copied
Out of curiosity, with your experience, would it be possible with other LMSs?
Copy link to clipboard
Copied
It depends if you are dealing with normal packages or with SCO-modules. For the last the answer is negative, for the first it is mostly possible, although I often choose to use the LMS features to create such a sequence. After all course and user management are typical features of the LMS.
I'll move the thread.
Copy link to clipboard
Copied
Thank you.
Copy link to clipboard
Copied
Under the SCORM standard, any SCO should NOT be directly calling another SCO. The LMS should be in control of which SCO gets launched next so that it can be sure to track the learner interaction.
So what you are proposing is not recommended by the SCORM standard. That's not to say it is not possible. Just that it is not a valid SCORM behaviour.
Find more inspiration, events, and resources on the new Adobe Community
Explore Now