Forum Discussion
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?
31 Replies
- suzannemeyerCommunity Member
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>- AndrewBlemingsCommunity Member
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.
- VeljkoRoskarCommunity Member
SAP help on this topic is here: 2188058 - Wrapper with additional buttons for SCORM 2004 content
- IzzuddinShuib-eCommunity Member
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!
- ChristDCommunity Member
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? - MarcusGriesb553Community Member
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.
- MelanieBrooksCommunity Member
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>
- Add the following text just below the SECOND <title> XXXXX </title>:
- 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.
- HeinrichBart602Community Member
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: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.xsdhttp://www.adlnet.org/xsd/adlcp_v1p3 adlcp_v1p3.xsdhttp://www.adlnet.org/xsd/adlseq_v1p3 adlseq_v1p3.xsdhttp://www.adlnet.org/xsd/adlnav_v1p3 adlnav_v1p3.xsdhttp://www.imsglobal.org/xsd/imsss imsss_v1p0.xsdhttp://ltsc.ieee.org/xsd/LOM lom.xsd">Rise 360<?xml version="1.0" standalone="no" ?><manifest identifier="wpwUr_cb_De7M3C2CYMXohGJzRe6cts1KGHj0ATy" version="1.3"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"MISSINGxmlns:imsss="http://www.imsglobal.org/xsd/imsss"xsi:schemaLocation="http://www.imsglobal.org/xsd/imscp_v1p1 imscp_v1p1.xsdhttp://www.adlnet.org/xsd/adlcp_v1p3 adlcp_v1p3.xsdhttp://www.adlnet.org/xsd/adlseq_v1p3 adlseq_v1p3.xsdhttp://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 Part1Now 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- MelanieBrooksCommunity Member
Thanks Heinrich!
- DonnaFreemanCommunity Member
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.
- CarlaRavazzzanoCommunity Member
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.
- SilviaMilano463Community Member
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!
- MarcusGriesb553Community Member
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>
- JakubForejt-066Community Member
Thanks to all for contribution to this thread! We are still having issue with SF navigation bar too. Strangely enough, Storyline contents have the buttons hidden without any intervention into xml files. Blank navigation bar is still displayed though.
With Rise contents, no matter what we adjust in imsmanifest.xml, the buttons are still present. We applied all the suggestions from this thread with no success in SuccessFactors :-)- CarlaRavazzzanoCommunity Member
- MelanieBrooksCommunity Member
I can't see the previous threads, but we have the same setup (Rise, SF), and this is the code we input into the manifest file. It works consistently for us to totally remove the buttons and ensure there is not an upload error.
- Check if the identifier “xmlns:adlnav= "http://www.adlnet.org/xsd/adlnav_v1p3" is part of the manifest. If not, add it.
If missing, add this:
xmlns:adlnav="http://www.adlnet.org/xsd/adlnav_v1p3"
- Next, 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>
Related Content
- 11 months ago
- 10 months ago