Improvements
Learner Audit Logs - Appraisal Due Date Changes
We’ve updated the learner audit logs in Flow to capture when a user changes the due date of a learner’s appraisal. The log now shows the date the change was made, the appraisal name, the user who made the change, and both the old and new due dates.
Why this Matters
Previously, there was no visibility when a due date was changed, making it difficult to track adjustments or investigate issues. This update adds transparency to the appraisal process by recording date changes directly in the learner audit logs.
Key Benefits
- Improved transparency: Shows when and by whom appraisal due dates were updated.
- Reduced support tickets: MS users can now self-serve by checking the audit log instead of contacting Support.
Stronger audit trail: Increases accountability and makes it easier to trace changes in appraisal activity.
Learner Audit Logs - Appraisal Reviewer Changes
The learner audit logs now capture when a user changes the reviewer on a learner's appraisal. The date of the change, the name of the appraisal, the user who made the change, and both the old and new reviewer names are now recorded.
Why this Matters
Previously, there was no visibility when a reviewer was changed, making it difficult to track adjustments or investigate issues. This update adds transparency to the appraisal process by recording reviewer changes directly in the learner audit logs.
Key Benefits
- Stronger audit trail: Increases accountability and provides a clear history of reviewer changes.
- Improved transparency: Makes it easy to see when and by whom appraisal reviewers were updated.
- Greater independence for MS users: Teams can self-serve and access this information directly in Flow, without needing to contact Support.
Bug fixes
- Unable to Add Thumbnails/Certificates Without Replacing SCORM File
- We fixed an issue that prevented users from updating thumbnails or certificates on SCORM files without reuploading the SCORM package. These elements can now be uploaded independently.
- Inactive User Updates Not Reflected in Flow
- We resolved a bug where updates made to inactive users in MOS were not processed in Flow. These updates, often used to anonymise leaver data, are now handled correctly.