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
New functionality, user experience improvements and bug fixes. Issues marked as Hotfix were developed in this sprint but applied to the previous release or directly to production, depending on impact.
Calculated fields no longer skip values after an empty field - CUR-4235
A field defined by a formula using a calculation (e.g. sum) several fields could store a wrong total when one of those fields was empty. Every value after the empty field was left out, so a report could show a different value than the form. This has been fixed, and an empty field now counts as 0 wherever it appears in the formula.
Needs action: stored values are not corrected automatically.
Fields set to generate Always or On save are corrected the next time the object is saved. For other fields, the advise is to run the Generate value hook after the release.
The hook has been extended with support for fields on relations, and can accept multiple fields to be regenerated by separating the fields by commas.
Ignored offerings are left out of activities and planning - CUR-4344
Offerings marked Ignore no longer appear where activities and teachers are collected per offering in the activity list, grid and card, the teacher pages, the reservation list and the activity groups page.
Ad hoc offerings should follow the defined ad-hoc code pattern - CUR-4200
The automated code generation based on a formula for ad hoc offerings was using the defined pattern for the standard offerings. This has been fixed, and the generated code A pattern configured on the ad hoc offering type therefore had no effect in the structure view or in the offerings on the general tab of a module. This has been fixed, and ad hoc offerings use their own pattern there and on the planboard. A name entered on an offering still takes precedence over the pattern, now on the planboard as well.
Integration
Extensions, improvements and fixes to the integrations: the Curriculum API, OOAPI, CSV import, and the data exchange with Data Manager, Core and the broker.
Bulk import endpoints accept up to 100 objects - CUR-4338
The bulk import endpoint implemented in a previous release was limited to 25 objects. This has been altered and it will accept up to 100 objects per request. See developer.timeedit.com for the endpoints.
Extend Person endpoint with support for items - CUR-3989
The person API returns the items object(s) stored on a person, such as professional development or qualification records. Items are always returned, irrespective of the requested academic year. Expired records will be returned with the end date rather than being left out.
- Items sent with a person are saved, so they can be added and updated through the API. An import does not remove items created in the application.
- The start and end date of an item are now included for each endpoint that exports items, for example on modules and studies.
CSV import extended with version for teaching methods and assessments - CUR-4296
The teaching method and assessment CSV imports have two new columns, definition and version. Both values are also included in the import and export API for teaching methods and assessments, as they are for modules.
Security
Our build process scans continuously for known vulnerabilities. Fixes are prioritised by impact: some go out as an immediate hotfix, others in the current or next sprint. See the central database of vulnerabilities for details.
Implemented security fixes - CUR-4214
Based on our standard constant security validation some medium and minor vulnerabilities were identified that have been fixed. This includes update of a number of CVE's, improvement of Token handling and enhanced shielding the monitoring endpoints.
Refer to the Workload Manual for configuration guidance.