If you want change the SCORM Settings go to:
- the Management Panel and click on Assets (SmarterPath for Jive)
- the Management Panel and click on SCORM/TinCan (SmarterPath for Office 365)
In order to see the SCORM Settings click on the Settings symbol on the right of the respective SCORM you want to edit.
1. Edit – Changes of the following information can be made:
- Asset Name
- Asset Description
- Asset Objectives
- Timing (when a participant is able to mark a step as completed - only useful if your SCORM doesn´t have a completion value set up)
2. Manage owners – you can select Owners of the SCORM. Only owners of the SCORM and SmarterPath Admins have access to edit this SCORM.
3. Upload SCORM – you can upload a new version of your SCORM file. (IMPORTANT: Adjust the versioning behaviour (find below) suggestion: "Always"!)
4. Preview – you can check out a preview of your SCORM.
5. Edit properties (settings are handled by our 3rd party SCORM provider) – Changes of the following information can be made:
(SCORM Cloud Course Properties *Not all course properties will apply across specifications)
NAVIGATIONAL CONTROLS | |
Navigation Bar | Should the player show the navigation bar containing the navigation buttons? |
Show Finish Button | Should the player show the Return to LMS button? |
Show Close SCO Button | Should the player show the Close Item button? |
Show Progress Bar | Should the player show the progress bar during course delivery? |
Use Measure For Progress Bar | Use Measure For Progress Bar – Determines if the progress bar state should be calculated from the progress measure rollup or from SCO completion *only applies to SCORM 2004 4th ed. |
Show Title Bar | Should the player show the title bar? |
Prevent Right Click | Should the player prevent users from right clicking in its navigation frames? |
Show Course Structure | Should the player show the course tree structure during delivery? |
Course Structure Starts with Open | If the course structure is displayed, should it default to being open or closed? |
Course Structure Width | If the course structure is displayed, how many pixels should be allocated for it? |
Structure Status Display | Determines how icons are displayed to indicate success and completion. Five Values |
Invalid Menu Item Action | Defines how to handle menu item links that won't succeed (show, hide or disable). |
LAUNCH BEHAVIOR | |
SCO Launch Type | New Window (default) or Frameset |
Player Launch Type | New Window (default) or Frameset (Default) |
New Window Options | Full Screen or you can specify dimensions with a few options on how to handle the resizing |
Time Limit | Maximum length of time a user can spend taking a course |
COMPATIBILITY SETTINGS | |
Finish Causes Immediate Commit | Will force the player to immediately persist data to the server when the SCO calls Finish/Terminate rather than waiting for the next periodic commit. Useful for SCOs that only save data on unload and require the player to be launched in a new window. |
Logout Causes Player Exit | Should the player allow a cmi.exit request of logout to exit the entire player |
Wrap SCO Window with API | Will put an API relay object in a frameset around a SCO that is launched in a new window. This is useful for SCOs that incorrectly use the ADL API Finder algorithm from spawned windows. |
Always Flow to First SCO | Should the player always launch the first SCO when the course is launched regardless of sequencing rules. |
Enable Validation of SCORM Interaction Results | Determines whether the format of SCORM responses are validated client-side |
Raw Score Can Act As Scaled Score | For SCORM 2004, if SCO sets a raw score but not a scaled score, determines if the raw score should count as the normative score for the SCO |
rollupEmptySetToUnknown | For 2004 courses, determines the rollup status when no child activites contribute to the rollup. When true, completion and statisfaction remain unknown |
lookaheadSequencerMode | Determines if or how lookahead sequencer is enabled client-side. |
resetRunTimeDataTiming | Should the player always persist runtime data when the exit type is suspend, or should this be left up to the sequencer? |
Return to LMS Action | In response to the SCORM 2004 4th edition that allows learners to choose their exit type when leaving a course, our Engine now has a menu prompt when the learner clicks "Return to LMS" |
Maximum Suspend Data Size | Maximum length of suspend data to save. SCORM 1.2 default is 4096 characters and SCORM 2004 is 64000 characters |
SCORM 2004 Edition | This is a SCORM 2004 only setting that allows the edition of the SCORM 2004 api to be changed. Use with caution |
Internet Compatibility Mode | Renders an X-UA-Compatible Meta Tag in the deliver frameset, api wrapper frameset, and intermediate page which can dictate the way content in child frames render for IE browsers. |
Disable Root Activity | Forces the root level course activity to be disabled to prevent creating a new attempt |
Rollup at SCO Unload | Forces rollup at all SCO unloads to handle when Terminate/LMS Finish is not called by the SCO |
Override Objective and Completion Status Set By Content to True | The default settings for SCORM 2004 sequencing can sometimes lead to a SCO being automatically being completed and satisfied if the SCO doesn't report appropriate run time data. This setting will override that bahavior. |
Invoke Rollup at Suspend All | Causes rollup at suspend all request |
Statisfaction causes completion | Sets any activity as completed when it's satisfied |
Make Student Preferences Global to Course | Causes any preferences set by a student to be applied to all SCOs |
COMMUNICATION SETTINGS | |
Max Failed Attempts | Determines the maximum number of attempts to try a runtime data update to the central server bfore declaring failure |
Commit Frequency | Determines how often, in miliseconds, runtime data sends updates back to the central server. |
DEBUGGER OPTIONS | |
Control | Determines the level of logging that should be performed with the control subsystem on the client |
Runtime | Determines the level of logging that should be performed with the runtime subsystem on the client |
Sequencing | Determines the level of logging that should be performed with the sequencing subsystem on the client. |
Look-ahead | Determines the level of logging that should be performed with the sequencing:look-ahead subsystem on the client. |
Include Time Stamps | Should timestamps be included |
HISTORY OPTIONS | |
Capture History | Determines if the course should send back information on each attempt |
Capture Detailed History | Determines if the course should send back detailed information on each attempt |
6. Edit versioning behaviour (settings are handled by our 3rd party SCORM provider) – you can select the following versioning behaviour for Participants:
- Never – keep existing registrations on the old version (the default)
- If Incomplete – if a registration is marked incomplete (or unknown)
- When Completed – if a registration is marked complete
- When Failed – if a registration is marked complete and failed
- When Passed – if a registration is marked complete and passed
- Always – always move to the latest version
7. Delete – if you do not need the SCORM anymore, you can delete it