I'm currently working on an e-learning that must be delivered in 1 .sco file (Scorm 1.2) to the client. My problem is I need branching. Something quite simple but it's not possible to achieve with the scorm packager it seems.
the idea is, I have 1 parent file and at a certain point the trainee will chose either scenario 1 or scenario 2. Those scenarios are capitvate files that are exported to Scorm.
So usualy (without Scorm) I would just make a relative link to the index file of the dependant file in the parent file, but... it doesn't seem to work.
And one more imprtant thing to notice is that the complete, not complete criteria should be attached to the scenarios and not the parent file.the scenarios alos contain testing, with results that should be reported back to the LMS.
What you are trying to do is essentially bypass having the LMS launch each SCO module, which is what the SCORM standard says should happen. Under the standard, each SCO is not allowed to directly call another SCO. The SCO gets launched when the learner clicks a link in the LMS, the learner completes the SCO, the LMS captures the completion and scoring data, and then that SCO shuts down (terminates). Either the learner will click another link to launch the next SCO, or if the SCORM package specifies sequencing rules, then the LMS can determine which SCO should be launched next. (However, sequencing rules are more related to SCORM 2004 and you are only using SCORM 1.2.)
So the limitation is not really with the SCORM Packager. You're just trying to do something that would be breaking the SCORM standard. It's designed to work that way for a reason. If you don't allow the LMS to do its job then the scoring data may not be captured correctly, etc.
Each separate SCO is allowed to report its own completion and quiz scoring to the LMS. But if that SCO is part of a multi-SCO course, the final result for the course should be a 'rollup' of all scores. Again, that's something you want the LMS to handle. So, you need to use the SCORM standard as it was designed to work.
Are you as developer defining which scenario has to be done or does the learner have the choice? In the latter case create a slide acting as a dashboard with two buttons: one for each scenario, which will use the command 'Jump to' and navigate to the first slide of that scenario.
Keep each scenario in a liniear sequece. You can use a shape button 'Next' on the first slide of the scenario, which you time for the rest of the project and having the default command 'Go to Next Slide'. Do you need Back navigation? On the first quiz slide, hide the Next button. After the quiz, score slide use the Quiz actons to navigate to an end slide. Same workflow for the other scenario.
Have a look at this example of Branch Aware course: