SCORM Wrapper

I'm not sure if this is an Articulate issue, or something from Plateau/Success Factors, but here goes.

I'm publishing my Articulate 2013 course in SCORM 2004 v2 for deployment on our Plateau LMS.  When the course is launched, it comes up in a "wrapper" with a set of control buttons (Suspend, Continue, Exit).  Is this something from Articulate, and if so, how can I manage it?  At the very least, I need to edit those buttons because the naming is not at all intuitive. 

I don't see any place within the Articulate tool to control this, although I am seeing some possible connection in the manifest file. 

Help?

12 Replies
Steve Flowers

Hi Phillip, 

Those are part of the content player frame generated by Plateau. It's been awhile since I've monkeyed with the launch settings in Plateau. You may be able to change this in the configuration.

Have you tried a SCORM 1.2 publish to see if the player frame behaves differently? If you're only dealing with a single module, you may see different / better results with SCORM 1.2. At the very least you may see fewer buttons in the wrapper.

Phillip Loughlin

Thanks, Steve.  That's sort of what I was thinking, but our admin couldn't find the settings.  I've sent a note to the Plateau forums in hopes that they'll have the answer I need. 

Gotta use SCORM 2004 in order to capture and report an open-ended text response in the module, otherwise, I've always been real happy with simple AICC (and life would be much simpler).

Thanks again!

Steve Flowers

If you run out of options in the configuration, you might be able to leverage DOM to change these labels or hide the buttons alltogether with some JavaScript in a trigger. Since the player frame is "upstream" from the content, you should be able to target the element. From what I've read about Plateau and SCORM2004, apparently they added the suspend button because they intended for the participant to click it... Because they require suspend to be invoked by the user. 

Accessing the buttons and features through DOM you should be able to trigger these before unload. Which is how it should be done Plateau / SuccessFactors never scored many points with me.

Ashley Terwilliger

Hi Raymond and Jakob, 

I haven't seen any other updates here, and as Steve initially mentioned it's a part of the wrapper within the LMS. To confirm this (in the event that maybe you're seeing something a little different) you could upload a copy of your published output to SCORM Cloud which is an industry standard for testing SCORM content. You could also reach out to others in this thread directly using the "contact me" option on their profile pages. 

Janet Canaan

Looks like this thread has kind of dwindled away, but the problem still exists. I am publishing a SL2 course, SCORM 2004 4th ed, to SuccessFactors LMS. The three wrapper buttons appear and I've tried everything I can think of to get rid of them. I've attached the imsmanifest for the course, and the KnowledgeBase article from SuccessFactors. Nothing is working. Still looks like this:

Has anyone had success in getting rid of these buttons? Been banging my head on the wall for several weeks now and need some help. Thanks!

suzanne meyer

Janet - I am experiencing the same problem.  Success Factors said to add code to the imsmanifest file to hide the controls but i have no idea where to add it.

SF Learning launches SCORM 2004 4th edition content inside an LMS-provided navigation wrapper. If your content is coded to set the required navigations requests and the LMS-provided navigation buttons are not needed, they can be hidden by adding the prescribed tags below in the imsmanifest file.

<adlnav:presentation>
<adlnav:navigationInterface>
<adlnav:hideLMSUI>previous</adlnav:hideLMSUI>
<adlnav:hideLMSUI>continue</adlnav:hideLMSUI>
<adlnav:hideLMSUI>exitAll</adlnav:hideLMSUI>
<adlnav:hideLMSUI>suspendAll</adlnav:hideLMSUI>

Hoping someone has additional info or provide suggestions on adding this to the manifest file.

 


</adlnav:navigationInterface>
<adlnav:presentation>

 

A B

Not sure if the above people ever got answers. Success Factors and their "trouble" fully implementing a 10-year-old technology (and make no mistake, SCORM 2004 4th Edition _IS_ a 10-year-old technology now) are well known, unfortunately. I won't say they're the only ones who push the removal of SCORM controls back on the customer (along with countless other things), but you'd think they were trying to be the champions of it.

Where I work, the solution is to publish the project, open up the lmsmanifest.xml file in Notepad, scroll down to the SECOND <title> tag, and right underneath it, paste in:

<adlnav:presentation>
    <adlnav:navigationInterface>
        <adlnav:hideLMSUI>continue</adlnav:hideLMSUI>
        <adlnav:hideLMSUI>previous</adlnav:hideLMSUI>
        <adlnav:hideLMSUI>abandon</adlnav:hideLMSUI>
        <adlnav:hideLMSUI>exit</adlnav:hideLMSUI>
        <adlnav:hideLMSUI>abandonAll</adlnav:hideLMSUI>
        <adlnav:hideLMSUI>exitAll</adlnav:hideLMSUI>
        <adlnav:hideLMSUI>suspendAll</adlnav:hideLMSUI>
    </adlnav:navigationInterface>
</adlnav:presentation>

Any <imsss:sequencing> tag should go UNDER the code you're pasting in. Inserting XML code into wrong places will break the functionality required for the LMS so it may take some practice. Leaving this here for anybody who comes after. Naturally people don't have to hide all of navigational controls like above, but we do.

This is one of countless ways in which SF "declines" process improvements. They know it's an issue. Whoever's pulling the strings, though, doesn't seem to care. Again: ten years old. As I understand it, our department (Fortune 100 company) is looking for a new LMS administrator, so soon maybe we won't have to care either.