The Open LMS Product team is happy to announce the release of WORK 3.3.0:
- Sandbox upgrade on Tuesday, October 22, 2024
- Production upgrade on Wednesday, November 6, 2024
Upgrade to Core 4.3.8
As part of this release, the team reviewed the code of 4.3.8 and upgraded the underlying systems, adding the corresponding fixes, improvements, and security patches.
Release Notes
For the full release notes from https://moodledev.io, please click on the following links:
4.3.8 Release Notes
4.3.7 Release Notes
New and Updated WORK Features
- New option to import custom notifications from one program into another
- Added the ability to display Program and Certification custom fields on certificates
- Added new indicators for problems with program content, such as when a course has been deleted
- Added new options for sending Program and Certification notifications to a user's related user
- Added a new option to reset course progress on a per-user basis for all content in a program, similar to how the recertification reset works
- Added a new option to export and import programs, including their contents and structure
- When setting up a User Development Plan (UDP) framework there’s a new option, "Use program default dates". When set to ‘yes’, the program defaults will be applied instead of using the UDP start and related dates. Changing this setting is not retroactive. Once this is set to ‘yes’, the change will apply to new assignments only.
- Added a new setting for User Development Plans to control the sort order of the priority field. The new options are Descending (a higher number has a higher priority) or Ascending (the lower the number, the higher the priority).
Bug Fixes and Minor Enhancements
Open Reports Engine
- Fixed a bug where reports that historically had export options would show as available to schedule for email delivery even if the export options had later been removed. Now if the export options on an existing report are all disabled, the report shall be removed from the available list.
- If export options are disabled at the site level, sometimes those options would still display on some report configuration pages. This has been corrected.
- Fixed a bug where you could not change the visibility status on a shared saved search. You can now change the visibility back to private from public, if needed.
- Resolved an issue with reporting finish time when using the Question attempts report source that could prevent the report from displaying correctly.
- When using the ‘Restrict access by user’ option in the ‘Access’ tab of reports, you could disable the option, but the previously selected users still displayed. This display error has now been fixed.
- Attempting to filter a report using the Attendance report source would trigger an SQL error and prevent the report from displaying. This has been corrected.
- When using the Attendance report source, if a user in the course had been unenrolled after some attendance statuses were set the report would display an error instead of the appropriate data. This has been fixed.
- Reports created using the course modules report source will now include users enrolled via User Development Plans.
- Several report sources supported restricting the content displayed to only the information related to courses the viewer was enrolled in. This did not work consistently and sometimes caused visual errors when used. This has been addressed, so the data should now display correctly.
Other enhancements and bug fixes
- Previously when you deleted an archived tenant from the tenant main view, an error was displayed. This is resolved and the user will now be returned to the tenant overview page.
- User development plan frameworks would sometimes display the wrong type when updating a framework setting, such as displaying as an ‘Assigned plan’ type instead of a ‘Requested plan’ type. This was only a visual error, but it has been corrected.
- Added an internal check to confirm, if multi-tenancy is enabled, that the expected roles all exist. If they’re deleted, the system will automatically recreate them. The system will now prevent deletion if multi-tenancy is enabled.
- When a taxonomy custom user field was required a user could not update their own value, so they would be stuck on their profile field update page, unable to navigate away. This has been resolved, so the field can be required and updated by the end user.
- Added several new community and vendor plugins. The available plugins can be reviewed by visiting our Plugin Matrix.
Comments
0 comments
Article is closed for comments.