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.
As an administrator I want to hide the faculty tab - CUR-3354
Using the page visibility the administrator can hide 'default' tabs from the user interface. It was noted that he ability to hide the Faculty tab was not supported. This has been added, to enable hiding the Faculty main tab voor all users.
The study code should not be regenerated when adding a new offering - CUR-3686
In case the automatic code generated for a study uses the offering as part of the code, the regeneration of the code was incorrectly executed when adding a new offering. A fix is applied to prevent triggering the code generation based on the creation of a new offering.
The annual roll-over should copy the assessment custom-fields - CUR-2525
The fields credits and duration on assessment were not copied to the future year when performing a roll-over. The fields are added to the year copy functionality to copy the over to the future year.
The custom-fields report should provide information where the field is used - CUR-2346
The custom-field report (administrator function) provides insight in the defined custom-fields and their attributes in the system. The report is extended to provide information on what page(s) a custom-field is used.
As an administrator I want to see in which workflows a role is used - CUR-2480
When managing a role (relation), a new feature is added that shows the workflows the specific relation is used in.
Manual notifications should only be sent once - CUR-3720
When sending notifications to staff members bound to a role, e.g. module coordinator, from faculty level, the notification was sent multiple times. It was found that the notification was sent to each staff member -> module relation, duplicating the notification for all users having multiple module relations. This has been fixed, and the notification is sent on individual, unique user.
Workflows should support person-based notifications - CUR-2183
Notifications can be configured to be sent, for instance if a process changes status. In the definition the role(s) to receive the notification are configured. For some processes, e.g. the availability process there is no role defined (it's implicit) and it is not possible to define a notification at status change, since there is no role available.
A fix is made, using the 'implicit user'. This means that for person-based workflows with no workflow attached that defines a role, the notification will be sent by default to the person itself.
An example of a configuration that sends a notification to the person when reaching a status is shown below. There is no Role defined, so the fallback is the usage of the 'implicit person'.
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.
Extend the API to support retrieval of (non-)educational activities - CUR-3741
The API is extended with the new endpoint worklogs. Using this endpoint both the educational and non-educational activities (tasks) can be retrieved.
Usage: <your_url>/api/canonical/v2/worklogs
Filters:
- no filter: retrieve the non-educational tasks
- ?educational = true: retrieve the educational tasks
- ?year = 2026: retrieve the worklogs for the defined year. Default the active year is used
- ?person = JDOE: retrieve the worklogs for the person with external ID (login) JDOE.
Information returned:
- activity information: type, name, date, code
- worklog information: plannedMinutes, actualMinutes
- person information: id, code, name
When updating an organisation via the API the last updated should be set - CUR-3516
In case an organisation (specification and qualification) was updated using the API, the last updated dateTime was not set. This has been changed, and not only the data, but also the last updated is set when using the API.
It should be possible to to sent unavailability for users already have bookings to Data Manager - CUR-3724
In case unavailability information was sent to Data Manager, but the user already has booking, no updates were made since an error is thrown the user already has bookings. A change is made to allow double booking when sending unavailabilities, causing the unavailability to be created / updated even if a user already has defined bookings.
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.