The release notes provide information on the features and improvements in the specified version. The release dates that are related to the version of the release are published in the Curriculum/Workload Management release schedule.
Improvements
The issues in release mentioned under the section improvements are considered as new functionality, user experience improvements or bug fixes. Issues marked as Hotfix have been developed during this Sprint release, but are hotfixed and technically added to the previous release or direct to production based on the impact of the issue.
Staff no longer assigned to a module relation or activity should not be in the workload report - CUR-3345
When a teacher is removed from activities or the relations pages, the user still shows in the Workload report. A change is applied to no longer show the removed staff in the workload report and only show the current related staff members in the report.
Changing offering start and end time of should not confuse users - CUR-3673 (Hotfix)
When changing the start date of an offering, the correct date was saved, but the field was shown in it's initial state (default to the grey 10:00 as input help). This of course confuses the users. A fix is applied and the date is now both save and displayed correct.
As and administrator I should be able to define a new team - CUR-3551
The option to define a new team was no longer visible/available in the team management page for administrators. The button is added, and new teams can be created again.
The create module authorisation should be respected - CUR-3668
The create module option should be shown in case a user has the authorisation CREATE_MODULE. There was one case where the authorisation was not handled correctly. If it wat defined at a faculty role, the authorisation was ignored and the add module button was not shown. This is fixed and the create module option now follows the authorisation rule on each level.
The subtype of entity type custom-fields should be editable - CUR-3714
The subtype of a custom-field of type entity was not always editable. This to prevent administrator to accidentally select another subtype for fields that are bound to specific functionality. E.g. change the studyId entity from Study to Module would have a massive impact. Based on requests, the option to change the subtype has been added. Just be careful and remember 'with great power, comes great responsibility'.
Integration
The issues mentioned under the section integration are considered as extension, improvements or bug fixes related to the Curriculum API, OOAPI and/or CSV import functionality.
The module endpoint should provide custom-fields defined for ad-hoc offerings - CUR-3661
The module endpoint didn't correctly return the custom-fields defined for ad-hoc offerings. This has been fixed and custom-fields are available in the JSON output.
Security
An integral part of our development and build process is automatic scanning for known security vulnerabilities. The vulnerabilities will be fixed based on their impact, which means that in some cases an immediate hot-fix will be applied, and in other cases the vulnerability will be fixed in the current or next Sprint (release). The security section provides an overview of the vulnerabilities mitigated. For more information on reported vulnerabilities, see the central database of vulnerabilities.
In this version no vulnerabilities needed to be addressed.
Refer to the Workload Management manual for configuration guidance.