dominKnow | ONE projects have two different end screen options available that can be automatically added into the learner’s content flow:
- Module End Screens
- Project End Screens
dominKnow | ONE projects have two different end screen options available that can be automatically added into the learner’s content flow:
Module end screens serve two potential purposes:
Project end screens also serve two potential purposes:
There are default end screens for both Module and Project end screens, plus authors can make their own custom Module and Project end screens.
The Publishing Profile has several settings that control or alter what the end screens show.
Both the Module and Project end screens are affected by:
The Project End Screen is affected by:
The Module End Screen is affected by several Publishing Profile settings, these effects depend on whether the Module End Screen is being shown as Content Summary or as a Test Summary:
Content Summary Mode | Test Summary Mode | |
---|---|---|
Display Learning Object Test Summary – Shows a break down by Learning Object for the learner’s completion/test results | Yes | Yes |
Pre-Test Review – Controls whether the learner is allowed to review their pre-test results (if given a pre-test) | No | Yes |
Post-test Additional Attempts – controls how many re-attempts the learner has for the test. The default setting is 5, which means the learner has 6 attempts in total. | No | Yes |
Post-test Review - Controls whether the learner is allowed to review their post-test results | No | Yes |
Skip Module End Screens Setting in Publishing Profile
This setting is different than the other settings in that it doesn’t affect what the Module End Screen displays.
It affects whether or not the Module end Screen is shown to the learner as a Summary/navigation screen after completing Module content.
If it is turned on, the learner will not see the module end screen when they complete the learning content in a module.
This setting has the most impact on the learner experience in projects that have more than one module. More on this below.
Let’s walk through some examples of how and when Module and Project end screens are shown to the learner.
One Module of Content with Test Questions
If the Project has only one Module and has test questions:
*If they choose Continue instead, they are shown the Project End Screen which also has a Take Test button.
One Module of Content with Test Questions and Skip Module End Screens Setting is On in Publishing Profile
If the Project has only one Module and has test questions and this setting is turned on:
Whether the Skip Module End Screens setting is on or off, for a one-module project with a test the learner is experience is pretty much the same.
You may prefer to turn this setting on if you feel the Project End Screen is better or sufficient to show the learner after the module content is completed.
More Than One Module of Content with Test Questions For Each Module
If the Project has, for example, two Modules and each Module has test questions:
*If they choose Continue instead, they are taken to the learning content for Module 2 (skipping the Module 1 test)
** If they choose Continue instead, they are taken to the Project End Screen which has Take Test buttons for each module
More Than One Module of Content with Test Questions For Each Module and Skip Module End Screens Setting is On in Publishing Profile
If the Project has, for example, two Modules and each Module has test questions:
For Projects that have more than one Module and testing for each or several modules, the Skip Module End Screens is essentially how you can control whether the learner can take a Module Test after completing the module content or they take all testing after completing the content in all Modules.
You can create your own Custom endscreens to use instead of the default end screens.
These can be created from the Project >> Master pages tab.
You can start with a template or create from scratch.
You can use system variables to display your choice of information to your learner.
NOTE: The default end screens do have features that cannot be replicated in a custom end screen, such as breaking down completion and test on a per-Learning Object basis.
For some audiences or learning contexts the end screens may provide more complexity than you need.
To simplify the test-launch process you can add a Take Test button to the Conclusion or last page in your Project or module. When they arrive at that last page the learner can select the button and immediately begin the test, no need to proceed to the end screen to access its Take Test button.
Tip: Disabling the Next button on that last page will prevent the learner from accidentally advancing to the end screen.
The learner will still see the end screen as a test summary after completing the test.
This article has more details on this option.
Comments ( 0 )
Sign in to join the discussion.