Significantly improve performance of report generation. Large reports will now generate much faster. However, it can still sometimes take hours to generate large reports due to the use of cached data in this report.
Add columns for course start date and course completion date.
Score and progress percentages are now rounded to two decimal places.
Total time and dates are now rounded to the nearest second.
Remove organization columns. This was redundant information since the organization is the same for all rows in this report and the organization name is in the report’s filename.
Bug Fixes
All Enrollments report:
The following changes have been made to prevent our reporting system from being unnecessarily backlogged by large All Enrollments reports.
Reports that are exported and sent via email are processed using a first-in, first-out queue. When the system is backlogged, it means there is a large amount of reports in the queue that the system is working through. This causes reports to be delayed longer than normal until everything in the queue has been processed.
There is now a limit of one All Enrollments report queued at a time per organization. Once a user exports an All Enrollments report, another one cannot be exported for their organization until the first report has finished generating and has been sent.
The All Enrollments report has been moved to its own queue separate from all other types of reports. A backlog of All Enrollments reports will no longer cause other reports to be delayed. (This was deployed on July 5th.)
Fix the number of hours in the total time not being displayed by default in Excel.
Fix minor formatting inconsistencies (column naming, “%” sign missing for scores and progress).
Fix inconsistent sorting of rows when different users or courses have the same name.
SCORM courses:
The following changes address specific SCORM 1.2 compliance issues with our LMS. In general, these resolve issues or errors with modules that rely on specific functionality of the SCORM data model and runtime environment.
Fix the lesson location (cmi.core.lesson_location) always being an empty string instead of the value that was previously set by the module. This could have caused issues like modules not resuming to the correct slide.
The entry status (cmi.core.entry) is now set as required based on the module’s exit status (cmi.core.exit) when a user ends a session with the module. If the exit status is “suspend”, then the entry status is set to “resume”. Otherwise, the entry status is set to an empty string. This could have caused issues like modules not resuming at all.
The total time spent in the module (cmi.core.total_time) is now updated as required when a user ends a session with the module. The session time (cmi.core.session_time) recorded by the module during the session is now added to the total time when the session ends.
Fix timespan values (cmi.core.total_time and cmi.student_data.max_time_allowed) not being in a compliant format when read from the data model. They were objects instead of “HHHH:MM:SS.SS” strings.
Fix the seconds portion of time and timespan values (cmi.core.session_time, cmi.interactions.n.time, and cmi.interactions.n.latency) not being parsed correctly, causing them to be saved with a value that was off by a fraction of a second.
Fix SCORM API functions returning “true” instead of an appropriate error code when a back-end error occurs. This could happen when calling LMSGetValue or LMSSetValue with an unsupported attribute name, or calling LMSGetErrorString with an unknown error code.
Fix LMSGetLastError sometimes returning the error code as a number-type value instead of a string-type value.
Reduce the likelihood of end-of-session SCORM API calls being dropped when a user navigates away from a module (such as returning to the course list).
Virtual classes:
Fix a recurring issue that would cause webcams and screen sharing to stop working. (This was deployed on July 5th.)
Fix screen sharing not working when using Firefox (“permission wasn’t granted” error).
