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.
A changes report can be limited to specific change categories - CUR-2687, CUR-2383
Support for Change categories is added to the changes page template. Earlier releases added support for the administrator to define change categories, and for instance create a category focussing on specific changes. E.g. only relation changes, relevant study changes with respect to accreditation, etc.
The option is added to create a changes (change report) page with a defined the change category. This allows using a specific, context based overview of changes per workflow.
Next to the configuration of a specific change report page, the changes report is extended with a Change categories selection. This allows for manual selecting a preconfigured category and apply that as a filter.
The Changes report should default to the selected year - CUR-2689
The Changes report will default opens with the selected year, instead of showing all year information.
Versioning: teaching methods, assessments and new definitions - CUR-4296, CUR-4142, CUR-4143
The versioning has been extended with support for teaching methods and assessments. The behaviour is equal to studies, module groups and modules, with a teaching method or assessment with an external ID is grouped into versions under a definition. The pagea show the version selector and Create new version next to the year selector.
See Curriculum: versioning configuration and usage for the full configuration.
Terminated modules should not be considered in the studyability validation - CUR-3886
A terminated module was still considered in the studyability validation. This has been corrected and the module and its credits will no longer be add to any period total, and it is no longer listed among the modules of the period.
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.:
- In case the the number of groups of an offering goes down, e.g. the number of students is reduced, the excess of groups are removed, and the user is informed. The removed activity groups page are added to the change history.
- The group manager screen used in a workflow cannot be closed in case the groups don't match up the calculated number of groups.
- When the number of groups is increased, e.g. number of students is increased, earlier removed groups are not added. They must be added manually in this case.
Offering based activity group handling optimised - CUR-4289, CUR-4326, CUR-4322
In the previous release (12.22) the option has been added to define activity groups per offering, using the setting schedule.generate_method_groups. A few changes are applied to optimise the group management.
Annual rollover should copy the related objects of subjects - CUR-4164
The rollover did not copy the Related objects of the subjects of a module to the new academic year. This has been fixed.
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.
Faculty and organisation added to the specifications report - CUR-4196
The specifications report is extended with support for the Faculty and Organisation column, offering support to show the related Faculty / Organisation in the report.
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.
Publishing to the curriculum broker should be simplified - CUR-4307, CUR-4256, CUR-4323
The publishing of information to the broker required setting a publication date and then publishing the information in two different steps (hooks). This has been changed by adding two hooks: Publish object and Unpublish object. The hook will respectively set the publication data and publish to the broker or unset the publication date and 'unpublish' from the broker in one go. Not requiring separate hooks anymore.
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.
Ignored offerings are not exported and not changed by imports - CUR-4344
The import and export API no longer sends offerings marked Ignore. An import leaves an ignored offering as it is: it is not updated or removed, and incoming data that matches it does not create a duplicate. Deleting an ignored offering through the API is refused.
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.
Add support for calendar periods to Reference endpoint - CUR-4355
A request for periods in the reference import API can now include calendar, with the external ID or code of a calendar. This will return the periods of that calendar. Executing the call with only calendar will return a list of all calendars.
Reference import externalId handling improved - CUR-4306
- A type created earlier without an external ID can be updated again. The import recognises it by its code and fills in the external ID, instead of failing.
- A reference type import no longer replaces the external ID of an existing type. A row whose ID conflicts with the external ID already stored for that code is rejected with a clear message, and the existing type is left unchanged.
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.
See the Curriculum manual for configuration guidance.