Enrollment SCORM - PreAssessment - affect next module visibility

[nimam7453071]

Hi, I am making an enrolment learning module and want to use the button/selection options to decide which modules a learner can move onto.

e.g

First they do the Enrolment Module and choose their discipline, then they will do one of these depending on their choice:

Module Mechanical (visible if they chose Mechanical in previous module)

Module Electrical (visible if they chose Electrical in previous module)

Module Communications (visible if they chose Communications in previous module)

Do we use quiz variables? What is the best approach if the first module is just an assessment? Does the output need to be a number/ID/result value (say 1-3)

[RodWard]

What you are talking about doing is TECHNICALLY possible, but...strictly-speaking it does actually break the SCORM rule that says each SCO module is not supposed to look outside itself or directly link to another SCO module.

If you were thinking of having quizzes or assessments in each of these modules, then you'd ideally need to create them in separate CPTX files because the SCORM rules also state that each SCO can only have one quiz/assessment that reports back to the LMS.  If you create all of the modules inside a single CPTX then you will not get any granular reporting split up between the different quizzes.  The SCORM LMS will just see them all as one big quiz.

If you want to have each module separately stored and delivered from the LMS then your branching and control of the visibility of subsequent modules would need to be done by the LMS, not by your Captivate SCO.

To achieve your goal you would need to persist variable data OUTSIDE of the SCO module itself.  Since you are talking about delivering all these modules from a SCORM-compliant LMS, then ideally you should be thinking of persisting the variable data in the LMS database.  But that's not necessarily as easy as you might hope because a SCORM LMS is only really interested in storing SCORM data, not ad-hoc other data from variables that you have separately created in your course and that have nothing to do with SCORM.

[nimam7453071]

Thanks Rod. I was thinking of using he LMS (Totara) to do the branching/visibility of Module M, Module E and Module C depending on the outcome of the Enrolment module. 

Within the Enrolment module, if I have a button for Mechanical, Electrical and Communications within on one of the slides I can run advance actions easily. 

I'm wondering what advance actions I can do? i.e to edit a system/result variable? Some thing like setting the score to:

If Mechanical Results = 20%

If Electrical Results = 40%

If Communications Results = 60%

Then use the LMS to do the rest.

[RodWard · Accepted solution]

System Variables inside a Captivate module mean nothing to the LMS.  It's only interested in the SCORM variables that tell it whether the module was completed and whether the quiz was successfully passed etc,

It sounds like what you might need to look into is whether or not your Totara LMS supports use of SCORM 2004, not just SCORM version 1,2.  With either SCORM 1.2 or 2004 you could build a Multi-SCORM package that contained multiple SCO modules, but version 2004 added the ability to define rules that controlled navigation and sequencing which then allowed the LMS to decide which SCO would be offered next after one of the SCOs was finished.  SCORM 1.2 doesn't offer this feature.

Captivate does provide the MultiSCORM packaging tool that allows you to bundle together a number of published SCORMs from separate Captivate CPTX files into a single multiSCO package.  If you publish to SCORM 2004 this tool does allow you to specify some rudimentary sequencing rules.  But if you publish first from the tool and then hack the imsmanifest.xml file it creates, you can manually change the code to make the branching more sophisticated.  This is normally outside the skillset of most Captivate developers.

Alternatively, you should ask the Totara people about whether the LMS offers any ability to do something like this OUTSIDE of the SCORM manifest.