SCORM 2004 Sequencing Tidbits

SCORM 2004 provides a powerful language for controlling sequencing and navigation between SCOs. As with any deep specification, it can take a little getting used to. When you’ve been working with it for a while, you sometimes forget all those little stumbling blocks you overcame on your way up the learning curve.

I recently had a chance to work on some rather involved sequencing templates after a several month sabbatical from sequencing and decided that this time around I’d write down all those juicy tidbits that are typically learned the hard way. I’ll be sharing them up here over the next few weeks and hopefully making life a bit easier for anybody who finds their way over to our little corner of the blogosphere.

  • Dear Rustici Team,

    I have one issue with a SCORM package and a question for you.
    I know that I can disable the LMS “Continue/Previous” buttons but can I enable them after the objective is completed? So that I can press “Continue” only after the objectives are completed?

    Why I’m asking this? I’ve created a forced sequencing, simillar to the one on your website, but if I press “Continue” in the LMS without completing the objectives, I receive an error that won’t be fixed.
    The easyest way would be to disable the “Continue” button when a section is opened and enable it after that section’s objectives are completed.
    The hardest way would be to use content internal “Continue/Previous” buttons, like in the ADL examples but I don’t want to think at that:D

    Can you please help me?

    Thank you,

  • Marius, I posted a reply to this question in our support forums at

Click to Hide Advanced Floating Content

Coming soon!'s same great content is getting a brand new look.

Subscribe to be the first to hear of the relaunch.