| Panel | |||||
|---|---|---|---|---|---|
| |||||
On this page:
Sub-pages:
|
...
The details captured for each course may vary slightly between each system configuration. Fields marked with * are mandatory
Definition of Fields
| Name | Enter a name for the course It is recommended an internally developed set of naming conventions are followed | |||||
|---|---|---|---|---|---|---|
| Description | Enter a description for the course This is the first description end-users will see and should contain an overview of what to expect within the course such as time required to complete, expected objectives etc | |||||
Valid For Number of months until a record expires | If the course has an expiry time frame, enter the validity period in months. For example, if the course expires after two years, enter '24' Courses will become available to the end user for recompletion 30 days prior to the expiry date.
| |||||
| Capability | If the course is required to be completed in Lucidity Competency, it must be linked to a capability. Select the relevant capability from the list. It is recommended the capability name is the same as the course name to prevent confusion. Refer to the Capabilities page within the Lucidity Competency user guide for more information. | |||||
Disabled Disabled courses are not available for users to complete | If a course is not required to be completed again, it can be marked as disabled. When ticked, a replacement course can be selected
The disabled course is available for administrators to manage and view completion records but cannot be completed by end-users. Any completion records will not be affected. If a replacement course is selected, users who has yet to complete the course will now need to complete the replacement course instead. | |||||
| Course Groups | If the course is to be part of a course group and completed by self-registered users, it can be linked by selecting the course group from the list. Refer to the Course Group page in this user guide for more details |
...
- Locate the specific course using relevant filters
- Click 'Actions' to the far right of the course
- Click 'Delete'
- In the pop-up that appears, click 'Delete' to completely delete the course from the system
| Warning | ||
|---|---|---|
| ||
Deleting a course cannot be undone - always use the delete function with caution. Any courses deleted in error will need to be recreated. All records associated with the course in Lucidity Induction won't be deleted but they will no longer be associated with a course and therefore have no course name listed. It is recommended old courses are archived rather than deleted, unless a course was made in error. Records in Lucidity Competency WILL NOT be deleted but will no longer be linked to an Induction course. |
Reporting from the Courses Page
...
The details captured for each module may vary slightly between each system configuration. Fields marked with * are mandatory
Definition of Fields
| Details - Name | Enter a name for the module If there is only a single module, it is recommended the module name is the same as the course name to prevent confusion. It is recommended an internally developed set of naming conventions are followed |
|---|---|
| Details - Description | Enter a description for the module This is the second description end-users will see and should contain brief instructions on how to complete the module, such as 'click start to continue' |
| Resources | See the Resources page of this user guide |
| Assessment | See the Assessments page of this user guide |
...
| Warning | ||
|---|---|---|
| ||
Deleting a module cannot be undone - always use the delete function with caution. Any modules deleted in error will need to be recreated. All resources and assessment within the module will also be deleted but records associated with the overarching course will NOT be deleted. |
Sorting Modules
The order modules appears to users can be changed by administrators.
...
TESTING ELEARNING COURSES
| Tip | ||
|---|---|---|
| ||
Lucidity Induction: Testing eLearning Courses |
Once eLearning courses are completely built, it is recommended they are fully tested from an end-user point of view to ensure they play as expected.
The resources themselves can be viewed from within the edit screen of a module but it is still important to test the full process in the same way an end user will.
Testing can be conducted in Lucidity Induction OR Lucidity Competency, depending on the site configuration, modules being used and tester knowledge.
...