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 admin I want to use :fte as calculation value - CUR-3429
A new standard calculation option :fte is added for the workload management tasks. This will use the standard contactual assignment of the user. E.g. a user has a contract with the department Law for 40%, then the :fte value is 0.4.
The allocation and assignment should not be set to 100% - CUR-3469
In the previous release an issue was introduced that when performing a recalculation of workload hours was using the 'separate offerings' settings by default. Where the 'separate offerings' should only should be used in specific situations. This caused the allocation and assignment to be set to 100%. This has been fixed, the default is restored and the calculation performed as expected.
The effort list should show correct totals - CUR-3466
In case a task is assigned to a period, and the periods are overlapping, e.g. quarter 1 and semester 1, the calculated effort totals were incorrect. Only one of the periods was used (due to the overlapping). This has been fixed and in case of overlapping periods, both are used in the calculation.
Auto generated ad-hoc periode code should be unique - CUR-3468
In the previous release the option was added to automatically generate the code of an ad-hoc period using a self configured formula. This function worked very well and is highly appreciated, the only issue was that the generate function that should automatically generate a trailing value to make the generated code unique was not working as expected. This caused message on 'duplicate code' and prevented the ad-hoc offering from being saved. This has been fixed and the code will be generated unique, preventing duplicate offering codes.
Terminated modules assessments should not be shown in the assessment-report - CUR-3336
The assessment-report template is used to report all assessments in the context of a faculty or programme. It was noted that assessments belonging to modules that were no longer offered (terminated in the selected year) were still showing.
A fix is applied and all assessments that are offered by a terminated module are no longer shown in the assessment-report.
The ad-hoc code should not be editable when set to read-only - CUR-3391
In case the code for offerings was set to read-only, it worked for offerings, but not for ad-hoc offerings. A quick fix would be to make it work independent for the offering type. But looking back in retrospective we realised there were quit some differences in the definition and usage of ad-hoc offerings.
We decided not to go for the quick solution, but to create a new object in the data model, where we now have the offering and the adhoc offering as separate objects. Both sharing their own configuration options, to ease the configuration and not doubting to hide or show fields based on type, select for both type to use read-only or editable.
Reference list management should show the references - CUR-3481
The reference list management (administrator) allows for the definition of conditional lists. In case the full list exceeded 250 items, not all values were selectable for adding to the conditional list. This has been fixed, so configuring conditional
The assessment-report should support filtering for owned and its status - CUR-34xx
The assessment-report is extended with support to filter the display on:
- show owned: show only the assessments owned by the selected object. For module it will be the assessments owned by the module. For programme it will be the assessments for modules owned by the programme
- show all: show all assessments, irrespective if they are owned or not owned
The user can select between the two filter options.
Configuration:
The administrator can configure the default behaviour of the assessment-report page with two new introduced configuration options:
- show all: the report will open, standard showing all the assessments (owned and non-owned).
- show filter: show the filter panel when opening the report (instead of collapsed)
In case a user applies for a role for an educational object, e.g. lecturer on module X, there was no option to highlight the relevant competences. This has been fixed, so the user can select the relevant competences for the application from its personal competence list.
When entering an application or approving an application for a role not only the relevant, but all buttons where shown. This has been fixed, and only the relevant buttons, e.g. approve/reject or cancel/submit, will be shown.
The competences report showed all competences of all users when retrieving the report for a specific department. This has been adjusted and only the users and their competences are shown for the department, instead of all.
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.
Ignored time-blocks should not be exchanged with TE server - CUR-3518
When using periods and time-blocks there is an option to mark time-blocks as 'ignore'. This should prevent these time-blocks to be exchanged to other systems. It was found that the TE server integration didn't filter the 'ignored' time-blocks. This has been fixed, so only the time-blocks that should be exchanged will be sent.
CSV import should support update of assignment fte - CUR-2618
When using the CSV import to upload assignments, the fte value was not correctly processed. A fix is applied to support updating the fte assignment value using the CSV import,
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.
Address OWASP security vulnerabilities - CUR-3492
Security vulnerabilities addressed:
- CVE-2026-29062(8.7)
- CVE-2026-29062(8.7)
- CVE-2025-68161(6.3)
Refer to the Workload Management manual for configuration guidance.