Curriculum completion status handling improvements
The LMS has been updated to ensure that the curriculum status for users is consistent in the administration portal and in the reports. After a user achieves a completed state, they will not automatically move back to an incomplete state, even if the curriculum definition changes, or their status for one of the courses in the curriculum changes.
Typically, a user will go through the curriculum statuses, Not Started > In Progress > Completed/Passed/Failed, so a user in the In Progress state will not move back to Not Started, nor will a user in the Completed state go back to either In Progress or Not Started automatically.
With this update, the status displayed in the administration portal matches the status shown in reports.
This new approach to managing completion for curricula enables the addition of a new feature, where the administrator can directly set the status of a curriculum for a user as Complete (optionally with a score), in the administration portal. This enables an Administrator to mark a user as complete, regardless of if they have completed all (or any) of the mandatory items within the curriculum.
To support scenarios where a user needs to move back to an incomplete status where a curriculum definition changes, e.g. from Completed to In Progress, we have also provided the ability for an administrator (on a per user basis), to recalculate the completion state for a curriculum. Where an administrator chooses to update the completion state of a curriculum for a user (by recalculating the user's completion status based on the current content within the curriculum), if the user moves from Completed to a previous state, the reports will also be updated to match this status. This ensures that the administration portal and the reports remain consistent.
Note that a further phase of the curricula updates will involve updates to the Apps and learner portals to match the behaviour described above.
The SSO functionality of the administration portal has been enhanced to (optionally) allow the automatic logout from an upstream Identity Provider (IdP), when logging out of the Admin portal. This option is only available where supported by the third-party IdP. Global administrators can see this in the Settings area of the Admin portal, but can only be configured by Agylia. Please contact Support, if you would like this feature enabled.
Various bug fixes.