Invalid "Condition: Expiration by lapse time"

This check verifies if any of the courses have an invalid expiration date. For the purpose of this check, a date is considered “invalid” if the course uses the “Condition: Expiration by lapse time” and the value is greater than 3650 (e.g. 10 years).

Issue

HCE 4.1.10.4 adds a “Certification and expiration” section to the course’s settings. This section replaces the “Condition: Expiration by lapse time” and “Condition: Expiration by date” sections found in the course completion settings in HCE 4.1.10.3 and earlier.

As part of the upgrade to HCE 4.1.10.4, the system migrates all values from the old “Condition: Expiration…” sections to this new “Certification and expiration” section. However, during our quality assurance process, Dual Code noticed that some instructors have set expiration values that far exceed 10 years. Some clients have courses expiring in 30,000 years, which is clearly a misconfiguration.

This System Health check looks for any course with an expiration value greater than 10 years. If a course that expires in >10 years is detected, the system sends an email to all administrators asking them to set a valid value and given them at least 30 days notice. If the value is not fixed prior to the HCE 4.1.10.4 upgrade, the expiration date will simply be deleted when the upgrade takes place, thereby turning the course into a once in a lifetime course.

Note that this will not impact any previously issued learning records. This change only impacts learners who complete the course in the future. Going forward, if a user receives a learning record, their record will not have an expiration date unless that expiration date is <10 years.

Best Practice

As a best practice, a course should either (a) never expire or (b) expire in a reasonable amount of time, where “reasonable” is considered to be 10 years or less. The new “Certification and expiration” section available in HCE 4.1.10.4 enforces this best practice.

Open