SCORM Wrapper

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!

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.

Hey, Steve, thanks again for the suggestion.  Now I'll show my ignorance and ask, "what is DOM?" 

I've been all through the manifest and .js files via my Articulate package and all I've managed to do is confuse myself.

Hi Phillip,

I came across your post as we're running into the same issue in Plateau/Success Factors.  Were you able to find a way to remove these buttons?  Thanks!

Hi Katy,

This thread is a bit older, so I'm not sure that Phillip is still subscribed. You may want to reach out to him directly using the "contact me" option on his profile page. 

Hi Katy and Ashley

I am in the same situation..., any great solutions here?

Same....upload our scorm package and we have the banner/wrapper show up with the 3 buttons...

Can this be removed completely?

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. 

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!

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>

Not sure if the above people ever got answers.

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.

Hi A B,

Thanks for your feedback. Unfortunately, my SCORM file does not work after I put that codes. Perhaps I pasted it at different line. Would you mind to share where exactly I should place it?

Secondly, I don't know why my SCORM unable to resume. Even though I have set prompt to resume at player setting. Do you know why? 

FYI, I have tested all version; 1.2, 2004 (2nd to 4th edition) but the problem persist. Resume popup does not appear in my LMS (SAP successfactor)

Thanks for your help. I attached my original manifest file for your review.

Thanks a lot!

Hello. I have the same problem. I'm inserting the code correctly (in my opinion) but it doesn't work. The buttons are still present.
Has anyone found a solution?

SAP help on this topic is here: 2188058 - Wrapper with additional buttons for SCORM 2004 content

Does this work for you? I added it according to the article, now whenever I import files into LMS it says "no valid files" seems XML is messed up... Can you share your manifest file for example?

I believe SAP broke it when they are working on the New Course Home page. I submitted a ticket with SAP, said it wasn't their problem.

The Launch button was creating an error, so I had to change the Launch URL string in the content object from launcher.html to index_lms.html and it worked ok. Not what the imsmanifest.xml file stated in the href.

Our IT team identified this issue: the SCORM package we exported from Rise no longer included the xmlns definition for adlnav. Therefore, the fix to both delete the terrible navigation button wrappers and make sure you don't get a content upload error that prevents you from uploading to SAP is this:

1. Export SCORM 2004 v. 4 file
2. unzip
3. open imsmanifest.xml file
4. edit as follows (using wordpad, not MS Word):
   1. Add the following text just below the SECOND <title> XXXXX </title>:
      
      

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

5. Check if the identifier xmlns:adlnav=”http://www.adlnet.org/xsd/adlnav_v1p3 is present. If not, add this exactly (include quotation marks at end) in the xmlns definitions:
   xmlns:adlnav="http://www.adlnet.org/xsd/adlnav_v1p3"
   notably, we add this just after the line that starts with xmlns:imiss=...
6. Save and rezip the file
7. Upload to SAP

*side note: this doesn't seem to be a change in the SAP software, but in what Articulate includes in the exported content package. Our IT department told us to follow up with Articulate to find out why this had changed.

I followed your instructions, but the file still failed in SAP LMS. 

Hi Carla,

Sorry to hear that you ran into this snag.

I recommend testing how your course behaves in SCORM Cloud to verify if the published package is fully functional. If your course works in SCORM Cloud, please reach out to the support team of SAP LMS to let them know that your course is not working properly when uploaded to their environment. 

This works 100% if you understand what is being said. Step 5 is where I suspect most people come apart. 

To do all of this, here's what you should do.

Take your published Rise 360 .zip file and extract it somewhere.

Go into the extracted folder, and open/edit your imsmanifest.xml file (I recommend using Notepad++, it's great for this)

There are 2 parts to solving this problem.

1. Adding the missing line to the top of your manifest file.
2. Adding the code to your manifest file that hides those annoying buttons.

For Part 1 you need to check the very top section of the manifest file. If you compare a manifest file from Storyline 360 output with that of a Rise 360 output you will see there are some lines missing, most importantly, the xmlns:adlnav line that enables the hiding of the elements that we are trying to achieve:

Thanks Heinrich!

Hello All, 

Would the provided steps also work for a Presenter file? I added the new code to the manifest file, but the LMS (SuccessFactors) rejected the file. I see that the adlnav file DOES exist at the top, so I am unsure why it didn't work. Presenter uses Articulate to publish the file, so it makes sense that the steps would be the same. But the manifest file looks a bit different, so perhaps it's not that simple. I would appreciate any help I can get. I've been successful to remove the wrapper buttons for both SL and RISE, so now I am trying to figure out this 3rd option for Presenter. Thank you! 

We are having the same issue with SuccessFactors. I even loaded the imsmanifest.xml file directly into the iContent server, but it didn't update the adlnav buttons.

I noticed there was a new adlnav_v1p3.xsd file within the SCORM root, which has the hidenav code, but I don't know how to get the imsmanifest.xml file to read the file or to execute the hide code.

here is the code found in the adlnav_v1p3.xsd file:

<?xml version = "1.0"?>
<xs:schema targetNamespace = "http://www.adlnet.org/xsd/adlnav_v1p3"
xmlns:xs = "http://www.w3.org/2001/XMLSchema"
xmlns = "http://www.adlnet.org/xsd/adlnav_v1p3"
elementFormDefault = "qualified"
version = "1.0">

<xs:annotation>
<xs:documentation>
This file represents the W3C XML Schema Language Binding of the ADL namespaced elements for navigation controls.
</xs:documentation>
</xs:annotation>

<!-- *********************** -->
<!-- ** Change History ** -->
<!-- *********************** -->
<xs:annotation>
<xs:documentation>
*************************************************************************
* Change History *
*************************************************************************
2003-18-09 Initial creation.
2004-23-01 Final edits in preparation for release
2005-06-06 Added new hideLMSUI vocabulary token suspendAll, exitAll,
and abandonAll
*************************************************************************
</xs:documentation>
</xs:annotation>

<xs:element name = "presentation" type = "presentationType"/>

<xs:element name = "navigationInterface" type = "navigationInterfaceType"/>

<xs:element name = "hideLMSUI" type = "hideLMSUIType"/>

<!-- Navigation Extension -->
<xs:complexType name = "presentationType">
<xs:sequence>
<xs:element ref = "navigationInterface" minOccurs = "0" maxOccurs = "1"/>
</xs:sequence>
</xs:complexType>

<xs:complexType name = "navigationInterfaceType">
<xs:sequence>
<xs:element ref = "hideLMSUI" minOccurs = "0" maxOccurs = "unbounded"/>
</xs:sequence>
</xs:complexType>

<xs:simpleType name = "hideLMSUIType">
<xs:restriction base = "xs:token">
<xs:enumeration value = "abandon"/>
<xs:enumeration value = "continue"/>
<xs:enumeration value = "exit"/>
<xs:enumeration value = "previous"/>
<xs:enumeration value = "suspendAll"/>
<xs:enumeration value = "exitAll"/>
<xs:enumeration value = "abandonAll"/>
</xs:restriction>
</xs:simpleType>

</xs:schema>

Thanks Melanie -this resolved our issue.  Like many others we're using SAP/SF LMS and we've decided to move our exams to a SCORM 2004 format.  Editing the manifest removes the buttons so that students aren't confused.