Reporting enhancement - dynamic user profile lookup
A new dynamic mode of user profile lookup has been added to the content activity report. Previously, user profile data included on the content activity report reflected a user's profile data at the time that the content activity occurred (i.e. at the time the reporting data was written to the reporting database, when for example a user started or completed a course). In some scenarios this is appropriate i.e. you want the reports to reflect the picture of the user's profile data at that historic point in time. In other scenarios however, you might want the report to reflect the user's current user profile properties. For example, their name may have changed if they married, their job role might have changed, their department might have changed, their group membership might have changed and so on.
The Report generator page for the content activity report now features a new PROFILE DATA selection field that contains two values: Current (the default) and Historic. When Current is selected, user profile data at the time the report is generated (i.e. now) is used. If Historic is selected, the user profile data at the time content was accessed (started or completed) is used.
Catalogue feed enhancement for offline curricula
The catalogue feed - as used by clients such as the Luminosity Mentor mobile Apps and the new Web learner portal (coming soon), has been extended to include the completion mode for curriculum entries. The completion mode determines how an individual content item within a curriculum should influence overall curriculum completion. Options include Must complete and Must pass. By providing this information to clients such as the mobile learning Apps, curriculum completion logic can now be computed in entirely offline scenarios, when no connectivity to the LMS is available.
Event and session UI and UX enhancements
A number of significant UI and UX improvements have been made to the administration portal to make it easier to manage events and sessions. These changes represent the 1st phase of a set of enhancements to event and session management to be rolled out over the current and subsequent releases. The main improvements in this release include making the UI for event and session management more consistent with other parts of the administration portal interface, and improving the way users are managed. For example, with the new powerful user filters added to the users lists associated with both events and individual sessions, it is now much easier to see who attended historic sessions, who is enrolled on forthcoming sessions, whose enrolment requests need processing and so on. Various default values, established when creating new sessions have also been changed, meaning there is now less data that typically needs to be edited while creating new sessions.
New /healthcheck page
A new health check page designed to aid problem diagnosis has been added to the LMS. This can be accessed at any time by appending /healthcheck to the primary LMS address. For example, to access the health check page for an LMS located at https://customername.lumo-reach.com, the page address would be https://customername.lumo-reach.com/healthcheck. The purpose of this page is to display the status of the connections to other dependent services such as the Experience API Learning Record Store (LRS) and User Directory Service (UserDS) and to display the client's browser details. This information is very useful to first line support personnel when troubleshooting issues reported by LMS users.
Simplification of "Completed" and "Viewed" status display strings
The LMS previously displayed "Completed" for courses, but "Viewed" for arbitrary files such as PDF documents, videos, Office documents and so on. This has caused some confusion with users, as they are not sure whether an item in the "Viewed" state has just been looked at and not completed, or whether the item has been completed. To resolve this potential source of confusion, the use of "Viewed" in both the Learner and Admin portals has been changed to "Completed". Before a file has been accessed the status now displays as "Not attempted" (rather than "Not viewed"). After an item has been accessed, the status now displays as "Completed" (rather than "Viewed"). Note that this change only applies to arbitrary files and brings consistency with courses. The display strings for status codes associated with SCORM and Experience API courses has not changed. These will say "Not Attempted", "Attempted" and "Completed" (which can be changed by the LMS to "Passed" or "Failed" if a mastery score is associated with the course). Unlike arbitrary files, the initial completion status for course content is driven by the content itself rather than by the LMS or Apps.
Various bug fixes
Various bug fixes.