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?

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: Export SCORM 2004 v. 4 file unzip open imsmanifest.xml file edit as follows (using wordpad, not MS Word): 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> 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=... Save and rezip the file 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.

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>

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.

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.

SCORM Wrapper | Articulate

MelanieBrooks
Community Member
2 years ago
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:

Export SCORM 2004 v. 4 file

unzip

open imsmanifest.xml file

edit as follows (using wordpad, not MS Word):

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>

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=...

Save and rezip the file

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.
- HeinrichBart602
  Community Member
  12 months ago
  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.
  
  Adding the missing line to the top of your manifest file.
  
  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:
  
  Storyline 360
  
  <?xml version="1.0" encoding="utf-8" standalone="no"?>
  
  <manifest identifier="wpwUr_cb_De7M3C2CYMXohGJzRe6cts1KGHj0ATy" version="1.3"
  
  xmlns="http://www.imsglobal.org/xsd/imscp_v1p1"
  
  xmlns:adlcp="http://www.adlnet.org/xsd/adlcp_v1p3"
  
  xmlns:adlseq="http://www.adlnet.org/xsd/adlseq_v1p3"
  
  xmlns:adlnav="http://www.adlnet.org/xsd/adlnav_v1p3"
  
  xmlns:imsss="http://www.imsglobal.org/xsd/imsss"
  
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  
  xmlns:lom="http://ltsc.ieee.org/xsd/LOM"
  
  xsi:schemaLocation="http://www.imsglobal.org/xsd/imscp_v1p1 imscp_v1p1.xsd
  
  http://www.adlnet.org/xsd/adlcp_v1p3 adlcp_v1p3.xsd
  
  http://www.adlnet.org/xsd/adlseq_v1p3 adlseq_v1p3.xsd
  
  http://www.adlnet.org/xsd/adlnav_v1p3 adlnav_v1p3.xsd
  
  http://www.imsglobal.org/xsd/imsss imsss_v1p0.xsd
  
  http://ltsc.ieee.org/xsd/LOM lom.xsd">
  
  Rise 360
  
  <?xml version="1.0" standalone="no" ?>
  
  <manifest identifier="wpwUr_cb_De7M3C2CYMXohGJzRe6cts1KGHj0ATy" version="1.3"
  
  xmlns="http://www.imsglobal.org/xsd/imscp_v1p1"
  
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  
  xmlns:adlcp="http://www.adlnet.org/xsd/adlcp_v1p3"
  
  xmlns:adlseq="http://www.adlnet.org/xsd/adlseq_v1p3"
  
  MISSING
  
  xmlns:imsss="http://www.imsglobal.org/xsd/imsss"
  
  xsi:schemaLocation="http://www.imsglobal.org/xsd/imscp_v1p1 imscp_v1p1.xsd
  
  http://www.adlnet.org/xsd/adlcp_v1p3 adlcp_v1p3.xsd
  
  http://www.adlnet.org/xsd/adlseq_v1p3 adlseq_v1p3.xsd
  
  http://www.imsglobal.org/xsd/imsss imsss_v1p0.xsd">
  
  What you need to do is add that missing line (bolded) into your manifest file.
  
  That takes care of Part1
  
  Now you can add the hideLMSUI elements which then forces the LMS to hide those annoying buttons that appear in LMSs like SuccessFactors.
  
  Add the following code under the second <title> row of your Manifest file (In-between the 2nd <title> tag and the <adlcp:dataFromLMS> tag
  
  <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>
  
  Once this is done, save the manifest file, and rezip all the contents of the folder back into a .zip file.
  
  Import this "updated" zip file into your SuccessFactors LMS and it should work.
  
  Attached is a fixed example of a Rise 360 manifest file.
  
  Hope this helps anyone else struggling with this!
  
  H
  imsmanifest.xml7 KB
  - MelanieBrooks
    Community Member
    12 months ago
    Thanks Heinrich!
- DonnaFreeman
  Community Member
  9 months ago
  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.
suzannemeyer
Community Member
6 years ago
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>
- AndrewBlemings
  Community Member
  6 years ago
  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.
  - VeljkoRoskar
    Community Member
    3 years ago
    SAP help on this topic is here: 2188058 - Wrapper with additional buttons for SCORM 2004 content
SteveFlowers
Community Member
11 years ago

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.
PhillipLoughlin
Community Member
11 years ago

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!
SteveFlowers
Community Member
11 years ago

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.
PhillipLoughlin
Community Member
11 years ago

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.
KatyStruck
Community Member
10 years ago
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!
AshleyT-Pollard
Staff
10 years ago
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.
jakobGravesen
Community Member
10 years ago
Hi Katy and Ashley

I am in the same situation..., any great solutions here?
RaymondWan
Community Member
10 years ago
Same....upload our scorm package and we have the banner/wrapper show up with the 3 buttons...

Can this be removed completely?