Forum Discussion
SuccessFactors LMS applying its own Navigational buttons
Hello,
When I publish Rise 360 to our SuccessFactors LMS it is applying navigational buttons that I do not want. I have been told by our LMS administrators this is normal behavior for SCORM 2004,...
For anyone looking for a solution, here you go.
To fix all of this, here's what you need to 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.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: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>
<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
Hi Heinrich,
I have edited the manifest file. After doing so, I receive a message that the SCORM packet includes invalid files. This does not happen if I don't edit the manifest file. Can you provide some insight into this?
I have noticed that my manifest files do not include the <adlcp:dataFromLMS> tag.
Hi DaphneDansby-41, if you were able to disable the navigation buttons in SF successfully without the error message (The Scorm package includes invalid files), please share your approach. Thanks!
