Release Notes

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.

The quick-search result in the topbar should direct to the details - CUR-2470 (Hotfix)

Under specific circumstances a search result shown in the quick-search, when clicked didn't redirect to the selected detail page. This has been fixed, to allow search and direct click-through to the detail page under all circumstances.

‍

Activities from previous years should offer an automated options - CUR-2470 (Hotfix)

The standard behaviour of the year roll-over is that the academic calendar and the educational components are copied to the newly created year. The educational components are copied, except for the activity-series. This to offer the responsible stakeholder to manage the delivery of a teaching methods or assessments the change to either use one click to select the information from the most recent year, or start from scratch.

This behaviour is not desired in all cases, and a request has been made to support an more automated way to copy the activity-series from the most recent years. A new hook is introduced that will copy the activity-series for a module from the most recent year. Using the combination of process manager, the standard reports and the hook a single, a selection or all modules can be selected and the hook can be applied. This automates the copy of the activity-series for all modules just by selecting the desired ones and execute the hook.

‍

As a user I want to select multiple values for multi-value fields  - CUR-2560 (Hotfix)

In case a field was defined as a multi-value field, it behaved like a single value. Only one option could be selected. This has been fixed, and the multi-value field allows selecting multiple values again.

‍

Only the assessment changed should be changed - CUR-2530 (Hotfix)

When changing an assessment allocated to multiple offering periods, the assessment was changed for all offering periods. This was a front-end issue, that has been fixed.

‍

As a user I want to select the assessment type - CUR-2505 (Hotfix)

It was not possible anymore to select values that were offered based on a drop-down UI component. It was reported for assessment type, but the same issue when creating a new module-group and select the type. This has been fixed, and the dropdown select options are working again as expected.

‍

Exam duration should support display in minutes and HH:MM format  - CUR-2526 (Hotfix)

The duration is standard defined as a field of type 'Number'. This means that the values are displayed as a numeric value, where in some cases a not always 100% perfect visualisation was implemented to translate the number to a 'time like' display.

To provide a better user experience and a consistent display of time information a new type has been added name 'Minutes'. By selecting minute, the data entry and data display is using a time format. The data is still stored as a numeric value.

Configuration: when defining the custom-field, set the value type to Minutes, next as sub-type select the field that should be displayed using the time format.

The display format is shown in the image below, where the time information is entered using a hours and minutes separation. The display format in read-only mode is HH:MM.

Module (and some other) searches are responding too fast  - CUR-2503

A change applied to the data-entry component for search was too responsive. It felt that almost before the character was typed the search was already executed. And each additional character immediately launched a new search. Causing difficulties in search and a bad user experience. This has been fixed, where the search is made less responsive and will wait a little time after a key stroke to allow the user to type a next character before starting a search.

‍

As a user I want to add a relation that is found using the advanced search  - CUR-2445

When using the advanced search to find a person to be assigned to a relation, the assignment didn't work. The fallback was that if the user was found, switch to the direct search and then assign the user. But the workaround is no longer required, since this has been fixed in this version.

‍

The task contribution report should show the contribution in percentage  - CUR-2366

A few releases ago the tasks-contribution report template is released, showing how many hours (staff from) an organisation contributes to each study. This version the report is extended to not only show the number of hours but also the contribution percentage per study.

‍

The teacher-assign template should show the activity-type  - CUR-2469

The teacher assign page offers the option to assign staff members to the defined activities. The page offers various filter options to select the activities and assign staff to those activities with one click. The filtering options are extended with the activity-type, allowing more variations in filtering the activities and assign the staff members.

‍

The activity-card should respect the end date  - CUR-2497

The activity-card shows field from the method-activity serie and assessment-activity-serie. In case a field has been given an end date, to configure it is no longer used, the field and its information were still shown. A fix is applied to force the activity-card respect the defined end date on fields.

‍

The activity-grid should show the activity type on the tiles  - CUR-2483

The tiles in the activity grid use to have a ‘header’ and a ‘caption’. The introduction of individual lesson names caused a change in the information display of the tiles. This was an unintended change and the display has been restored to the previous behaviour:

• Header: shows the ACTIVITY TYPE (name of the type, e.g. lecture, practical, written test.
• Caption: shows the LESSON NAME in case set, else show the ACTIVITY-SERIE CODE

‍

As a user I want to search / filter on dates as if they are strings  - CUR-2445

The search / filter option offered in the standard reporting for dates has been extended. Support is added to search as if the date is not a date, but as string. This means that a search on a part of the date will already provide results, e.g. search/filter on 13 will show dates like 13-10-2025, 13-01-2023.

‍

Extend the copy of appraisal/method-scheme with support for individual assessment/method  - CUR-2460

The option to copy assessment and method related date is extended. The appraisal and method-scheme will offer 2 copy buttons.

• The button shown on the assessment or method will only copy the assessment / method and its underlying activity-serie(s).
• The button shown on the highest level (appraisal / method-scheme) will perform the copy including all defined underlying assessments / methods.

While developing the new functionality the issue where the activity-serie name was not set after the copy is solved.

‍

A form page based on activity-serie should show the desired fields - CUR-2422

To support the management of activity-serie information in a workflow, a custom form page based on the activity-serie is required. The support for using an edit page in the workflow was only supported using the default edit page showing all fields. Using a custom form page, to only select the desired fields, didn't show all available fields on the activity-serie. A change is applied to extend the selectable fields to all activity-serie fields and allow the usage of the custom form page with the fields set in  a workflow.

‍

The year roll-over should support roll-over of multiple faculties  - CUR-2520

The year roll-over generated an error when creating the new year and rolling over all faculties in one go. The work-around is to copy one faculty at a time. The issue causing the error has been identified and is fixed. The year roll-over will support copying over all faculties in one action.

‍

Multi-value Element based fields should be shown readable on read-only pages  - CUR-2352

In a previous release the readability of read-only multi-value information has been improved. The values are displayed as bulleted options as improvement. It was highly appreciated, but it was noted that multi-value fields based on an Element used the 'old', less readable visualisation. This has been adjusted and all read-only multi-value fields will display in the same readable format.

‍

As an authorised user I want to delete an appraisal - CUR-2420

An option has been added to support deletion of an appraisal using the standard authentication rules. To support and steer the deletion the following authentication rules are available:

• EDIT_APPRAISAL: Edit an existing appraisal
• DELETE_APPRAISAL: Delete an existing appraisal
• CREATE_APPRAISAL: Create a new appraisal

‍

As a user I should be able to change the parent of an assessment - CUR-2474, CUR-2512

In the previous version the following change has been applied: Using the 'admin' tab of an assessment provides the option to change the parent. However, when saving the changed information, the change was not affected. It seemed that the parent was excluded from the save. This has been adjusted, so the assessment and its change parent will  now be saved correctly.

‍

A situation was found where the function gave an error and thus didn't function. The was caused by the fact a parent should be a 0-1 relation and should be configured as such (default setup). In this case the parent was accidentally set to multi-value. A change is made that will perform an additional check during start-up to validate if a default relation is accidentally changed to multi-value, and will correct this change.

‍

As an admin I should be able to change the linked information - CUR-2474

In the previous version the (?) icon was added in the topbar providing the option configuring links to documentation. A third option offered, but not mentioned was the link to the accessibility information. In fact, the link was shown, but the underlying label and URL were not yet available.

The set of configurable links is:

• Navigation.Help.Docs.Url (renamed label for Static.Label.Manual.Url), used to define the URL to the documentation.
• Navigation.Help.Support.Url (new label), used to define the URL to the internal support info (FAQ) or support desk.
• Navigation.Help.Accessibility.Url (new label), used to define the URL to the internal support info (FAQ) or support desk.

In case the URL is defined empty or with only a - (dash), the menu item will not be shown. This to allow only showing relevant menu items with a link.‍

‍

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.

‍

Analysis impact CVE-2025-55182

A so-called zero-day vulnerability CVE-2025-55182 has been reported. Due to the impact and the possible requirement for an immediate hotfix the vulnerability has been analysed. The outcomes of the analysis was that the reported vulnerability did not have an effect, since the vulnerable part is not used and not immediate action (hotfix) is required.

The fix for the vulnerability is applied following the standard procedure to keep the used standard components up to date covering both access to new functionality, stay up to date with fixes and security patches.

‍

Refer to the Workload Management manual for configuration guidance.

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.

‍

Hotfixes

‍As probably noticed reading the release notes, quit a high number of issues has been marked and resolved as hotfix. Therefor a separate section is added to create a distinction with the issues following the standard release pattern.

This is caused by the fact we are aware that during this period in year the different processes to manage the curriculum and its content is starting and in some cases peaking. We understand the pressure this may put on the staff involved and therefore we increased the hotfixes providing a short(er) cycle for fixes.

‍

Reference labels should be editable, shown and correct - CUR-2395, CUR-2482 (Hotfix)

The latest version introduced some undesired behaviour managing and displaying reference table data. The reference information was not editable and the definition of conditional reference list may show reference values from another list. The last issue was that the labels assigned to a reference table were not always displayed, and either no or a fallback to the code was used to display reference options.

All of the above are fixed, so the reference information can be managed and will be shown as expected.

‍

The quick-search result in the topbar should direct to the details - CUR-2470 (Hotfix)

Under specific circumstances a search result shown in the quick-search, when clicked didn't redirect to the selected detail page. This has been fixed, to allow search and direct click-through to the detail page under all circumstances.

‍

Activities from previous years should offer an automated options - CUR-2470 (Hotfix)

The standard behaviour of the year roll-over is that the academic calendar and the educational components are copied to the newly created year. The educational components are copied, except for the activity-series. This to offer the responsible stakeholder to manage the delivery of a teaching methods or assessments the change to either use one click to select the information from the most recent year, or start from scratch.

This behaviour is not desired in all cases, and a request has been made to support an more automated way to copy the activity-series from the most recent years. A new hook is introduced that will copy the activity-series for a module from the most recent year. Using the combination of process manager, the standard reports and the hook a single, a selection or all modules can be selected and the hook can be applied. This automates the copy of the activity-series for all modules just by selecting the desired ones and execute the hook.

‍

As a user I want to select a reference value that exceeds the 250th position - CUR-2527 (Hotfix)

Due to a small error in the paginated retrieval of a reference list, only the first set of 250 values was retrieved and offered for selection. This has been fixed, so all reference values will be retrieved and offered for selection.

‍

The quick-search should only show the configured searchable types - CUR-2395 (Hotfix)

When using the quick-search the option is shown to select what object type (e.g. module, study, method, assessment) should be taken into consideration. The shown selectable types were all types in the system, even if the type was not explicitly marked as 'searchable'. This has been fixed, so only the object types that are marked searchable fill be offered for selection.

‍

As a user I want to select multiple values for multi-value fields  - CUR-2560 (Hotfix)

In case a field was defined as a multi-value field, it behaved like a single value. Only one option could be selected. This has been fixed, and the multi-value field allows selecting multiple values again.

‍

Only the assessment changed should be changed - CUR-2530 (Hotfix)

When changing an assessment allocated to multiple offering periods, the assessment was changed for all offering periods. This was a front-end issue, that has been fixed.

‍

As a user I want to select the assessment type - CUR-2505 (Hotfix)

It was not possible anymore to select values that were offered based on a drop-down UI component. It was reported for assessment type, but the same issue when creating a new module-group and select the type. This has been fixed, and the dropdown select options are working again as expected.

‍

Exam duration should support display in minutes and HH:MM format  - CUR-2526 (Hotfix)

The duration is standard defined as a field of type 'Number'. This means that the values are displayed as a numeric value, where in some cases a not always 100% perfect visualisation was implemented to translate the number to a 'time like' display.

To provide a better user experience and a consistent display of time information a new type has been added name 'Minutes'. By selecting minute, the data entry and data display is using a time format. The data is still stored as a numeric value.

‍

Configuration: when defining the custom-field, set the value type to Minutes, next as sub-type select the field that should be displayed using the time format.

The display format is shown in the image below, where the time information is entered using a hours and minutes separation. The display format in read-only mode is HH:MM.

‍

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.

‍

Module (and some other) searches are responding too fast  - CUR-2503

A change applied to the data-entry component for search was too responsive. It felt that almost before the character was typed the search was already executed. And each additional character immediately launched a new search. Causing difficulties in search and a bad user experience. This has been fixed, where the search is made less responsive and will wait a little time after a key stroke to allow the user to type a next character before starting a search.

‍

As a user I want to add a relation that is found using the advanced search  - CUR-2445

When using the advanced search to find a person to be assigned to a relation, the assignment didn't work. The fallback was that if the user was found, switch to the direct search and then assign the user. But the workaround is no longer required, since this has been fixed in this version.

‍

Matrix learning route should only show the relevant calendar periods  - CUR-2442

The dedicated matrix report displaying the planned modules using the time-block information  spread over the week and time-blocks showed all calendars defined in the system. In case using multiple calendars, a filter is defined to assign the filter to a dedicated set of education objects, e.g. a faculty. The matrix report didn't respect the defined filter, which caused the visualisation / duplication of all calendars in the report.

A fix is applied causing the matrix learning route report to respect the defined filter and only show the one relevant calendar.

‍

The task contribution report should show the contribution in percentage  - CUR-2366

A few releases ago the tasks-contribution report template is released, showing how many hours (staff from) an organisation contributes to each study. This version the report is extended to not only show the number of hours but also the contribution percentage per study.

The teacher-assign template should show the activity-type  - CUR-2469

The teacher assign page offers the option to assign staff members to the defined activities. The page offers various filter options to select the activities and assign staff to those activities with one click. The filtering options are extended with the activity-type, allowing more variations in filtering the activities and assign the staff members.

‍

The activity-card should respect the end date  - CUR-2497

The activity-card shows field from the method-activity serie and assessment-activity-serie. In case a field has been given an end date, to configure it is no longer used, the field and its information were still shown. A fix is applied to force the activity-card respect the defined end date on fields.

‍

The activity-grid should show the activity type on the tiles  - CUR-2483

The tiles in the activity grid use to have a ‘header’ and a ‘caption’. The introduction of individual lesson names caused a change in the information display of the tiles. This was an unintended change and the display has been restored to the previous behaviour:

• Header: shows the ACTIVITY TYPE (name of the type, e.g. lecture, practical, written test.
• Caption: shows the LESSON NAME in case set, else show the ACTIVITY-SERIE CODE

‍

As a user I want to search / filter on dates as if they are strings  - CUR-2445

The search / filter option offered in the standard reporting for dates has been extended. Support is added to search as if the date is not a date, but as string. This means that a search on a part of the date will already provide results, e.g. search/filter on 13 will show dates like 13-10-2025, 13-01-2023.

‍

The subject matrix download should export in the correct order  - CUR-2445

The subject order download created an Excel with a different ordering of the subject columns. A change is applied to keep the display order as shown on the page equal to the order when exporting to Excel.

‍

Deleting an objective from a module should not require a comment  - CUR-2529

Deletion of an objective from a module required the entry of a comment. Since a comment is not required, a fix applied to enable deletion of objectives without a required comment.

‍

The qualification-report template should only show valid studies  - CUR-2462

The qualification report provides insight in the studies using the qualification. The filter applied to the 'used by' was not respecting the academic year and showing all studies that used the qualification in the current and previous years. A fix is applied to limit the used by information to the active selected year.

‍

The planboard should expand all groups (if configured so)  - CUR-2319

In a previous release the configuration option was added to define the behaviour of 'expand all' on the structure and planboard page. The default was that only the own module-groups were expanded, the added configuration option defined that all module-groups should be expanded. The behaviour related to the setting was applied to the structure page, but not to the planboard. This has been adjusted, so both the structure and planboard page respect the 'expand all' setting.

‍

The planboard should  only show the configured subjects - CUR-2318

Using the planboard to display and filter on subjects assigned to the modules in the study, all subjects defined on the modules were shown on the tiles and as filterable options. Even in case the subject was not defined on the study looked at. A fix is applied where the planboard respects the defined subjects on the study and only shown those subjects as filterable options and as 'coloured bullets' on the module tiles.

Extend the copy of appraisal/method-scheme with support for individual assessment/method  - CUR-2460

The option to copy assessment and method related date is extended. The appraisal and method-scheme will offer 2 copy buttons.

• The button shown on the assessment or method will only copy the assessment / method and its underlying activity-serie(s).
• The button shown on the highest level (appraisal / method-scheme) will perform the copy including all defined underlying assessments / methods.

While developing the new functionality the issue where the activity-serie name was not set after the copy is solved.

‍

A form page based on activity-serie should show the desired fields - CUR-2422

To support the management of activity-serie information in a workflow, a custom form page based on the activity-serie is required. The support for using an edit page in the workflow was only supported using the default edit page showing all fields. Using a custom form page, to only select the desired fields, didn't show all available fields on the activity-serie. A change is applied to extend the selectable fields to all activity-serie fields and allow the usage of the custom form page with the fields set in  a workflow.

‍

The year roll-over should support roll-over of multiple faculties  - CUR-2520

The year roll-over generated an error when creating the new year and rolling over all faculties in one go. The work-around is to copy one faculty at a time. The issue causing the error has been identified and is fixed. The year roll-over will support copying over all faculties in one action.

‍

Multi-value Element based fields should be shown readable on read-only pages  - CUR-2352

In a previous release the readability of read-only multi-value information has been improved. The values are displayed as bulleted options as improvement. It was highly appreciated, but it was noted that multi-value fields based on an Element used the 'old', less readable visualisation. This has been adjusted and all read-only multi-value fields will display in the same readable format.

‍

The study structure cost template should show choice rules  - CUR-2473

When using the study structure cost template, the defined choice rules were no longer displayed. This has been fixed and the choice rules are displayed again.

‍

As an authorised user I want to delete an appraisal - CUR-2420

An option has been added to support deletion of an appraisal using the standard authentication rules. To support and steer the deletion the following authentication rules are available:

• EDIT_APPRAISAL: Edit an existing appraisal
• DELETE_APPRAISAL: Delete an existing appraisal
• CREATE_APPRAISAL: Create a new appraisal

‍

As a user I should be able to change the parent of an assessment - CUR-2474, CUR-2512

In the previous version the following change has been applied:Using the 'admin' tab of an assessment provides the option to change the parent. However, when saving the changed information, the change was not affected. It seemed that the parent was excluded from the save. This has been adjusted, so the assessment and its change parent will  now be saved correctly.

A situation was found where the function gave an error and thus didn't function. The was caused by the fact a parent should be a 0-1 relation and should be configured as such (default setup). In this case the parent was accidentally set to multi-value. A change is made that will perform an additional check during start-up to validate if a default relation is accidentally changed to multi-value, and will correct this change.

‍

As an admin I should be able to change the linked information - CUR-2474

In the previous version the (?) icon was added in the topbar providing the option configuring links to documentation. A third option offered, but not mentioned was the link to the accessibility information. In fact, the link was shown, but the underlying label and URL were not yet available.

The set of configurable links is:

• Navigation.Help.Docs.Url (renamed label for Static.Label.Manual.Url), used to define the URL to the documentation.
• Navigation.Help.Support.Url (new label), used to define the URL to the internal support info (FAQ) or support desk.
• Navigation.Help.Accessibility.Url (new label), used to define the URL to the internal support info (FAQ) or support desk.

In case the URL is defined empty or with only a - (dash), the menu item will not be shown. This to allow only showing relevant menu items with a link.

‍

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.

‍

OOAPI pagination should follow the standard - CUR-2439

The OOAPI pagination is 1-based, and the default pagination in Curriculum is 0-based. This worked correctly for the first page, but retrieving information exceeding the defined page limit (requiring multiple pages)  didn't apply the adjustment to act 1-based. This has been fixed and paginated data is also returned correctly.

‍

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.

‍

Analysis impact CVE-2025-55182

A so-called zero-day vulnerability CVE-2025-55182 has been reported. Due to the impact and the possible requirement for an immediate hotfix the vulnerability has been analysed. The outcomes of the analysis was that the reported vulnerability did not have an effect, since the vulnerable part is not used and not immediate action (hotfix) is required.

The fix for the vulnerability is applied following the standard procedure to keep the used standard components up to date covering both access to new functionality, stay up to date with fixes and security patches.

‍

Refer to the Curriculum manual for configuration guidance.

‍

This bug fix was introduced in Test environment 11-12-2025, and will be pushed to production with the 04-12-2025 release.

Bug

When searching for Program of study while dedicating a group, some programmes did not appear in the results. The search now uses all mapped, searchable, programme fields and shows them in the dropdown, so programmes are consistently findable.

The release notes provide information on the features and improvements in the specified version.  The release dates related to the versions are published in the Evaluation release schedule.

‍

Improvements

New functionality, user experience refinements, and bug fixes. Issues marked as hotfix are developed in this sprint but applied to the previous release or directly to production, depending on impact.

‍

The condensed consecutive report should show results - EV-388

The condensed consecutive report shows the evaluations results in a condensed manner. Due to a change there were no evaluation results shown. A fix is applied and the results are shown again, like in the screenshot below.

The statistical information shown in reports is not clear - EV-389

The statistical information shown in the evaluation reports was not clear and raised some questions. The information shown is for example 9.5 / 9 / 0.8 (12) with the following explanation for each value

• Average = 9.5
• Median = 9
• Deviant =  0.8
• (Maximum) = 12

A legend is added to the reports, so the structure of the compact display of statistical information is clear to the users.

‍

Lecturers should have access to the lecturer reports  - EV-392

When opening lecturers year report, a message was shown "In this period, you don't have the required relationship (in order to view this report) to one or more of your evaluations". The report expected the evaluationId of the lecturer as input. If they were not provided the error was thrown.

A fix is applied to enable the display of the report without providing any evaluationId(s). The default behaviour will determine all personal evaluationIds for the lecturer and base the report on those.

‍

Security

An integral part of our development and build process is the automatic scanning for known security vulnerabilities. Fixes are prioritised based on impact: some may require an immediate hot-fix, while others are addressed in the current or next Sprint (release). For more information on reported vulnerabilities, see the central database of vulnerabilities.

‍

During this release no vulnerabilities were reported that needed mitigation.

‍

Refer to the Evaluation manual for configuration guidance.

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 Study guide 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 are developed in this sprint but applied to the previous release or directly to production, depending on impact.

‍

Module groups should be shown in same order as in Curriculum - SG-514

The module groups shown in the structure overview will be shown in the defined sequence order. In case the sequence was not defined, the order in which the module groups were shown in the structure was different from Curriculum. A change is applied to use the sequence if available (no change), otherwise use the same sorting order algorithm in both Study guide and Curriculum.

The sorting order is: sequence, then type sequence, then code, then abbreviation.

‍

The administrator should be able to delete configured elements - SG-517

A bug was introduced that caused deletion of configuration, such as filters, labels, jobs, references and tabs, could not be deleted. This has been fixed, so the different configuration settings can now be added, updated and deleted again.

‍

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.

During this release no vulnerabilities were reported that require mitigation.

‍

For more guidance on configuration and setup of Study Guide, use the relevant Study Guide manual.

This release moves Registration period editing into the Allocate Overview for faster, less error‑prone updates and makes proposal scope easier to understand in the detailed view. It also improves permission error messages so users why they have problems updating a group or allocating a student.

This release is pushed to test at release date and production a week later.

Improvements

• Registration period management in Edit menu
• What changed: The Registration period page has been removed and replaced with “Registration period” under the Edit menu in Allocate Overview.
• Why: Aligns with other edit actions, reduces context switching, and requires both start and end dates to prevent partial entries.
• Also new: You can now clear a registration period when needed.

• Clearer scope in Allocation proposal
• What changed: The detailed proposal view now lists the modules that are included in the generated solution.
• Benefit: Quicker validation and easier cross‑reference when reviewing proposals.

• What changed: When a user tries to modify a group or allocate a student without the required permissions, the error message clearly states the restriction and where it applies.

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.

‍

Fields of type number should not offer 'undesired assistance' - CUR-2387

The number field offers an 'up and down arrow' as assistance, to allow using the mouse or up and down arrows to enable stepping one up or down. This was working so good that in case a value was typed it was very easy to change the value when moving away or scrolling away, causing the value to be changed.

A change is applied to handle to focus to the or 'mouse-over arrows' and prevent from accidental changing the value when moving away or scrolling the page.

‍

As a user I want a clear option to de-select a value - CUR-2387

Based on standard guidelines the de-select of a value in a list-box was recently changed from an 'empty selection' to a stylish x in the select box. Based on the reactions we learned that stylish is not always the most understandable solution for implementation consultants and users. We reverted the change and added the 'No selection' option to the listbox to de-select a earlier selected value.

Information set to be shown on the method-scheme should be shown  - CUR-2464

When marking a field to be shown at method level in the method-scheme, the information was not shown. At the end the issue was not that the information was no shown, but that more than 2 values were defined to be shown. The display limited the display to two additional columns (values), to keep the screen as calm as possible.

A change is made to increase this limit to a maximum of four additional values to be shown.  The expectation is that the administrator doing the configuration will validate based on the type / values of the additional added fields will validate if four will fit and still keep a readable page.

‍

The label and related value should be aligned  - CUR-2446, CUR-2345

It was noted due to some generic UI changes applied the alignment between the label and its corresponding value was off in case the information was shown read-only. The effect was visible for individual fields or pages marked as read-only or the label page (which is always read-only). This has been fixed, so the label and its corresponding value are properly aligned.

‍

Topbar related findings and improvements - CUR-2454, CUR-2404

The release of the topbar to the acceptance environment has lead to a number of findings that are solved in this release:

• As a user you should only see the accessible menu items in the Personal menu, instead of all
• The selected menu options should be highlighted, so the user will immediately see what menu has been selected

‍

The footer information should be moved to the topbar - CUR-2444

The footer is removed and the information accessible in the footer has been moved to the topbar. The topbar will show a (?) (question mark icon) at the right, that unfolds when clicked. The information accessible is the information that was defined in the footer.

Configuration

As part of the change applied the label identifiers used will be changed, and a new one is defined:

• Navigation.Help.Docs.Url (renamed label for Static.Label.Manual.Url), used to define the URL to the documentation.
• Navigation.Help.Support.Url (new label), used to define the URL to the internal support info (FAQ) or support desk.

‍

When adding an existing group, filtering should be able - CUR-2360

When adding a module-group to the study structure, the filter option supporting filtering on attributes such as module-group type or faculty didn't work (anymore). The filter could be applied, but the results were not filtered. This has been fixed, so filtering is working again.

‍

The activity-list should support display of all activity defined fields - CUR-2489

When defining the fields to be shown in the activity-list, the select box offering the available fields to select from only showed a limited set of fields. This has been fixed, so the select box of fields to be shown is showing all defined fields.

‍

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 API support for expressions should be more forgiving - CUR-2430

The API Get endpoints provide the option to specify an expression to restrict the returned results, e.g. typeId in ('BA', 'MA') on the study endpoint to only retrieve studies of type Bachelor or Master. The definition of the filter was very strict, like using the correct casing. Some changes have been applied to be more forgiving using different casing and spacing.

‍

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.

‍

Person information should only be accessible and editable for the admin - CUR-2453, CUR-2461 (Hotfix)

Due to a change applied earlier, for a normal user it was possible by manually entering the URL to get access to the personal information. This has been corrected, so unauthorised users will not have access and will get a proper message stating this.

‍

Refer to the Workload Management manual for configuration guidance.

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.

‍

Fields of type number should not offer 'undesired assistance' - CUR-2387

The number field offers an 'up and down arrow' as assistance, to allow using the mouse or up and down arrows to enable stepping one up or down. This was working so good that in case a value was typed it was very easy to change the value when moving away or scrolling away, causing the value to be changed.

A change is applied to handle to focus to the or 'mouse-over arrows' and prevent from accidental changing the value when moving away or scrolling the page.

‍

The read-only objective template should not show pagination - CUR-2240

When using the objective template in a read-only form, e.g. as a chapter in a rows template based report, not only the objectives were shown, but also the pagination options. A fix is applied, to only show the objectives.

‍

As a user I want a clear option to de-select a value - CUR-2387

Based on standard guidelines the de-select of a value in a list-box was recently changed from an 'empty selection' to a stylish x in the select box. Based on the reactions we learned that stylish is not always the most understandable solution for implementation consultants and users. We reverted the change and added the 'No selection' option to the listbox to de-select a earlier selected value.

As a user I should be able to change the parent of an assessment - CUR-2474

Using the 'admin' tab of an assessment provides the option to change the parent. However, when saving the changed information, the change was not affected. It seemed that the parent was excluded from the save. This has been adjusted, so the assessment and its change parent will  now be saved correctly.

‍

Information set to be shown on the method-scheme should be shown  - CUR-2464

When marking a field to be shown at method level in the method-scheme, the information was not shown. At the end the issue was not that the information was no shown, but that more than 2 values were defined to be shown. The display limited the display to two additional columns (values), to keep the screen as calm as possible. A change is made to increase this limit to a maximum of four additional values to be shown.
The expectation is that the administrator doing the configuration will validate based on the type / values of the additional added fields will validate if four will fit and still keep a readable page.

‍

The label and related value should be aligned  - CUR-2446, CUR-2345

It was noted due to some generic UI changes applied the alignment between the label and its corresponding value was off in case the information was shown read-only. The effect was visible for individual fields or pages marked as read-only or the label page (which is always read-only). This has been fixed, so the label and its corresponding value are properly aligned.

‍

Topbar related findings and improvements - CUR-2454, CUR-2404

The release of the topbar to the acceptance environment has lead to a number of findings that are solved in this release:

• As a user you should only see the accessible menu items in the Personal menu, instead of all
• The selected menu options should be highlighted, so the user will immediately see what menu has been selected

‍

The footer information should be moved to the topbar - CUR-2444

The footer is removed and the information accessible in the footer has been moved to the topbar. The topbar will show a (?) (question mark icon) at the right, that unfolds when clicked. The information accessible is the information that was defined in the footer.

Configuration

As part of the change applied the label identifiers used will be changed, and a new one is defined:

• Navigation.Help.Docs.Url (renamed label for Static.Label.Manual.Url), used to define the URL to the documentation.
• Navigation.Help.Support.Url (new label), used to define the URL to the internal support info (FAQ) or support desk.

‍

When adding an existing group, filtering should be able - CUR-2360

When adding a module-group to the study structure, the filter option supporting filtering on attributes such as module-group type or faculty didn't work (anymore). The filter could be applied, but the results were not filtered. This has been fixed, so filtering is working again.

‍

The assessment matrix should be accessible for users - CUR-2444

The assessment matrix access is allowed for users having the VIEW_ASSESSMENTS right. The access determination was too strict/incorrect. This has been fixed to allow users having the correct right access to the assessment matrix.

‍

The activity-list should support display of all activity defined fields - CUR-2489

When defining the fields to be shown in the activity-list, the select box offering the available fields to select from only showed a limited set of fields. This has been fixed, so the select box of fields to be shown is showing all defined fields.

‍

Long reference names should be shown/accessible - CUR-2321

When using long reference names, exceeding the maximum screen width, the display just showed the part of the reference name that fits on the screen. A fix is applied that will offer a 'mouse-over' in these incidental cases. The mouse-over will show the full name of the reference.

‍

When adding an offering period based time-blocks the name should be shown - CUR-2351

When using time-blocks based offering periods, the user can select a period and then from a list the defined time blocks. The list only shows the code of the defined time blocks. This has been changed to supply both the code and the name of the time block period.
E.g. Q1-TB1 will now be shown as Quarter 1: 13:30-15:10   Q1-TB1

‍

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 API support for expressions should be more forgiving - CUR-2430

The API Get endpoints provide the option to specify an expression to restrict the returned results, e.g. typeId in ('BA', 'MA') on the study endpoint to only retrieve studies of type Bachelor or Master. The definition of the filter was very strict, like using the correct casing. Some changes have been applied to be more forgiving using different casing and spacing.

‍

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.

‍

Person information should only be accessible and editable for the admin - CUR-2453, CUR-2461 (Hotfix)

Due to a change applied earlier, for a normal user it was possible by manually entering the URL to get access to the personal information. This has been corrected, so unauthorised users will not have access and will get a proper message stating this.

‍

Refer to the Curriculum manual for configuration guidance.

Available on Test on Tuesday the 25st of November and Production the 2nd of December.

• Further validation of activities before submission, ensuring it is correct
• Ability to create activities without activity templates
• Improving the validation of Study Combinations submission to ensure it is correct

Available on Test on Tuesday the 25st of November and Production the 2nd of December.

Activity Manager

• Made scheduling results box expandable to avoid relying on inconsistent tooltip on hover.
• Filter on timezone in the activity filter
• Fixed the rendering of time picker
• Fixed issue when activity filters contained <number>-<number>
• Hide archived activity imports

Core

• Fixed issue where fields were not editable any longer
• Improved & extended French translations
• Introduced security headers to further strenghten our application security

Available on Test on Tuesday the 25st of November and Production the 2nd of December.

• Activity imports page improvements:
  • Possibility to hide constraints
  • Possibility to show id of import/template
• Removed left sidebar and moved items to the top bar instead
• Fixed inconsistent behaviour in filtering by week/date range
• General UX improvements

This release focuses on making the Issue list easier to work with and the Allocate Overview more predictable. It introduces a rebuilt issue type filter and fixes an ordering bug so units are always listed alphabetically, even across pages.

This release is pushed to test at release date and production a week later.

Improvements

• Rebuilt Issue type filter
  • What changed: The Issue type filter has been rebuilt so you select the type(s) of issues you want to see, and the corresponding modules are shown.
  • Benefit: Faster triage, fewer clicks, and a clearer link between issues and affected modules.

• We have now introduced support for sequencing rules on activity series level when auto-scheduling, where you can set a minimum and maximum time between activities. This enable customers to auto-schedule  common use cases like:
• I need a minimum of x minutes or hours between activity A and activity B
• I need activity A and activity B to be scheduled back-to-back
• I need a maximum of x minutes or hours between activity A and activity B
• Support selecting several objects for one activity / activity series, enabling customers to for instance have room requirements & teacher requirements which will be correctly assigned in the same auto-scheduling job.

• Additional logging to enable better analysis of failures and performance
• Improved ways to fetch data, taking steps towards running larger auto-scheduling jobs

• Several minor bug fixes and re-factoring/removal of code for improved stability

Available on Test on Tuesday the 25st of November and Production the 2nd of December.

• Edit Multi-Type Objects: the customer can now edit objects containing multiple types directly in the UI.
• System Preferences Access: The TE_ADMIN::admin role can now access System Preferences.
• Objects Page Rename: “Object Manager” is now renamed to Objects for clarity.
• “Created By” in User Drawer: The user drawer now shows who created the user record.

• Ordered Fields in Object Tables: Fields are now displayed in a clearer, more consistent order.
• Protected Object Type Selection: Clearing the object type in the detail drawer is no longer allowed to prevent mistakes.

• Correct Table Height: Table height now updates properly when filters change.
• Membership Update Fix: Membership additions now work correctly after previous removals.
• User Field Population: User fields are now filled correctly when creating or editing.
• Create-User Drawer Stability: The drawer no longer closes unexpectedly when saving.
• Column Selection Reset: Column selections now reset properly when closing the modal.

Available on Production on Thursday the 20st of November for all customers

After several iteration based on your feedback of the new Object Manager in Test, we have finally released it to all customers in Production.

Why this matters

• Removes dependency on Java installations

• Enables wider accessibility and fewer IT hurdles

• Streamlines configuration directly in Admin

• Sets the stage for scalable object management workflows

Key Capabilities

Create and manage objects

• Create new objects with rich metadata

• Add related elements: memberships, organisation nodes, availability, and optional relations

• Compare object details side-by-side for clarity and control

• All edits now support instant field validation, improving feedback and accuracy during entry

Filter and search

Filter by:

• Object typ

• Organisation node

• Any field using flexible search parameters

User friendly editing

• Edit individual objects in a clear UI

• Designed to simplify routine object maintenance

Upcoming improvements

• While the initial release focuses on single object creation and management, upcoming iterations will include:

• Bulk editing – Edit fields, assign org nodes, inactivate or add multiple objects at once.

• Import/Export – Support for batch import/export by object type and matching filters.

Required permission To access the Object Manager in Admin, the user must have the scope: TE_Admin::admin.

The release notes provide information on the features and improvements in the specified version.  The release dates related to the versions are published in the Evaluation release schedule.

‍

Improvements

New functionality, user experience refinements, and bug fixes. Issues marked as hotfix are developed in this sprint but applied to the previous release or directly to production, depending on impact.

‍

Report performance optimisation   - EV-383, EV-382

An issue was filed that some reports, especially using user Tags, were getting slower and in some cases caused a system load so high that the system froze for other users. Some in-depth analysis is done on the reports executed, the used underlying queries, the data set used and based ont he analysis a number of performance improving changes have been applied.

Measurement on the reports causing the high system load after the performance optimisation show the reports are return much faster and the system load is at an more than acceptable level.

‍

Users should be prevented from requesting the same report again and again - EV-384

This issue is related to the performance optimisation issue. The analysis showed that part of the high load was caused by the fact that users got impatience and hit the report button again to retrieve the same report. This causes a snowball effect, since the first one was still running and consuming resources. And now a second request was started. And in some cases analysis showed that up to 5 equal request were fired.

To prevent users from executing the same report again, or better inform users there previous similar report request is still running, a pop-up will be shown. This will reduce the snowball effect and help in an optimised delivery of reports.

In case the user navigates away from or refreshes the page, an additional warning is shown using the default Browser information. The user can then decide if the report request will be cancelled or not.

‍

Security

An integral part of our development and build process is the automatic scanning for known security vulnerabilities. Fixes are prioritised based on impact: some may require an immediate hot-fix, while others are addressed in the current or next Sprint (release). For more information on reported vulnerabilities, see the central database of vulnerabilities.

During this release no vulnerabilities were reported that needed mitigation.

‍

Refer to the Evaluation manual for configuration guidance.

‍

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 Study guide 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 are developed in this sprint but applied to the previous release or directly to production, depending on impact.

‍

‍WCAG 2.2 compliancy improvements - SG-508

The WCAG compliancy improvements performed in the previous release left the following issue as part of the full AA compliancy requirement.

The following changes are applied:

• The environment tag should have sufficient contrast. Since the tag is not used on production environments this was not solved in the previous release.
• A skip navigation shortcut should be available as defined in the WCAG guidelines.
• The user selected language should be correctly set and accessible. The language is always set to en (lang="en"), even when another language is active. The application responds in the correct language, but a screen reader is not correctly informed about the actual selected / active language.
• Modals should be announced to screen readers.

‍

Reference setting invisible should be respected - SG-511

In case a reference value has been assigned to a field in Curriculum, and the reference value is set to 'invisible' the end result should be the value should not be shown in study guide. This was not the case, but has been solved so the invisible setting for reference values is respected.

‍

The table / list setting on the structure tab should be respected - SG-500

The configuration of the study structure tab offers the option to define the default display behaviour to be set to table or list view and which of the options should be available for the users to select from. The configuration was not correctly used by the page shown to the users, but is fixed and works as expected.

‍

Automated jobs (e.g. nightly import) should respect the timezone - SG-503

The configuration of automated jobs didn't use the correct timezone, resulting in executing a job schedule at 3:00 AM during the middle of the day. This has been fixed and the correct timezone is used that will execute a job scheduled at 3:00 AM at 3:00 AM.

‍

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.

During this release no vulnerabilities were reported that require mitigation.

‍

For more guidance on configuration and setup of Study Guide, use the relevant Study Guide manual.

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.

‍

New topbar release (update)

The release of the new topbar to Production was planned for release 12.2, but is extended with 2 weeks and will be effectuated with this release (12.3).

‍

Topbar related findings and improvements - CUR-2431, CUR-2424, CUR-2402, CUR-2403, CUR-2393

The release of the topbar to the acceptance environment has lead to a number of findings that are solved in this release:

• Search should search in the selected year. The search didn't respect the selected year, but used the year configured as the 'default year' for all search actions
• The reporting main menu should only be shown when authorised. The reporting menu and its options where not filtered based on authorisation. A user could see an option that was not authorised and only after selecting got the message 'unauthorised'. This has been fixed to only show the authorised actions.
• Process submenu should respect the sequence of the defined processes. The process menu shows the available processes. Processes can have a sequence, to define the order in which the processes are shown in the menu. The menu didn't respect the sequence, which is fixed to show the processes in the defined sequence again.
• Year switch on object should also switch the full-context year. When using the year switcher for instance on a module, the module information of the selected year is shown. When changing year, the global year selection (in the topbar) in Curriculum should also change to this selected year. The global year wasn't switched. This is fixed to keep the global year in sync with the object related selected year.
• Impersonation should be clearly visible. A new 'impersonation banner' is added to inform in case impersonation (login as ...) is active.
• Improved support on mobile with better support for the menu, navigation bar and search.

‍

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.

‍

Person dropdown should show list of persons - CUR-2441 (Hotfix)

In different situations the person dropdown was not showing a list of persons to select from. This has been (hot)fixed, to enable selecting a person from a dropdown again.

‍

Custom fields for assessment and activity-serie are shown empty - CUR-2435 (Hotfix)

Defined (and populated) custom-fields on assessment and assessment->activity-serie were shown empty after the previous release. The cause was identified and (hot)fixed to both show the data again.

‍

Team management (adding persons to a team) should be possible   - CUR-2400

The option to add a new team member (person) to a team was broken. This has been fixed to support managing the team and adding new members is working again.

‍

Managing the assessment activities should respect the configured workflow   - CUR-2386

In case a dedicated edit workflow was defined to manage the assessment activity-series, this was not used. This has been fixed.

‍

The activity grid should support creation of a new activity-serie   - CUR-2397

The option to create a new activity-serie in the activity grid is supported. Due to the changes made to extend support for multiple offerings in the same period the activity-grid has been made more robust to require an offering Id. However, in case there is no requirement for multiple offering per period and the configuration is 'older' the offering Id is not used. In this case creation of a new activity-serie results in an error.  A change is applied to also support creation of an activity-serie without an unique offering ID.

Some usability and user experience changes has been made   - CUR-2374, CUR-2369, CUR-2341, CUR-2269

A number of changes has been applied related to user interaction and experience:

• Alignment of label and value in form fields are aligned
• Reports will show information for fields of type TIME
• Reports showing 'related objects' will use a maximum column width and then switch to showing the number of related objects with a mouse-over to show all. This, instead of expanding the column.

‍

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 API should offer an option to retrieve all related programs for a module - CUR-2419

The module endpoint for Module provide the option to retrieve the module details. This includes the relation to the 'owner' study. In case a module is used in multiple different programs, there is no elegant option to retrieve these related programs from the module perspective.

A new endpoint related/{moduleId} is added to support retrieval of the related studies for a module. The result of the API call is a list studies including the identification fields uid, id, code and the name multi-lingual).‍

‍

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.

This release no vulnerabilities has been reported that require mitigation.‍

‍

Refer to the Workload Management manual for configuration guidance.

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.

‍

New topbar release (update)

The release of the new topbar to Production was planned for release 12.2, but is extended with 2 weeks and will be effectuated with this release (12.3).

‍

Topbar related findings and improvements - CUR-2431, CUR-2424, CUR-2402, CUR-2403, CUR-2393

The release of the topbar to the acceptance environment has lead to a number of findings that are solved in this release:

• Search should search in the selected year.
  The search didn't respect the selected year, but used the year configured as the 'default year' for all search actions
• The reporting main menu should only be shown when authorised.
  The reporting menu and its options where not filtered based on authorisation. A user could see an option that was not authorised and only after selecting got the message 'unauthorised'. This has been fixed to only show the authorised actions.
• Process submenu should respect the sequence of the defined processes.
  The process menu shows the available processes. Processes can have a sequence, to define the order in which the processes are shown in the menu. The menu didn't respect the sequence, which is fixed to show the processes in the defined sequence again.
• Year switch on object should also switch the full-context year.
  When using the year switcher for instance on a module, the module information of the selected year is shown. When changing year, the global year selection (in the topbar) in Curriculum should also change to this selected year. The global year wasn't switched. This is fixed to keep the global year in sync with the object related selected year.
• Impersonation should be clearly visible.
  A new 'impersonation banner' is added to inform in case impersonation (login as ...) is active.
• Improved support on mobile with better support for the menu, navigation bar and search.

‍

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.

‍

Person dropdown should show list of persons - CUR-2441 (Hotfix)

In different situations the person dropdown was not showing a list of persons to select from. This has been (hot)fixed, to enable selecting a person from a dropdown again.

‍

Custom fields for assessment and activity-serie are shown empty - CUR-2435 (Hotfix)

Defined (and populated) custom-fields on assessment and assessment->activity-serie were shown empty after the previous release. The cause was identified and (hot)fixed to both show the data again.

‍

The message 'too many characters' should only be shown when relevant   - CUR-2405 (Hotfix)

An change has been made to the handling of data that unfortunately lead to always show the message 'to0 many characters'. It was a display only, very annoying, issue, the text could still be modified and saved since the validation if the text was too long was still working as it should do. A (hot)fix is applied to only show the message when relevant, and the text is actually exceeding the define maximum character limit.

‍

The standard reporting should support filtering on datetime fields an a correct export   - CUR-2414

The  reported issue was that datetime fields were not correctly exported to Excel and CSV. This has been fixed, and while fixing it was noted that the search / filter in the report provided a limited search option for datetime fields. The search option has been extended to provide search on date, time and combinations of date and time.

‍

The description-report template should no offer filtering on year   - CUR-2411

The  description-report template provides an overview of all defined descriptions and relevant additional information on a single line per description text/language combination. A search/filter and sort option for year is shown in the report and gave an error when used. This has been fixed by disabling the (irrelevant) year sort option, since the report is only providing description information for the selected year.

‍

Field sequence should be respected during value generation   - CUR-2410

Curriculum provides extensive support for generating field values based on expressions. In these expression values of other fields can be used. In case a generated field value is based on the value of another field that is also based on an expression, the order in which the field values are generated is relevant. In this release support is added to base the order of the generated values on the defined sequence.

‍

Team management (adding persons to a team) should be possible   - CUR-2400

The option to add a new team member (person) to a team was broken. This has been fixed to support managing the team and adding new members is working again.

‍

Managing the assessment activities should respect the configured workflow   - CUR-2386

In case a dedicated edit workflow was defined to manage the assessment activity-series, this was not used. This has been fixed.

‍

The activity grid should support creation of a new activity-serie   - CUR-2397

The option to create a new activity-serie in the activity grid is supported. Due to the changes made to extend support for multiple offerings in the same period the activity-grid has been made more robust to require an offering Id. However, in case there is no requirement for multiple offering per period and the configuration is 'older' the offering Id is not used. In this case creation of a new activity-serie results in an error. A change is applied to also support creation of an activity-serie without an unique offering ID.

‍

Some usability and user experience changes has been made   - CUR-2374, CUR-2369, CUR-2341, CUR-2269

A number of changes has been applied related to user interaction and experience:

• Alignment of label and value in form fields are aligned
• Reports will show information for fields of type TIME
• Reports showing 'related objects' will use a maximum column width and then switch to showing the number of related objects with a mouse-over to show all. This, instead of expanding the column.

The defined type restriction for study -> module-group should be respected   - CUR-2349

On the different relations between studies, module-groups and modules a type-filter can be defined. It was noted the type filter configuration for the study -> module-group relation was not respected. This as been fixed, so only the defined types in the filter can be selected when adding a new main group to the study.

‍

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 API should offer an option to retrieve all related programs for a module - CUR-2419

The module endpoint for Module provide the option to retrieve the module details. This includes the relation to the 'owner' study. In case a module is used in multiple different programs, there is no elegant option to retrieve these related programs from the module perspective.

A new endpoint related/{moduleId} is added to support retrieval of the related studies for a module. The result of the API call is a list studies including the identification fields uid, id, code and the name multi-lingual).

‍

CSV import and export should support Chinese character sets - CUR-2311, CUR-2312

The import of data via CSV using the Chinese character set for string/text fields resulted in an incorrect import. The same situation occurred when exporting data from Curriculum in Excel / CSV, where the result export had incorrect data. This has been fixed by assigning the proper language (e.g. ZH) on import and export.

‍

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.

This release no vulnerabilities has been reported that require mitigation.‍

‍

Refer to the Curriculum manual for configuration guidance.

The Registration period filter has been re‑implemented to use group‑level periods with three states (Open, Closed, No date). Hourly auto‑allocate now de‑allocates students who have de‑enrolled, freeing up seats much faster than the previous nightly run.

This release is pushed to test at release date and production a week later.

Improvements

• Registration period filter re‑implemented in Allocate Overview
  • What changed: The filter now uses group‑level registration periods and offers three states: Open, Closed, No date.
  • Why: Aligns behavior with how registration is configured at group level and removes dependence on the module “Registration period set” field.
  • Next: The Registration period page will be replaced with a Registration period option under the Edit menu in the next release.
  • Note: The module‑level “Registration period set” field is now deprecated.

• Hourly de‑allocation for de‑enrolled students
  • What changed: Auto‑allocate now also de‑allocates students who have de‑enrolled on an hourly schedule, not just overnight.
  • Why: Frees up seats faster so other students can register or be allocated sooner.
  • Impact: Quicker seat turnover during the day.

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 Study guide 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 are developed in this sprint but applied to the previous release or directly to production, depending on impact.

‍

Assessment fields should return the value instead of N/A - SG-499

‍

WCAG 2.2 compliancy improvements - SG-497

Based on feedback and regular planned validation on WCAG compliancy a number of changes have been applied to Study guide to meet the WCAG 2.2 compliancy definitions.

The following changes are applied:

• Run through all pages to validate and if necessary adjust that all tabs, buttons, and links are keyboard-accessible with proper ARIA labels. The sub-tabs are extended with icon and transition support.

• Streamlined / simplified the user interface by limiting the number of buttons that were offered multiple times on the same page. Also change the breadcrumb on detail pages with a back button.

• Reduced the visual noise by removing lines in the quick-view (search result detail) and changing several box shadows with subtle borders.

• Usage of so called semantic elements for titles, e.g. h1, h2. This allows for a clearer visual hierarchy and improves understanding by reading tools.

• Used semantic elements for other elements too, like summary, details, main, footer, etc.

• Relaxed some spacing, and overall styling for a cleaner look and feel

• Improved navigation speed.

As a bonus from adjusting to WCAG compliancy, the complexity and maintainability is improved by consolidating overlapping business logic, in overview and detail components, into generic stuff.

The screenshot below shows the implementation of 'Tab' and 'Tab order' support from a usability perspective.

The list overview is cleaned and next to the tab-order support the used buttons are more clear and no longer duplicated.

Even though we perform a regular check on compliancy, we are always open for things we missed. In case in Study guide a non-matching WCAG 2.2 compliancy is identified, please sent a ticket to support, so we can pick it up.

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.

During this release no vulnerabilities were reported that require mitigation.

‍

For more guidance on configuration and setup of Study Guide, use the relevant Study Guide manual.

The release notes provide information on the features and improvements in the specified version. The release dates related to the versions are published in the Evaluation release schedule.

Improvements

New functionality, user experience refinements, and bug fixes. Issues marked as hotfix are developed in this sprint but applied to the previous release or directly to production, depending on impact.

‍

Extend mail (notification) support for Microsoft Graph API - EV-380

In this release no functional stories, but a pure technical story has been resolved. Evaluation is sending notifications (emails) to the respondents and employee stakeholders. Different options are supported having their own benefits and drawbacks.

In this version support for sending mail via Microsoft Office 365 is added by implementing the Microsoft Graph API. This will enable sending emails using this API and a customer defined/created user account in Office 365. The sending mechanism will take the Microsoft defined mail limits into consideration (max 60 per minute, max 3600 per hour and max 10000 per day).

The benefit of this mail option is that configuration on both sides is simple and straightforward from a technical perspective. For the mail receivers the main benefit is that the mails are send from the internal domain and therefor will not end-up in a spam box.

‍‍

Security

An integral part of our development and build process is the automatic scanning for known security vulnerabilities. Fixes are prioritised based on impact: some may require an immediate hot-fix, while others are addressed in the current or next Sprint (release). For more information on reported vulnerabilities, see the central database of vulnerabilities.

During this release no vulnerabilities were reported that needed mitigation.

‍

Refer to the Evaluation manual for configuration guidance.

This release adds an admin setting to control whether students can register into conflicting groups and surfaces allocation progress at a glance. It also resolves issues affecting proposals, conflict control and visibility of unscheduled groups.

This release is pushed to test at release date and production a week later.

Improvements

• Allocation progress at a glance
• The Allocate Overview now shows the number and percentage of fully allocated (completed) modules at the top. The figures respect the modules a user can access. In a future update, they will follow the current table filter.

• Conflict control setting
• Admins can now configure whether students are allowed to register to groups that conflict with reservations the student already has, this is possible to override by staff in Allocate Overview and Manage student.

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.

‍

An integral part of this release is the 12.0 release that has not been an official release, but an announcement of changes to the overall navigation and the topbar. Check the 'heads-up' information for more details.

‍

As a user I want to report on the staff assignment  - CUR-1954

For assignments there is only the page template assignment that supports the management of assignments. In this release an assignment report supporting  sort, filter and export possibilities is added to both the organisation and faculty level.

From the faculty all all assignments of the organisations related to the faculty are shown, from the organisation all assignments directly related to this organisation and organisation-children are shown in the report.

Configuration:

• Select the new page template: assignment-report
• Further configuration is done using the standard options of creating Tabs or adding pages to Workflow(s)

‍

The module copy function should provide a more extensive copy - CUR-1845

The module copy function is used to copy an existing module and its data. The copy function is extended with the copy of more sub-objects. The copy function will now copy:

• descriptions
• relations
• additionals
• offerings
• credits
• capacity
• subjects
• cost_divisions
• links
• appraisals
• method_schemas
• methods

‍

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 API support to manage non-educational tasks - CUR-1976

To enable better management of the non-educational tasks the previous release added support for importing non-educational tasks using CSV import. In this release API support is added to the standard API to upload non-educational tasks.

‍

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.

This release no vulnerabilities has been reported that require mitigation.‍

‍

Refer to the Workload Management manual for configuration guidance.

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.

‍

Processes should only be started on create  - CUR-2306 (Hotfix)

Based on the configuration it, processes can start other processes on create. In some cases this creation (start) of a new process was not only executed on create, but on any change made in the process. This has been fixed, so the start of a new process will be executed on create only.

‍

Sharing of offering based on Entity should support multi-value  - CUR-2308

When using a custom-field of type Offering -> Entity, defined as a multi-value field, this should support adding the different defined offerings as a related object(s).  Since the select didn't support multi-value, it was only possible to add a single related offering object. This has been fixed, to support selection of one or more related offering objects.

‍

The activity grid should only show activities from the selected location  - CUR-2336 (Hotfix)

On Acceptance the activity Grid and lists both showed all activities from same period offerings across different locations. This has been hotfixed, so it will not hit Production with this error, and both the grid and the list will show the activities bound to the selected period and location.

‍

Group type filter should also be used when adding a new group  - CUR-2267

The definition of the module-group custom-field supports setting a filter. This filter will not show the defined module-group types when searching for an existing module-group. However, when adding a new module-group, the filtered out types are still offered as a selectable option to the user. To prevent the user from selecting a 'filtered module-group', the selectable options when adding a new module group these values are removed from the selectable options.

‍

A borrowed module-group should be removable from the study structure - CUR-2348 (Hotfix)

An authorised user (authorisation: EDIT_STUDY_MODULE_GROUP) or even the admin was able to remove a borrowed module-group from the study program structure. This has been fixed, so the borrowed module-groups in the program structure can be managed again.

‍

An authorised user should be able to manage study -> module-group data - CUR-2310

The authorised user (authorisation: EDIT_STUDY_MODULE_GROUP) was not able to change any (custom) fields on the study -> module-group relation, e.g. sequence or required. This has been fixed, so the relationship information can be managed again.

‍

The structure page should show the descriptions for module-groups - CUR-2309

At module-group level a description can be set to be shown on the structure page as additional information to students. The description was only shown in case the structure page was defined as editable. A change is made to also show the description in case the structure page is defined as read-only.

‍

The HTML Editor should support multiple text alignment options  - CUR-2218

When configuring and using text alignment options (left, center, right) in the HTML editor, all variants were 'stripped out' and converted to standard left alignment on save. This has been fixed, so the alignment will not only show correctly in the HTML editor, but is also saved using the selected alignment type.

‍

The HTML Editor should highlight changes  - CUR-2347

Descriptions changed using the (HTML) editor didn't show all changes applied in history mode. This has been fixed, so the history view will show / highlight all changes made to the original text.

‍

The selection of module types should respect the defined sequence  - CUR-2237

The different select options of module types offered to the user didn't respect the configured sequence by the administrator. The default (fallback) options was used instead, listing the types in alphabetical order. This is fixed, and the module types will now respect the defined sequence.

‍

As a user I want to report on the staff assignment  - CUR-1954

For assignments there is only the page template assignment that supports the management of assignments. In this release an assignment report supporting  sort, filter and export possibilities is added to both the organisation and faculty level. 

From the faculty all all assignments of the organisations related to the faculty are shown, from the organisation all assignments directly related to this organisation and organisation-children are shown in the report.

Configuration:

• Select the new page template: assignment-report
• Further configuration is done using the standard options of creating Tabs or adding pages to Workflow(s)

‍

The administrator relation overview should support sorting  - CUR-2303

The administrator relation overview shows headers that look like sorting is supported. However, when clicking the header sort-order icon,  nothing happens. This has been fixed, so the administrator can now use the headers to sort the defined relations.

‍

The administrator access rule configuration should respect the relations sequence - CUR-2221

The management of the access rules shows the roles on the left hand side. The roles shown do not follow any (human) logical sort order. This has been changed to show the roles based on the defined sequence and next alphabetically.

‍

The year roll-over should copy root type of ribbon periods - CUR-2101

The year roll-over script has been extended to also copy the recent added ribbon period root-types.

‍

The module copy function should provide a more extensive copy  - CUR-1845

The module copy function is used to copy an existing module and its data. The copy function is extended with the copy of more sub-objects. The copy function will now copy:

• descriptions
• relations
• additionals
• offerings
• credits
• capacity
• subjects
• cost_divisions
• links
• appraisals
• method_schemas
• methods

‍

Scheduled scripts should us the configured timezone - CUR-2307

It was noted the scheduled scripts default used UTC instead of the configured timezone. This could lead to unexpected execution times of scripts that were thoroughly planned to run at specific times at night. A fix is made to set the timezone used by scheduled scripts to the configured timezone in the Curriculum instance.

‍

Curriculum should offer Danish and Malay language support - CUR-2315

Support for two additional languages is added to Curriculum. Both Danish and Malay user interfaces are now officially supported.

‍

Descriptions in reports should show not be shown on multiple lines - CUR-2373

Reports having descriptive fields in the configuration showed the descriptive text spread over multiple lines, instead of taking the first characters, padding with ... and offer a mouse-over to show the full text. This has been fixed, and the report is more readable.

‍

(Student) Group management

This release (student) group management has been added  as a new functionality. It should be considered as a first release, supporting one generic use case, but not covering all kind of use cases. Based on change requests, over time, support for additional use cases will be added.

The (student) group management implementation is both considered from an educational and an education logistics (planning and scheduling) perspective. Different definitions of groups are supported, including nesting to Lets first define different namings for the groups identified before we get into logistics requirements. This will provide a better option to match the requirements and validate if the division in identified group types is sufficient, should be slightly adjusted or should require additional types.

1. Group - level 1: All students starting a study at the same moment in time
2. Group - level 2: A pre-set group of students that will follow activities in the context of the program and its modules as a coherent group. Groups of level 2 are 'children' of level 1 groups.
3. Group - level 3: A group of arbitrary students identified by size only that will define the amount of students to follow a specific activity to optimize the learning experience.

Let’s look at a practical example to give it some context:

In 2025 90 students are starting the BA of Match, code BAM. Looking from an educational perspective the maximum number of students following the same activity is 90 (lecture), the minimum number is 10 (labs) and there is an intermediate size of 30 (workgroup, project, …).

Using the level strategy detailing groups from the 'smalles desired size' to the full size, the following setup using a simple naming convention could be used:

• BAM_L1 (90 students, level 1 - full size, used for lectures)
  • BAM_L2_1 (30 students, level 2 - intermediate  size, used for other teaching methods )
    • BAM_L3_1A (10 students, level 3 - small size, used for lab activities)
    • BAM_L3_1B (10 students)
    • BAM_L3_1C (10 students)
  •  BAM_L2_2 (30 students)
    • BAM_L3_2A (10 students)
    • BAM_L3_2B (10 students)
    • BAM_L3_2C (10 students)

•  BAM_L2_3 (30 students)
  • BAM_L3_3A (10 students)
  • BAM_L3_3B (10 students)
  • BAM_L3_3C (10 students)

The group definition is considered an Administrator task, including support for import of the different (student) groups bound to a program (study).

‍

Group definition and management (admin function) - CUR-2326

The (student) group definition is considered the management of a Reference. To support the different options mentioned above and the option to add additional values relevant for (student) groups to a Reference item, the Reference object model is extended. The Reference object supports the definition of additional fields to be added and management for a single Reference, e.g. type, code, name, capacity, etc.

By using the Reference as the standard all options already supported for references are available, including the CSV import, standard API (api/v2/reference) and even the option to use conditional filters/grouping.

Configuration:

Step 1 - Define the student group Reference field

The first step is creating a Reference that will be used for the group definition. In the example the Reference is named Student group.

Step 2 - Add the relevant attributes (fields)

The student group can be used as a standard reference list, with just a single value. It can also be used as an object with additional attributes. Use the Fields option to manage the additional fields to be available for the group definition. In the example a capacity and level field are added to the group definition.

Step 3 - Populate the student group Reference list

Once the Reference is correctly configured, the individual groups can be added. The defined custom-fields Capacity and Level are added. Default the Sequence, Parent and Owner are added to define the hierarchy and the owning study..

A list of the created / imported student groups is shown.

Step 4 - Assign the student group to the method -> activity-group

The new sub-object activity-group for methods and assessments is used to manage the group(s). Based on the used vocabulary, the name can be changed.

To add the option to define groups and 'store' them with the method (or assessment), add the field to contain the groups. Use a field of type Reference and point to the earlier created student group Reference.

Once the (student) groups are defined, they will be available for the user as a selectable item. The user can add the relevant group(s) to the the individual activities. Multiple groups can be added to a single activity.

‍

Calculate number of (student) groups and assign (student) groups by the user - CUR-2327

When defining the activity-serie the user defines the maximum number of students (expected) and the max group size. Based on this information the number of (student) groups required will be calculated.

A new page (activity-groups-page) is added supporting the user to define the relevant (student) groups to the calculated groups at activity level.  The page can be used as a workflow page in the activity edit worfklow.

Manage groups in bulk by the administrator - CUR-2330

The groups can be defined on individual basis by the 'module coordinator' (or corresponding role) per module and activity-serie.

Next to the manual option, a CSV import is supported by using the CSV import type ACTIVITY_GROUP. The CSV import can be used to populate the activities with the relevant groups.

To support easier management (add, update, delete groups) a new report option is added via the page template groups. Enable for instance the faculty.groups page to provide access to the group report, as shown in the image below.

The report provides the standard options, including definition of columns to be shown, save them as template, export to Excel, etc.

The exported file group information can be modified, the file can then be manipulated to match the ACTIVITY_GROUP import format (by removing some additional columns from the export), and be imported to update the student groups on the different modules and activity-series.

‍

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 API support to manage non-educational tasks - CUR-1976

To enable better management of the non-educational tasks the previous release added support for importing non-educational tasks using CSV import. In this release API support is added to the standard API to upload non-educational tasks.

‍

The sequence attribute should not be filled with 'random' values - CUR-2228

It was noted the sequence shown on screen in the structure view and the sequence returned by the API retrieving the study and its module-groups were different. Further investigation learned that the API set the order of the sequence, and so creating a order that was not specified.

Since the issue-report and underlying requirement was not only to 'remove' these sequence numbers, but that the API return would return the module-groups in the same order as shown in the user front-end (structure). So next to not creating the sequence, the sorting of the module-groups in both the front-end and the API are using the same algorithm.

‍

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.

This release no vulnerabilities has been reported that require mitigation.‍

‍

Refer to the Curriculum manual for configuration guidance.

This release builds on the Allocate Overview redesign with clearer warnings, a tidier row layout, and a faster way to review students in Student Adjustment.

This release is pushed to test at release date and production a week later.

Improvements

• Student Adjustment: “Complete allocation” filter
  • Show only students with complete allocation or those still missing allocations for the selected module.
  • Wording and design aligned with the Allocate Overview.

• Activity‑level capacity warning
  • When expanding a module, activities with insufficient capacity are clearly flagged to speed up triage.

• Consistent row layout in Allocate Overview
  • The “View students” link and the “Completed” tag are now aligned between rows for easier scanning.

• Registration and Manage Student
  • When reservations fall on a weekend, the calendar extends to include Saturday and Sunday.

Improvements

• Chinese textset is now supported in PDF exports.
• Removed "Reservation: Incomplete" status from Viewer emails.
• Clearer error message in Reserve when a user tries to create more reservations than allowed.

Bug fixes

• Reserve correctly displays reservations that span multiple days.
• Fixed an issue where reservations were not properly presented when "Date & Searched items" were shown in column headers.
• Fixed an issue where Admin → Special settings were not displayed properly.
• Fixed an issue in Reserve where recently used objects disappeared.

The Curriculum/WLM team launches typically one major version per year. There are different reasons to do this, but the moment when is always bound to a major step forward from a functional, technical or user experience perspective. Based on this, already several moment passed this year that weren't used. But this time a change is made to Curriculum that was considered the right one for a new major version.

The next release (published October 31, 2025) and its related release notes are similar to all other release notes, with issues mentioned under the section improvements to be considered as new functionality, user experience improvements or bug fixes. Issues marked as Hotfix were developed during this Sprint release and  already hotfixed to the previous release or direct to production based on the impact of the issue.

In order to not 'clutter' the release notes with the change that lead to a major version, this special release note / heads-up is published, only focusing on the new major feature. The new feature focusses on improving and standardising the overall user-experience over the different TimeEdit products. In the past period minor and medium changes have been made, but this release focussed on a complete redesign of the topbar navigation.

‍

Extended feedback period and 'solution' time reservation

One of the reasons it is marked as a major release and a separate release-like heads-up is published is because a change to the navigation may have impact on users, or just ask for additional testing or updating user documentation.

To cater for this, the new Topbar will be released and available on Acceptance for two release cycles. This allows to perform the necessary steps and be prepared for the release and enablement of the Topbar in production.

Even though the changes are thoroughly tested, experience tells that due to the nature of Curriculum with all its flexibility not all paths used by customers in their own application can be / are covered. This means we have reserved capacity and priority to issues found related to the new Topbar, to provide a smooth path to the production release.

The new topbar is already available in the 11.24 release, but the activation has been stalled till the heads-up. This means that already in the 11.24 release the new topbar can be validated and continued starting from the 12.0 release (will be released this Friday).
The official release to production is planned as an integral part of release 12.2 (Check the Curriculum release schedule).

‍

The new topbar navigation

The topbar navigation assists the user in navigating and using the application. The topbar will become available in all TimeEdit products, to provide a standardised behaviour and user experience over the different products.

The image below shows the new topbar, supporting at least the same functionality as the 'old' one. In the next sections the different components in the topbar will be detailed. The bigger changes will be clearly stated.

A major change in the Topbar is that the navigation is outlined to the left, instead to the right.
Visually the different components are standardised to the TimeEdit overal design with a more logical location of 'buttons' and functions, usage of icons for easier identification, including highlight of selected (menu) items.

‍

The product switcher

At the top left of the Topbar there is the so-called product switcher. The product switcher standard shows the product the user is currently working with. In this case Curriculum.

The user can click on the product switcher (icon + name) to unfold a list of all applications available for the user. The applications will differ per customer, so the image shown is just an example of a special configuration. The user can now select another product and switch directly to that product and continue working.

Right of the Product switcher the customer logo, name of the environment and in case of non-production systems an indicator of the system type (in this case Beta).

‍

Navigate the menu

Before moving to the right, first the menu will be covered. As already said, the major change in the menu is the outlining for right to left.

Depending on the configuration the user will see the different menu-items. The currently selected main-menu and sub-menu will be highlighted. In this case the Dashboard is selected, and the user opened the 'Personal' menu-section. After selecting a menu in the Personal section, Personal will be highlighted. The provided menu options Personal and Report are different compared to the 'old' menu, the changes are highlighted in the next two sections.

Personal menu

The Personal menu is a new menu that provides direct access to the logged-in person related information. In the 'old' menu this was hidden in the right top-corner when clicking the person icon. To provide a more intuitive path, the Personal menu is introduced.

For historic reasons, the access to the Personal information is still available via the person icon in the right-top corner.

The sub-menu items shown are, as probably already expected, based on configuration. The sub-menu's shown are the menu items defined as Tabs of type Person.

Release 12.1 will add support to show/hide the Personal tab using the default Pages option.

‍

Reports menu

The reports menu has been changed slightly. The access to the processes is at the main-level grouped and on the next level the process information desired needs to be selected. Furthermore the unfolding of the different process types and processes is looking more crisp, but from a navigation perspective it is the same.

Another change is move from the Inventory menu to be part of the Reports menu. The Inventory used to be a section with it's own menu at top-level, but since it is more related to reporting it has been moved to keep a cleaner main menu and defined the functionality at logical places.

‍

The year switcher and simulations

From the menu, let's move to the top row functions. For now we skip the 'search', that is not yet migrated to the new look and feel and new search options.
The first top row function is the year switcher. This has been moved to the top bar, which is a more logical location from a usage perspective.

The basic functionality of the year switcher has not changed. The usage icons and colour highlighting is added to provide better visual information to the user.

When selecting the Manage simulations options a sub-menu is unfolded showing the personal defined / accessible simulations and the option to create a new simulation or manage the existing set.

The simulation management is extended to not only show a list of all defined simulations, but the option to navigate between the years the simulation is defined for (Based on year) and the option to filter / search for simulations with a specific name.

Notifications

The next menu is the icon and it's indicator showing the number of 'unread' notifications. When clicking the notifications icon, the list of notification is opened. The visualisation has been changed, based on feedback received from customers.

An indicator (green bullet in the screenshot) is added to indicate if a notification is read or not. The background colour of the notification is uses as a highlight with the same function (read or not).

The notifications are shown including the send date and the first part of the body text. By clicking the notification the body text will be unfolded.

The user can remove an individual notification using the 'dust bin' icon.

The notifications sub-menu (icon with the three dots) provide additional filter and management options to steer the information shown. The different options are self-explanatory.

Language switcher

The next menu is the language switcher. In line with other functions, this is styled as a switcher that is opened when clicking the language (globe) icon or the language abbreviation text (EN).

This is a change from the 'old' topbar where all supported languages where shown in the header, potentially consuming quit a lot of space in case different languages were supported.

Personal information

The final menu is the personal information, offering the user the option to navigate to the personal information and configure specific behaviour. A non-admin user will not have access to the sub-menu options Debug mode and API Token, and will only see the other ones.

The sub-menu Details is navigating to the Person information defined in Curriculum. This is the 'old' way of navigating still supported, but is now also available via the Personal menu in the menu-section.

From a functional perspective no changes are made, only the visualisation of the menu leading to the underlying page.

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 Study guide 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 are developed in this sprint but applied to the previous release or directly to production, depending on impact.

‍

Import should not fail on usage of symbols - SG-494

The import of Study guide from Curriculum failed in case symbols were used in a code. The request to get the data based on the code failed as did the import. A fix is applied to support importing data from Curriculum with codes having symbol (characters).

‍

The definition of a new field should not select the first reference type - SG-495

When configuring a new field in a widget, the ‘reference type’ selector always selected the first reference option. This was caused by the fact  there was no empty option. A fix is applied to add the empty option to the list and no longer select a reference option.

‍

The selection between table or list view in structure should be global - SG-325

The Table/List switcher on the structure page was shown for each top-level or nested group, which creates a busy interface and duplication of code. From a usability perspective the change is made to move the toggle to the the top of the page (similar to already used in overview pages).

‍

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.

During this release no vulnerabilities were reported that require mitigation.

‍

For more guidance on configuration and setup of Study Guide, use the relevant Study Guide manual.

This release simplifies dedication by removing capacity splits, makes non‑scheduled options visible by showing groups without reservations, and prevents de‑registration from hidden‑all‑groups activities when students are already allocated. We also sharpened the Allocate Overview to clearly separate capacity from allocation status.

This release is pushed to test at release date and production a week later.

Improvements

• Dedication simplified
  • Dedicate entire groups to one or more student categories without managing capacity splits. Existing dedications still apply, but the capacity value is ignored.
  • Benefit: Quicker setup and fewer configuration errors.

• Visibility of non‑scheduled options
  • Groups without reservations are now shown in Registration and in Manage student List view.
  • Example use: Offer a choice between attending a lecture in person or a recorded version.
  • Benefit: Support registration and allocation to options that aren’t timetable‑based.

• Safer de‑registration behavior
  • When an activity has all groups hidden and a student already has an allocation, de‑registration is prevented.
  • Benefit: Avoids accidental loss of necessary allocations during configuration windows.

• Clearer Allocate Overview
  • The table now highlights Capacity and Allocation separately.
  • Benefit: Faster scanning to spot mismatches and issues.

• Linked‑group warnings could appear erroneously when data saved in varying order. Fixed.
• Students with multiple category values failed to match dedication rules. Fixed.

The release notes provide information on the features and improvements in the specified version.  
The release dates related to the versions are published in the Evaluation release schedule.

Improvements

New functionality, user experience refinements, and bug fixes. Issues marked as hotfix are developed in this sprint but applied to the previous release or directly to production, depending on impact.

‍

The Excel and SPSS export should contain evaluation tags - EV-377

Both the Excel and SPSS export only provided the member (student) tags, and were missing the so-called evaluation tags like faculty and study. Both the exports have been adjusted to contain both the member and the evaluation tags.

‍

Generating SPSS export should not give a system error - EV-378

Large SPSS exports could give a system error. Analysis of the log files learned that the cause was that the SPSS generator ran out of memory. A change is made to allow the SPSS generator to consume more memory and generate these large reports.

‍

Security

An integral part of our development and build process is the automatic scanning for known security vulnerabilities. Fixes are prioritised based on impact: some may require an immediate hot-fix, while others are addressed in the current or next Sprint (release). For more information on reported vulnerabilities, see the central database of vulnerabilities.

During this release no vulnerabilities were reported that needed mitigation.

‍

Refer to the Evaluation manual for configuration guidance.

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 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 should have better insight in the custom-fields - CUR-2126

A request heard multiple times it an option to get easier / better insight in the defined custom-fields in the system. Especially for systems that have defined a large number of custom-fields on study and module level a more report-like overview showing all information defined will provide more insight. The standard custom-field management provides the support to define, change and detail the custom-fields, but is not designed to provide extended reporting providing detailed insight in the defined custom-fields.

The request is focussed on providing the desired insight with the following extension to the currently provided functionality:

The custom-field definition should track ‘creation’ and ‘modification’ timing informationIn case a custom-fields is defined or updated no timestamp information is stored. To provide better insight in what has been changed timestamp information is added to the custom-field definition. The timestamp information should be available in the report and allow for sorting / filtering of the custom-fields, e.g., show all custom-fields defined or modified since March 16.

A reporting option should be available to report, search and filter on the custom-fields
A report option has been added using the 'standard reporting options' available for users to report on all defined custom-fields. By using the standard options, there is support for search, filter, (de)selecting attributes to be reported, definition of own templates and exporting the result.

A new menu-option is added to the Administrator menu (bottom section) to support reporting on the custom fields, as shown in the image below.

The basic filter of the report has the options:

• Root type: defines what object should be reported, e.g. study, module, faculty, ...
• Entity type: defines the sub-object, e.g. additional, offering, ... If no entity type is defined all fields will be shown.
• Visible: option to leave out (or only report on) custom-fields that are marked as invisible.

‍

The planboard should only show the related study subjects - CUR-2256

Using the planboard to visualize a study with its modules and related subjects showed all subjects defined on the modules. The planboard should show only the subjects that have been defined at study level. This has been fixed, so the planboard will only show the study related subjects.

‍

The appraisal page should only show the relevant buttons - CUR-2242

The appraisal page shows a number of buttons (start, copy, delete) that looks as if they have no use. The start button has been removed and the copy and delete button can be made (in)visible using configuration.

Configuration of the appraisal page-template:

- Hide generation: enable the checkbox to hide the Delete and Copy button.

‍

As a program responsible I want to define module -> study relation information - CUR-2125, CUR-2261

In the previous sprint the functionality to support the definition of attributes on the module -> study relation has been added (CUR-2125). The story focussed on the registration of the information only.

The follow-up story implementing the more 'under the hood' functionality have been added:

• Option to configure module->study fields as fields to be shown in the structure tree
• CSV import support for study-module
• Extend the module endpoint in the API to return the module->study relation information

‍

‍Auto-generated email address no longer generated / shown in reports - CUR-2185

There was some customer specific logic in the application that automatically generated an email address in case the email address was not provisioned. This logic has been removed.
From an architectural design perspective the custom code should be limited and the source system (in this case the system that provisions users) should provide the email addresses.

Based on standard configuration it is still an option let Curriculum generate the email address, using a standard formula and a hook configuration 'generate value' that will kick-off the formula.
The image below shows the formula that will use the provided email, or else create an email based on the externalId and a @timeedit.com suffix.

Ad-hoc periods should always allow modification - CUR-2162 (Hotfix)

The option to lock offerings for edit added in the previous version was a too strict for ad-hoc offerings and causes them to be locked for edit always. A change is made to 'unlock' the ad-hoc periods and always allow modification.

‍

Report download broken - CUR-2297 (Hotfix)

The report download option didn't create a download anymore. This has been fixed to support downloads again.

As an administrator I want to configure default setting for reports  - CUR-2217

A functionality already supported for some other report page-templates is the support to configure a default template to be used and prevent the user from switching the template. In this version this configuration is added to the report templates task-report, availability-report, method-report, effort-report and appraisal-report.

Choice rule should distinct between rule and value  - CUR-2217

Always good to have a little anoying bug that feels so insignificant it might be there for a long time but is never reported. This is probably a highlight in this category. In case a rule definition is used on a module-group to express for instance that 4 of the underlying modules need to be select the information shown would be 'Choose exact4'. The rule and the value were concatenated. This has been adjusted to improve readability and will now show 'Choose exact 4'.

‍

Multi-value fields should be shown readable on a read-only page - CUR-2196

In case a form page is defined as read-only that has a multi-value field configured, the multi-value data was shown in an 'unreadable' way. All values were concatenated into one long string.
To improve the usability and readability the display of multi-value fields on read-only pages is changed. The values will be shown as a bullet list with a single bullet for each defined value as shown below.

‍

The expansion status of the curriculum mapping matrix report should be kept  - CUR-2105

When using the curriculum mapping matrix reports, the information can be expanded. In case some filter or option is changed that requires refreshing of the data, the current expand status is reset. The matrix will be shown in fully collapsed mode.
A usability improvement is made, where a change in a filter or option will refresh the data, but will also keep the matrix in its current status regarding expanded information.

‍

Faculty report should allow mouse-over on truncated texts - CUR-2254

In case information in the faculty report doesn't fit the column, the text is truncated and extended with 3 dots. This is the standard approach in all reports. Missing was the mouse-over to enable viewing the full text. This has been added to the faculty report.

‍

As an admin I want to cleanup my 'test configuration' - CUR-2127

During configuration of the system a lot of ‘test configuration’ may be added and used to play around with processes and data. This configuration will clutter the system, since it cannot be deleted due to the basic architecture and design of Curriculum. The base is that information can never be deleted, since one of the Curriculum results is a full audit trail to trace all modification proposals till final approval into extensive detail.

This principle is built in and adhered to in all environments (test, acceptance, production), limiting the option to remove (configuration) data that is related to actual educational objects.

A feature request to support a kind of 'force delete' that overrides the basis principle should support the deletion of the following configuration elements:

• Custom-fields
• Pages
• Workflows
• Processes

Functionality to support the force delete is added, adhering to the rules:

As a system I will NEVER support deletion of the above-mentioned configuration objects in production

The option to enable the force delete of configuration option a config-setting can be used. The config setting will NOT word on systems marked as 'production'. This to limit the risk of accidental removal of data related to configuration objects in a production environment that is based on the earlier mentioned architecture and design principle.This implies that support for deletion can only be configured on test and acceptance.

Configuration:

- In the Administrator / Config menu set the environment.allow_force-delete option to true to enable the force delete option,

As an administrator I can delete custom-fields

The delete will be shielded with an ‘are you sure’ and a field to type in the custom-field name to prevent accidental deletion of a custom field.

• In case the custom-field has data attached, the related data will be removed from the system.
• In case the custom-field has data changes attached, the audit trail data will be removed from the system.
• In case the custom-field is shown on a page, the custom-field will be removed from the page.
• The custom-field will be deleted, once all the data / relations are removed

As an administrator I can delete custom-pages

The delete will be shielded with an ‘are you sure’ and a field to type in the custom-page name to prevent accidental deletion of a custom page

• In case the page is used in a workflow, the page will be removed from the workflow.
• The page will be deleted, once the relation to workflows / tabs are removed

As an administrator I can delete workflows

The delete will be shielded with an ‘are you sure’ and a field to type in the workflow name to prevent accidental deletion of a workflow.

• In case the workflow is used in a process, the workflow will be removed from the process.
• In case the workflow has related transition information, this data will be removed from the system
• In case the workflow has related tasks (active / inactive), the task data will be removed from the system
• The workflow will be deleted, once all the data / relations are removed

As an administrator I can delete processes

The delete will be shielded with an ‘are you sure’ and a field to type in the process name to prevent accidental deletion of a process

• In case the process has related transition information, this transition data will be removed from the system
• In case the process has related tasks (active / inactive), the task data will be removed from the system
• The process will be deleted, once all the data / relations are removed

‍

Reports should support search on date fields - CUR-1938

The search option in the standard reporting option didn't support search on full dates. This has been fixed, to add support for searching on dates in the different reports.

‍

Multiple offerings in the same period should be available as alternative offerings - CUR-2024

When defining multiple offerings in the same period, e.g. using different locations, on a module, these cannot be differentiated in the alternative offerings on study structure level. A change is applied to enable distinction of the double offerings and support the differentiation and selection of alternative offerings from the study structure level.

‍

As an administrator I want to configure if custom-fields on objective are required - CUR-2247

This is an issue related to curriculum mapping, where when adding / editing an objective on a module subject and/or an assessment can be added to this objective. The configuration option of the fields support the option to mark the field as required. The change applied in this version is that the 'required' setting will be evaluated and respected.

‍

Order of offerings should be consistent - CUR-2186

The different page-templates showing offering information didn't use the same sorting mechanism. From a usability perspective this is not desired. A change is applied to all page-templates to use one standard sorting mechanism showing offering information.

‍

A condition defined on the method category should be respected - CUR-2263

The method category offers an option to configure a condition, e.g. only show the method category in the context of one faculty. The configuration option was there, but the evaluation of the condition wasn't. This has been fixed, so in case a condition has been defined on the method category it will be respected.

‍

Vacancies should be manageable from the vacancy list - CUR-2295 (Hotfix)

The option to view and/or edit a vacancy from the vacancy list was broken and didn't open the expected form, but showed a technical error. This has been fixed, so management of vacancies from the vacancy report is working again as expected.

‍

As an organisation (department) manager I want to see my contribution to programs - CUR-1937

A new report-template has been added named 'tasks-contribution' that enable reporting from an organisation perspective, displaying all studies and hours per study the organisation contributes to.

The hours per study is the sum of the hours on modules, groups, activities for all staff members of the department (and its children).

‍

As an administrator I want to configure custom-fields on educational tasks, that can be used by users - CUR-2243

In order to support better management, allocation and reporting of tasks outside the context of the curriculum structure, support has been added to define custom-fields on educational tasks. This will support adding additional attributes on tasks that can be used for the different overview. A practical example could be to get an overview of all tasks that are related to the project 'A brand new day'.

The administrator will add a custom-field to the Task object definition. Any custom-field can be added, e.g. a list of all projects, including the standard options to steer display, apply conditions, add info labels, etc.

The user will have access to the field when creating or managing a Task. Based on the example provided, the user can search and select the list from the defined list

The user can report on tasks, and using the standard reporting options can add the 'project' field to the report, filter on the project 'A brand new day' to get an overview of all tasks defined in the context of this project. The user can save the report as a template, or export to CSV or Excel.

‍

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.

‍

OOAPI data exchange to RIO and eduXchange should have consumer data - CUR-2266

The OOAPI data standard defines the fields that are expected or even required when exchanging data with eduXchange an RIO. For customers that started using the data-broker implementation, to limit load on Curriculum and speed up processing of data, the consumer data was not complete. This has been fixed, so the OOAPI implementation based on the broker API will now correctly populate the consumer object.

‍

Extend error reporting on data export (integration) - CUR-2294

When using the export / event-based integration option to exchange data to an external system the basis setup of the message and what to return in case of an error is well-defined. It was noted that in some cases the integration got stuck and returned an error without being a direct technical HTTP error and without reaching the external system that would adhere to the standard and return the defined message.

A change has been applied to be less strict on the return message that are not sheer technical or from the external system, but got stuck in the middle and return a different format. The returned message will be logged and shown, which will help in identifying the root cause of the failure.

‍

Extend CSV support to manage non-educational tasks - CUR-1976

To enable better management of the non-educational tasks a number of changes have been made that allow importing non-educational tasks using CSV import.

The CSV support is provided by using the 'TASK' import and provide the fields:

1. year - the year the tasks should be applied to
2. task_id - unique identifier of the task as present in an external system, e.g. the HR system
3. assignment_id - unique identifier of the assignment/contract
4. template_id -  type of task , e.g. admission committee
5. description - text to provide textual context
6. correction - decimal value to define if more or less hours are applicable

In the next release API support will be added to the standard API.

‍

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.

This release no vulnerabilities has been reported that require mitigation.‍

‍

Refer to the Curriculum manual for configuration guidance.

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.

‍

Reports should support search on date fields - CUR-1938

The search option in the standard reporting option didn't support search on full dates. This has been fixed, to add support for searching on dates in the different reports.

‍

A condition defined on the method category should be respected - CUR-2263

The method category offers an option to configure a condition, e.g. only show the method category in the context of one faculty. The configuration option was there, but the evaluation of the condition wasn't. This has been fixed, so in case a condition has been defined on the method category it will be respected.

‍

Vacancies should be manageable from the vacancy list - CUR-2295 (Hotfix)

The option to view and/or edit a vacancy from the vacancy list was broken and didn't open the expected form, but showed a technical error. This has been fixed, so management of vacancies from the vacancy report is working again as expected.

‍

As an organisation (department) manager I want to see my contribution to programs - CUR-1937

A new report-template has been added named 'hour-contribution' that enable reporting from an organisation perspective, displaying all studies and hours per study the organisation contributes to.

The hours per study is the sum of the hours on modules, groups, activities for all staff members of the department (and its children).

‍

As an administrator I want to configure custom-fields on educational tasks, that can be used by users - CUR-2243

In order to support better management, allocation and reporting of tasks outside the context of the curriculum structure, support has been added to define custom-fields on educational tasks. This will support adding additional attributes on tasks that can be used for the different overview. A practical example could be to get an overview of all tasks that are related to the project 'A brand new day'.

The administrator will add a custom-field to the Task object definition. Any custom-field can be added, e.g. a list of all projects, including the standard options to steer display, apply conditions, add info labels, etc.

The user will have access to the field when creating or managing a Task. Based on the example provided, the user can search and select the list from the defined list

The user can report on tasks, and using the standard reporting options can add the 'project' field to the report, filter on the project 'A brand new day' to get an overview of all tasks defined in the context of this project. The user can save the report as a template, or export to CSV or Excel.

‍

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 and update of non-educational tasks - CUR-1976

To enable better management of the non-educational tasks a number of changes have been made that allow importing non-educational tasks using CSV import.

The CSV support is provided by using the 'TASK' import and provide the fields:

1. year - the year the tasks should be applied to
2. task_id - unique identifier of the task as present in an external system, e.g. the HR system
3. assignment_id - unique identifier of the assignment/contract
4. template_id -  type of task , e.g. admission committee
5. description - text to provide textual context
6. correction - decimal value to define if more or less hours are applicable

In the next release API support will be added to the standard API.

‍

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.

This release no vulnerabilities has been reported that require mitigation.‍

‍

Refer to the Workload Management manual for configuration guidance.

This release makes the Allocate Overview easier to scan by sorting activities and groups in a clear, predictable order. It also improves the guidance you get in allocation proposal when recommendations are not met for linked groups, so issues can be resolved quickly.

This release is pushed to test at release date and production a week later.

Improvements

• Allocation proposal: If selected linked groups do not follow the recommended configuration, the proposal is now cancelled with an actionable message that explains what is missing and how to fix it.

• Allocate Overview sorting: Activities and groups are now sorted alphanumerically, giving a logical and consistent order across modules and within each activity.

This release focus mainly on improving the data collection and prepation process, making the process less error-prone and thus ensuring higher data quality when scheduling.

Improvements

• Activity padding is now supported when submitting activities from Preferences to Data Manager, when importing activities into Data Manager as well as editing padding directly on the activities in Data Manager.

• Reject Submission Activities Deletion: Ensure that when a submission is rejected, all associated scheduled activities are now reliably deleted
• When sending activities from Data Manager to Activity Manager, we now forcing to sebd all activities belonging to the same module (instead of allowing sending partial activity sets as allowed before)
• Adjusted the logic for activities are grouped when sending activities from Activity Manager to Data Manager to use the same consistent grouping logic currently used when sending actitivities from Data Manager to Activity Manager or to Preferences. It will now be more error-proof to send activities back and forth across the process without accidently introducing data inconsistences. 
• New filtering possibilities for Study Combinations, both in the Review by Study Combination and Generate Student Set views, where you can now filter by Module/Course. This will signifcantly users to  find the relevant Study Combinations for several different operations.

Smaller fixes

• Help Center Link Update: Change help center link to https://www.timeedit.com/learn

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 Study guide release schedule

Improvements

The issues in release mentioned under the section improvements are considered as new functionality, user experience improvements or bug fixess

‍

Defined rules should be shown - SG-492

The rules, e.g. prerequisites, defined in Curriculum were not shown in Study Guide. This has been fixed, to the defined rules in Curriculum are properly shown in Study Guide to inform the student on any pre-requisites, co-requisites or other defined rules.

‍

The study->subject widget should support filtering - SG-489

The Subject widget shows all defined subjects on a study, irrelevant of subject category or subtype. A new filter option has been added to the configuration of the Subject widget to support distinction between category and subtype combinations and thus define multiple widgets supporting the different desired combination.

The options added to the Subject widget configuration are:

• Widget field modal has been reordered for clarity and consistency. Now has a reference type select dropdown.
• Subjects widget field now supports filtering on subject category and type, just like the MATRIX widget did already. E.g. reference.type=Lo&reference.subType=Vor reference.type=Lo&reference.subType=WW,VO to show multiple categories.

‍

Enable configuration of the assessment title in the Appraisal widget - SG-483

The title / name of the appraisal shown in the appraisal widget was hard-coded set to the appraisal code.  From a study guide user perspective the code is not always the most 'informative'. To improve the information provided a configuration option is added to configure the title / name shown.

Configuration:

The first field in the appraisal widget will be shown as the title/name. To add a custom title, perform the next steps.

•  Add a field to the appraisal widget- Type: VALUE- Fieldname: title- Sequence: 0
• Define the desired format using the standard convention of ${field_name}{assessment.code}) (${ILOassessed}) - ${type} -> LV: ${Assessment_Length_Value}

To allow more flexibility, the format definition supports both appraisal and assessments fields, including already separate defined fields ones based on a reference type.

The information shown will be based on the configured title field and format

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.

This release the mitigated vulnerabilities are:

• CVE-2025-7783 (9.4)
• CVE-2025-58754 (7.5)

‍For more guidance on configuration and setup of Study Guide, use the relevant Study Guide manual.

The release notes provide information on the features and improvements in the specified version. The release dates related to the versions are published in the Evaluation release schedule.

Improvements

New functionality, user experience refinements, and bug fixes. Issues marked as hotfix are developed in this sprint but applied to the previous release or directly to production, depending on impact.

Condensed reports should work independent of number selected filters - EV-375 (Hotfix)

Due to the added option that allows using report filters on condensed report, depending on the number of filters selected the generated request could exceed the maximum URL length. This has been fixed, so the report will show independent of the number of selected filters.

‍

Response percentage should take all evaluations into account - EV-374

The summed reports show the calculated response percentage of all selected evaluations. However, in case an evaluation has no responses or too few to allow reporting, it was not used in the calculation of the average response percentage. This causes the response percentage to be higher than it is. A fix is applied to calculate the average response percentage based on all selected evaluations including the evaluations with no or too few responses.

Labels are not always shown when opening a report - EV-364

A rare case where on a specific version of Microsoft Edge the labels are not loaded correctly. Development didn't succeed in replaying the issue and based on the issue and an analysis what could cause the issue or help in identifying the cause, some changes have been made to the load timing and additional front-end logging is added. The timing change can have solved the issue, and if not, the logging will help in identifying the cause.

Security

An integral part of our development and build process is the automatic scanning for known security vulnerabilities. Fixes are prioritised based on impact: some may require an immediate hot-fix, while others are addressed in the current or next Sprint (release). For more information on reported vulnerabilities, see the central database of vulnerabilities.

During this release no vulnerabilities were reported that needed mitigation.

‍

Refer to the Evaluation manual for configuration guidance.

This release streamlines linking groups at the activity level and enforces recommended linked‑group rules across key workflows to prevent invalid allocations and registrations and allows you to control reservation statuses to use.

This release is pushed to test at release date and production a week later.

Improvements

• Bulk link groups at the activity level
  • Link once per activity instead of group by group.
  • Faster setup with fewer clicks and fewer mistakes.
• Enforced linked‑group recommendations across workflows
  • Prevents allocating or registering students into linked groups that do not meet the recommended configuration.
  • Applied in Registration, Manage student, Manual allocation, and when generating allocation proposals.

• Conflict control: In Admin, Allocate Reservation Filter you can now configure the filter for reservation statuses that Allocate should show in graphical views and use for conflict control. Previous hardcoded setting will be used as default, until the setting has been updated.Default settings are

  Complete, Confirmed, Rejected, Incomplete, Requested

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 a department manager I want to approve ad-hoc absence requests - CUR-2034

(Un)availability management of staff members is standard supported in different means. The until this release supported (un)availability was based on generic setting steered with the weekly availability pattern or a number or percentage of unavailability hours in the context of workload.

The image below shows the user screen to define the weekly availability pattern.

In this release the option is added to support the request of 'ad-hoc' unavailability by a user and the approval by the HR manager.

A new screen is introduced called 'unavailability', that can be added to the user Tab settings as shown in the image below, but can also be added into a workflow to gather 'ad-hoc' unavailability prior to the semester start.

The user is shown an overview of the ad-hoc requests done and their status. The user can define additional ad-hoc unavailabilities by clicking the Add button.

The user can specify:

• Start and end date
• Start and end time
• Type, allowing to define if it should be set als unavailable, available or rather not
• Description to define the reason for the absence

The HR manager will have access to the Absence report (unavailability-report) that will show an overview of the the staff unavailability request.

The image below shows the standard view. The HR manager can filter on date to select only request that have been filed between specific dates, or on status to only see the 'open' requests (or the approved / rejected ones).

The HR manager can use the toggle buttons to 'select all' or 'select one/more' requests from the list. In the image below the HR manager selected one request. Once selected the Approve and Reject button appear to enable the HR manager to manage the request.

In case the HR manager approves the request, a pop-up appears that allows the further handling of the request. The HR manager can decide to just accept and without providing any additional information and handling, but can also decide the absence should both have effect on the availability in scheduling and in the availability of the person in relation to workload.

In the image below the latter is chosen. The HR manager has marked that for this request a 'task' should be created that will have effect on the total availability of the person. The request should be marked and saved as an ad-hoc absence task in the users profile. The amount of hours is calculated based on the request, but can be adjusted at this moment.

If we then look at the users profile, we notice a task has been added in the section 'Absence'. The task size is 16 hours and this 16 hours will be deducted from the total available hours for the person.

This means that an unavailability 'marked' as task will lead to an additional deduction of hours, next to the standard user availability hours that already has deducted the contract defined leave hours.

Buttons to manage activities in the activity-grid should be accessible - CUR-2164

The activity grid shows a visual representation of the desired teaching layout (activities). The activity-series and activities defined can be managed using the buttons shown in the tile. However, in case a long(er) activity name was used, the name was positioned on top of the buttons, making them inaccessible. A change is applied to truncate the activity name and not float over the button. The button is now always accessible and the full name of the activity is available using mouse-over.

As an administrator / implementation manager I want to brand the used product - CUR-1993

The Workload management and Curriculum product partly use the same configuration and administration interface. Using the administration interface the 'branding' of the product can be defined and differentiate between the Workload management or Curriculum branding.

Configuration:

Navigate to the Administration -> Config menu option

1. Set the 'header.workload-product' to true to use the Workload management branding
2. Set the 'header.workload-product' to false to use the Curriculum branding
3. Optional set the 'header.product-switcher' to activate the TE product switcher including the branding selected

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.

This release no vulnerabilities has been reported that require mitigation.‍

‍

Refer to the Workload Management manual for configuration guidance.

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 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.

In-line module-group descriptions should support multi-lingual - CUR-2157

The structure page offers support to 'in-line' change the informative description for module groups, e.g. you have to select 6 credits from the underlying modules. This description field was available as a multi-value field, but only manageable at the module-group.

A change is made to support management of all supported languages direct from the structure page, instead of only one language.

Organisation report should support opening organisation details - CUR-2232 (Hotfix)

The navigation from the organisation report / overview to the underlying organisation details was broken. This has been (hot)fixed, to enable navigation to the visualisation and management of the organisation details via the organisation report.

Assessment related credits not shown - CUR-2225 (Hotfix)

Implementations using a self-defined custom-field to define assessment related credits didn't correctly show and validate the credits. The credits used to validate if the total defined credits on the assessments matches the defined credits at the module was always incorrect, since the assessment credits value used was 0. This was caused by the fact that the credits has been moved to a Curriculum default field, and the existing data for this implementation wasn't moved. For the implementations affected the existing data has been migrated to both show the correct credit value at assessment level and use this value in the calculation.

As a user I want to remove (shared) methods from the method-tree - CUR-2235 (Hotfix)

Due to a change in the previous version it was no longer possible to move a 'shared / lend' method from the method-tree that has lend the method from another module. This has been (hot)fixed, to support removal of lend methods again.

Only the owner should be able to edit an assessment - CUR-2295 (Hotfix)

In case an assessment was lend from another module, the lending module owner could change the activity-serie of the lend assessment. This has been fixed to only allow changing of the assessment and its activity-serie(s) by the owner.

As an administrator I want to lock management of an activity-serie for an offering period - CUR-2124

In case a module is offered twice a year, e.g. Semester 1 and Semester 2, and the process to manage the module activity-series is run twice a year, a user can both modify the information defined for Semester 1 and Semester 2. The requirement is that it should be possible to 'lock' (disable any editing) the defined information for Semester 1, when the process is run for Semester 2.

A configuration option is added to the Academic year - Period configuration to define a 'lock date' per Period. This allows for setting a lock date upfront, that will be used to enable editing of the activity-serie based on the selected period. In case the defined date is passed, the activity-serie will be locked and shown as read-only to the user.

Reset button shown for module with a changed code - CUR-2205

In case the module code of an existing module is changed, a 'Revert code' button is shown in the workflow of all stakeholders involved in the process that allows to revert the code back to the original code. The requirement is to not show the 'Revert code' button. To support the requirement, and additional configuration option is added to either enable or disable the showing of the 'Revert code' button in the workflow.

Configuration (Administrator -> Config menu):

• changes.show_revert_code = true / false

Deleted subjects should not be shown (in bulk select) - CUR-2187

When using bulk select on subjects, the deleted subjects at study / specification level were still shown. This has been fixed, so only the 'active' subjects are shown and available for bulk select.

The process manager should show all specifications in the selected year - CUR-2207

The process manager only showed the specification with a data equal or before the start date of the selected academic year. Specifications starting during the year were not shown. A fix is applied to extend the specifications shown in the process manager by validating if the specification is valid within the academic year. Thus validating if the start date of the specification is between the start and end date of the selected year.

Deleted offering periods should not be shown in the route planner - CUR-2159

In case a route (study path) is defined with the relevant offering and the offering is removed from the module, the offering was still shown in the route as if it was active. A change has been made to the route-planner to visually inform the user the defined route is using an invalid offering. Instead of 'not showing' the removed offering, the offering will be shown as 'strike-through' to indicate the original defined route for the module - offering combination is no longer available and requires a change.

As a program responsible I want to define module -> study relation information - CUR-2125

A feature request has been filed to support the definition of attributes on the module -> study relation. This would be similar to the module -> module-group relation, where you can define information specific for a relation between an individual module and a module-group. A practical example would be that module A is required in module-group B and not required in module-group C and D. The required attribute is in this case defined on the relation between a module and its module-group.

A similar option should be available to support the definition of information on the relation between a module and the programme offering the module. To support the definition and management of the module-study relations it is required that information can be defined and managed on the relation from a module with the offering programme. To offer a broader support then just the module-study relationship information the support will also take the module-group as part of the relationship. This allows for defining different values for an attribute in case a module is offered multiple times in a program, based on its module-group context.

In case a module is offered multiple times in a program, it is supported to NOT select the module-group. In this case the relationship information is the same for each occurrence of the same module in the program.

Added functionality to support the above is:

• Add support to define ‘relationship’ information of a module in context of a programme (study) and module-group.
• Add support for the administrator to define custom-fields on the module-study relation to be managed using this relationship.
• Extend the management of module-study relations for the user from the structure page by extending the module-module_group popup to support both module-group and study relationship information.
• When managing the module-study relation, ‘inherit’ the module-group containing the module. This to limit the user actions to solely selecting the study and setting the relationship information.
• Only provide the module-study relationship management information to the user if at least one attribute is defined by the administrator.

The image below shows the option to define the module -> module-group relation information (tab: Structure) and the module -> study relation information (tab: Relation (study/module)).

Configuration and management of offerings should support conditional fields - CUR-2087

Conditional fields are supported on (almost) all object, and so now and then we are pointed to an object that is lacking this support. It was noted that offering periods did support the configuration of conditions and conditional fields, but the visualisation didn't respect the configuration. This has been fixed, to support usage of conditional fields on offerings too.

Buttons to manage activities in the activity-grid should be accessible - CUR-2164

The activity grid shows a visual representation of the desired teaching layout (activities). The activity-series and activities defined can be managed using the buttons shown in the tile. However, in case a long(er) activity name was used, the name was positioned on top of the buttons, making them inaccessible. A change is applied to truncate the activity name and not float over the button. The button is now always accessible and the full name of the activity is available using mouse-over.

Reports using a row page should show the information when expanding the page - CUR-2204

In case a report page is defined that using a row page and the row page is configured to be collapsed by default, when expanding the page the row page information was not shown. A change is applied to retrieve and display the row page information on expand.

The planboard subject view should only show the subjects directly related to the study - CUR-2021

In all reports, except the planboard view, the subjects shown are filtered on the defined relation to the study. This 'direct related to study' filter is now also applied to the planboard view, so the behaviour of all reports is the same.

As an administrator / implementation manager I want to brand the used product - CUR-1993

The Curriculum and Workload management product partly use the same configuration and administration interface. Using the administration interface the 'branding' of the product can be defined and differentiate between the Curriculum or Workload management branding.

Configuration:

Navigate to the Administration -> Config menu option

1. Set the 'header.workload-product' to true to use the Workload management branding
2. Set the 'header.workload-product' to false to use the Curriculum branding
3. Optionally set the 'header.product-switcher' to activate the TE product switcher including the branding selected

Usage of images in descriptive texts should be more robust - CUR-2200

The management of the descriptive texts supports adding images. In case an image is added, it will initially be added as 'bytes' to the description and in the background the image is save to the image server. Once save the 'bytes' are then replaced with the location of the image.

When adding very large images (several Mb's) the timing of saving the image and replacing the 'bytes' with the URL can not be finished prior to the user Save action. This means that the description of several Mb's will be saved, which is limited. This is the technical background to provide some details on what happened.

Several changes are applied to create a more robust (error proof) handling of descriptions with images. The save shouldn't give a 'system error', but a useful message for the user. For instance, the text is saved, but the image could not be uploaded. This means the user has the text and can add the image again, or maybe reduce the image size to a size more suitable for web viewing and then add it. Several 'error' situations were identified and have been solved based on the above tactic.

As a department manager I want to approve ad-hoc absence requests - CUR-2034

(Un)availability management of staff members is standard supported in different means. The until this release supported (un)availability was based on generic setting steered with the weekly availability pattern or a number or percentage of unavailability hours in the context of workload.

The image below shows the user screen to define the weekly availability pattern.

In this release the option is added to support the request of 'ad-hoc' unavailability by a user and the approval by the HR manager.

A new screen is introduced called 'unavailability', that can be added to the user Tab settings as shown in the image below, but can also be added into a workflow to gather 'ad-hoc' unavailability prior to the semester start.

The user is shown an overview of the ad-hoc requests done and their status. The user can define additional ad-hoc unavailabilities by clicking the Add button.

The user can specify:

• Start and end date
• Start and end time
• Type, allowing to define if it should be set als unavailable, available or rather not
• Description to define the reason for the absence

The HR manager will have access to the Absence report (unavailability-report) that will show an overview of the the staff unavailability request.

The image below shows the standard view. The HR manager can filter on date to select only request that have been filed between specific dates, or on status to only see the 'open' requests (or the approved / rejected ones).

The HR manager can use the toggle buttons to 'select all' or 'select one/more' requests from the list. In the image below the HR manager selected one request. Once selected the Approve and Reject button appear to enable the HR manager to manage the request.

In case the HR manager approves the request, a pop-up appears that allows the further handling of the request. The HR manager can decide to just accept and without providing any additional information and handling, but can also decide the absence should both have effect on the availability in scheduling and in the availability of the person in relation to workload.

In the image below the latter is chosen. The HR manager has marked that for this request a 'task' should be created that will have effect on the total availability of the person. The request should be marked and saved as an ad-hoc absence task in the users profile. The amount of hours is calculated based on the request, but can be adjusted at this moment.

If we then look at the users profile, we notice a task has been added in the section 'Absence'. The task size is 16 hours and this 16 hours will be deducted from the total available hours for the person.

This means that an unavailability 'marked' as task will lead to an additional deduction of hours, next to the standard user availability hours that already has deducted the contract defined leave hours.

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 Broker with support for OOAPI v5 - CUR-2202

The data is managed and stored in Curriculum, optimised to support the management of data. With the increase of 'retrieval' oriented interface we noticed that this optimisation is not the most effective way for mass retrieval. In order to support mass retrieval the Broker is introduced a few months ago, that is 100% designed to support mass retrieval of Curriculum managed information.

From a technical perspective the Broker will receive 'approved' data from Curriculum and save the information in the read-optimised format. The Broker can be accessed using the API to retrieve studies, modules. Where the Curriculum API has to 'gather all data and generate the JSON output message', the Broker has direct acces to the JSON output message, since that is the optimised storage format.

This release the Broker is extended with OOAPI services. Due to the nature of one of the services using OOAPI that every 5 minutes does a full refresh of all studies / modules, the generated peak load affected the Curriculum performance. In some cases the load was so high and the generation of the response was not fast enough (exceeding 60 seconds) that the 'requesting' system showed an empty result. Initial test with the same requests and data to compare Curriculum versus Broker API calls learns that the read optimised Broker is between 20 and 100 times faster.

The initial set of OOAPI services implemented in the Broker, to support eduXchange data retrieval, is:

• Organization
• Specification
• Programs
• Courses
• Offerings

The service definition is available in Swagger format at https://curriculum-broker.eu.timeedit.net/v3/api-docs

getGroup service should return the module-group -> module attributes - CUR-2239

The getGroup service didn't return the user defined custom-fields on the module-group to module relationship. Only the standard available (and pre-configured) Curriculum fields were returned. This has been changed and the getGroup service will now return all defined custom-fields on the module-group to module relation.

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.

This release no vulnerabilities has been reported that require mitigation.‍

‍

Refer to the Curriculum manual for configuration guidance.

The combined Curriculum/Workload management release schedule provides an overview of all upcoming releases for the next period. Releases are scheduled to occur once every two weeks. With each update, we introduce new features, enhance existing ones, and provide security patches along with regular fixes.

Release schedule 2025 / 2026

The overview below shows the planned releases for 2026 and the last month of 2025 on both Acceptance (Staging) and Production.

‍

2025

‍

Sprint 162

• Version: 11.24 / 12.0 (topbar release, acceptance only)‍
• Acceptance: 17-10-2025‍
• Production: 28-10-2025

‍

Sprint 163

• Version: 12.1
• Acceptance: 31-10-2025‍
• Production: 11-11-2025

‍

Sprint 164

• Version: 12.2‍
• Acceptance: 14-11-2025‍
• Production: 25-11-2025

‍

Sprint 165

• Version: 12.3
• Acceptance: 28-11-2025‍
• Production: 09-12-2025

‍

2026

‍

Sprint 166 (4 weeks)

• Version: 12.4‍
• Acceptance: 12-12-2025‍
• Production: 06-01-2026

‍

Sprint 167

• Version: 12.5‍
• Acceptance: 09-01-2026‍
• Production: 20-01-2026

‍

Sprint 168

• Version: 12.6‍
• Acceptance: 23-01-2026‍
• Production: 03-02-2026

‍

Sprint 169

• Version: 12.7‍
• Acceptance: 06-02-2026‍
• Production: 17-02-2026

‍

Sprint 170

• Version: 12.8‍
• Acceptance: 20-02-2026‍
• Production: 03-03-2026

‍

Sprint 171

• Version: 12.9‍
• Acceptance: 06-03-2026‍
• Production: 17-03-2026

‍

Sprint 172

• Version: 12.10‍
• Acceptance: 20-03-2026‍
• Production: 31-03-2026

‍

Sprint 173

• Version: 12.11‍
• Acceptance: 03-04-2026‍
• Production: 14-04-2026

‍

Sprint 174

• Version: 12.12‍
• Acceptance: 17-04-2026‍
• Production: 28-04-2026

‍

Sprint 175

• Version: 12.13‍
• Acceptance: 01-05-2026‍
• Production: 12-05-2026

‍

‍

‍

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 Study guide release schedule

Improvements

The issues in release mentioned under the section improvements are considered as new functionality, user experience improvements or bug fixes.

The object 'Specification' should be supported as a main tab - SG-358

Where other objects like Study, Module, Module-group and Faculty are available for configuration as main tab in the study guide, the specification wasn't yet. In this release the ability to define a main tab using the Specification has been added.

The configuration is similar to any of the other tabs and widgets, and just requires selecting the type 'Specification' instead of for instance Study or Module.

The detailed explanation to configure the main tab and the different widgets to support search, filter and/or display of detailed data of an object is available as an Academy guide.

The sidebar filters tooltips should be accessible - SG-479

The sidebar filter options provide the option to define a tooltip that can be opened to provide usage information to the users. A bug was introduced where the tooltip wasn't shown any more in the sidebar with filter options. This has been fixed, so the tooltip is shown again as expected.

‍

The study guide should show the defined line-breaks - SG-488

When displaying textual descriptive texts, the study guide 'text display function' could strip multiple line-breaks and reduce them to a single line-break. This to prevent from showing a lot of white space in case multiple line-breaks were defined.

This has been fixed to a more 'architectural / design' approach where the study guide will show the data and its line-breaks as defined. In case there are too much line-breaks (e.g. too much white space) it will not be solved by the study guide, but should be solved by removing these line-breaks in the source (Curriculum).

The period time-line representation should display correctly in Safari - SG-485

The display the module and its offering periods in a program using the period time-line representation was not correctly displayed in Safari. This has been fixed, so the period time-line representation is also correctly displayed in Safari.

‍

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.

This release no vulnerabilities has been reported that require mitigation.‍

‍For more guidance on configuration and setup of Study Guide, use the relevant Study Guide manual.

The release notes provide information on the features and improvements in the specified version.  
The release dates related to the versions are published in the Evaluation release schedule.

Improvements

New functionality, user experience refinements, and bug fixes. Issues marked as hotfix are developed in this sprint but applied to the previous release or directly to production, depending on impact.

Condensed reports should be exportable to excel/csv - EV-373

The condensed report sounds like a compact report, but is in most cases an extensive report with many columns (and rows). In the previous sprint(s) some changes have been made to optimise the visualisation of the condensed report on screen and improve the PDF printed result.

Especially the PDF printed result is tricky, since the number of columns can be so extensive that a lot of manipulation of creating 'virtual pages' is required to get a more or less consistent and readable PDF result.

To cater for the actual requirement of 'getting the data out of evaluation in a usable format', the initial user story has been adjusted to support just that in the form of a Excel export. The condensed report can now be exported as Excel to allow access to all the data in the report, even allowing manipulation of the columns to show, filter, sort, etc. The Excel can then be printed as PDF in case the PDF is still required, using the different Excel options to fit to page, adjust the printing direction, etc.

Production shouldn't crash - EV-369 (hotfix)

After the migration of the production environments to the new stack, the production environment could just 'stop functioning correctly / become unresponsive'. Analysing the logs revealed the root cause, that pointed to a specific configuration in the network traffic where the server could just drop a random database connection. This caused the production 'crash'.

This has been fixed, by adjusting the network configuration to prevent the random database connection drops.

The FTP archive function should be more resilient - EV-370

The FTP archive function copies the Evaluation generated PDF reports to a central location for further processing in the customer infrastructure. The FTP didn't have a retry mechanisme in case of a network hick-up, so any hick-up would cause a failing FTP archive data exchange.

A fix is applied to add a retry mechanism to the FTP archive function in case of an error. The retry mechanism will retry the failed file and then continue with the next report files making the FTP archive function more robust and resilient.

‍

Security

An integral part of our development and build process is the automatic scanning for known security vulnerabilities. Fixes are prioritised based on impact: some may require an immediate hot-fix, while others are addressed in the current or next Sprint (release). For more information on reported vulnerabilities, see the central database of vulnerabilities.

During this release no vulnerabilities were reported that needed mitigation.

‍

Refer to the Evaluation manual for configuration guidance. Version release dates are provided in the Evaluation release schedule.

This release focuses on improving clarity around modules capacities and data quality for linked groups, as well as making Allocate Overview faster and more reliable.

Improvements

• Manual allocation from the group drawer
  • Clearer error messages that list which selected students could not be allocated and why.
  • Improved support for linked groups:
    • Students will be allocated to the selected group and its linked group.
    • If students already have allocations in one or both activities, those allocations are removed before allocating the the selected group and its linked group.

Screenshoot of manual allocate with linked groups

• Auto‑allocation status handling is improved, removing the a timeout that sometimes triggered an error message even when to job succeeded.

This release focuses on improving clarity around modules capacities and data quality for linked groups, as well as making Allocate Overview faster and more reliable.

Improvements

• Dynamic capacity in Allocate Overview
  • What changed: Capacity for a module is now calculated dynamically from its student groups (instead of reading the "expected enrollment" field on the module).
  • Why: Keeps capacity accurate as you change group sizes.
  • Where it shows:
    • Capacity number in Allocate Overview
    • Over‑enrollment warning in Allocate Overview
    • Over‑enrollment warnings in Issue list

Screenshot of Allocate overview, highlighting a warning for a module where the capacity is lower then enrolled students

• Linked group guideline warning
  • What changed: Allocate Overview now flags linked groups that do not meet the recommended configuration for linked groups.
  • Why: Makes data quality issues easy to spot and prevents unexpected allocation results.
  • In coming release we will add bulk linking of groups, where these guidelines are enforced already when linking groups. And the linking of individual pairs will be removed in the drawer.

Screenshot of a warning message for a linked group that breaks all guidelines

• Faster and more robust data loading in Allocate Overview
  • What changed: Optimized how and what data is loaded behind the scenes.
  • Why: Enables features like dynamic capacities and improves responsiveness, of the interface.
  • Expected impact: Noticeably quicker initial load and smoother interactions.
• Quicker expansion of Allocated student in the drawer when no students are allocated
  • What changed: Reduced the time to expand the "Allocated students" section in the drawer when it is empty.
  • Why: Removes a small but frequent delay in everyday workflows.

Bugs

• Fixed: Could not save distribution rules
  • Symptom: Saving distribution rules failed without applying changes.

Improvements

New functionality, user experience refinements, and bug fixes. Issues marked as hotfix are developed in this sprint but applied to the previous release or directly to production, depending on impact.

Improved Printing Functionality for Curriculum Rows Pages - CUR-2061, CUR-2082

Enhanced the printing capabilities within Curriculum, with key usability improvements for clearer and more controlled output:

• Introduced a new "break" page type for use in "rows" pages; when printed, each "break" inserts a page break, allowing for cleaner separation of content.
• All pages, including the new "break" page, can now be reused or shown multiple times within the same rows page.
• Print layout now supports both portrait and landscape orientation, so the content is always full width.
• In print mode, the following artifacts are now hidden for a cleaner result: buttons, tooltips, the footer, and empty fields.
• The customer logo is now displayed at the top of printed "rows" pages.

The print button on "rows'" pages can be shown  using the "display print" page configuration.

Assessment Matrix Improvements and Fixes - CUR-2162, CUR-2174, CUR-2175, CUR-2176, CUR-2177, CUR-2178, CUR-2179, CUR-2180

A comprehensive update to the assessment matrix enhances export options, performance, filtering, and overall usability—aligning it more closely with the subject matrix, which also benefits from most of below improvements:

• Export Options: Added support for CSV and Excel exports, showing modules, objectives, and their contribution to assessment types.
• Performance: Faster loading and improved interaction responsiveness across both the assessment and subject matrices.
• Objective Expansion: New setting to control whether objectives expand by default when opening a module. Configurable per page and overridable by the user.
• Filtering Enhancements:
  • Page-configured category now correctly limits available assessment types.
  • Type columns now count only matching modules, not objective-level matches.
  • Fixed disappearing tree elements under certain filter conditions.
  • When no type filter is active, the full tree is shown, matching subject matrix behavior.
• Ordering & Display Improvements:
  
  • Assessment types now follow the configured sequence (or order by name
  • Headers and labels are truncated dynamically based on screen size and page category.
  • Type match counters shown in larger font for readability.
  • Improved visual feedback for expanded and hovered rows.
  • Toggle button hidden for groups without modules or modules without objectives.

‍

Support for Uploading Documents to Person Entities – CUR-2213

You can now upload documents directly to person objects in Curriculum. This makes it easier to manage and find files like competencies, certifications, training records, and other relevant documentation all in one place.

This is a powerful addition for institutions looking to centralize person-related records and streamline administrative processes. Whether you're tracking qualifications or simply need a place to store important files for curriculum management per individual, this functionality gives you the flexibility to do so.

The feature uses the familiar document custom type and is academic year independent like the person object itself, so documents stay attached to the person over multiple years.

Reach out to support if you’d like help setting this up or want to brainstorm ideas for this.

Approve and Reject Unavailability Requests – CUR-2215

To better support department- and organisation-level processes around staff availability and absence, it is now possible to approve or reject (un)availability requests submitted by employees.

A new page, availability-request-approve, has been introduced to provide approvers with a central interface for reviewing and managing requests. When a request is approved or rejected, the outcome is reflected in the user's availability page.

Key functionality includes:

• Filter requests by Status (open, approved, rejected), Start Date, and End Date
• Approve or reject requests individually or in bulk
• Rejections require a motivation for transparency
• Available to users with the new APPROVE_AVAILABILITY permission

This addition streamlines approval workflows, increases visibility, and ensures cleaner, more reliable availability data across the organisation,

The user submitting (un)availability can view the status of each request:

‍

Improved Filtering of Periods in Personal Task List – CUR-2217

Periods on the personal task list are now filtered based on the faculty or organisation assigned to the user, in line with calendar conditions (e.g., facultyId in (ORG_CODE)). This avoids showing irrelevant periods from other academic calendars.

The personal task list gives a handy overview of the availability and utilization across different years, months and periods

OOAPI Integration Improvements - CUR-2201, CUR-2209, CUR-2211

Enhanced OOAPI integration with performance, reliability, and specification conformance improvements. Configuration options have been expanded to support all needs. More updates will follow soon.

For detailed setup guidance or to learn about all options, please contact support.

Restore Offerings - CUR-2089

It's now possible to restore removed offerings using the Restore button, available when viewing offering pages in Changes mode.

Paginated Organisation Report – CUR-1898

The organisation report is now paginated, resulting in faster load times and improved performance. This enhances the user experience—particularly for new users, for whom the organisation report is often the first point of entry.

‍

Added 'Terminated' Status to Group Report – CUR-2153

The module-group report now supports selecting and displaying the terminated column, making it easier to identify and filter out groups that are no longer active or scheduled to be given.

‍

Improved Usability of Empty Date(Time) Fields - CUR-2099

Removed placeholder text from empty date(time) fields to prevent confusion, as it could appear (pre-)filled. These fields now display as empty by default; the input format is still shown after your first selection.

‍

Editable Activity List with Schedule Edit Rights - CUR-2188

The activity list in the method tree is now editable when the schema is owned (unchanged requirement) and the user has EDIT_SCHEDULE(_WORKFLOW) rights, even without EDIT_METHODS(_WORKFLOW). This enables teachers and management to adjust activities without requiring full method edit permissions.

‍

Fixed: Missing Custom Fields After Year Copy on Specifications Without External ID - CUR-2154

Fixed an issue where specifications lacking an external_id could lose custom fields during a year copy. Year copies now retain all custom fields regardless of external_id presence.

‍

Fixed: Mid-Year Starting Specifications Not Visible in Report View - CUR-2220

Fixed an issue where specifications that started later in the academic year were not shown in the specification report. Specifications are now correctly displayed as long as they are active at any point during the academic year, even if their start date is after the academic year has begun.

‍

Fixed: Deleted Items Still Visible in Item Reports - CUR-2145

Resolved an issue where deleted items continued to appear in item reports.

‍

Other Fixes and Improvements

We’ve made a broad set of behind-the-scenes improvements in this release, covering performance, stability, integrations, and data handling. Below is a summary of the most impactful changes:

• General performance and stability improvements
• Faster loading when the feedback tab is closed
• More accurate cost calculations
• Improved caching
• More reliable person import and export processes
• Faster and more accurate integrations (OOAPI, RIO, Data Manager, Core, Study Guide, customer-specific)
• Correct redirect behavior after interacting with unsaved changes modal
• Enhanced logging for diagnostics

As always, specific fixes are communicated directly to reporters.

‍

Security

An integral part of our development and build processes is the automatic scanning for known security vulnerabilities. Fixes are prioritized based on impact: some may require an immediate hot-fix, while others are addressed in the current or next Sprint (release). For more information on reported vulnerabilities, see the central database of vulnerabilities.

No security issues were identified this sprint.

‍

‍

Refer to the Curriculum manual for configuration guidance. Version release dates are provided in the Curriculum release schedule.

Improvement

• All new entrances require users to login as default. This is now reflected by the interface for setting up new entrances so that user name and password is only required if “Require login” checkbox is unchecked.

Screenshot of configuration interface for creating new entrances

• Week numbers was previously not shown when UK date format was shown, this is now changed to always show

Bugfix

• Solved a problem where system ran out of memory when creating exports

Improvements

New functionality, user experience refinements, and bug fixes. Issues marked as hotfix are developed in this sprint but applied to the previous release or directly to production, depending on impact.

‍

Enhanced Widget (Field) Filtering and Visibility Logic – SG-475 (Hotfix 2.49.1 & 2.49.5)

Widget (field) configuration now cleanly separates data filtering from field visibility, offering improved precision and flexibility more aligned with Curriculum filter behavior.

The new condition option has been introduced to control widget field visibility. This allows you to control whether a field is shown or hidden, depending on the context or object that you're viewing. This was already possible using the filter  property, but only for INFO fields; that use case has been automatically migrated to use a condition instead. Conditions are also now consistently supported across all widget field types.

The filter property on widgets and widget fields is now used exclusively for filtering widget data and supports more flexible, nested key-value expressions. Legacy shorthand filters (e.g. using just ET to filter methods by category) have been automatically migrated to the new, more expressive syntax. For example:

• required=true — Filter for required methods or appraisals
• credits=4, method.contactHours=0, method.type=SO , method.category=ET, method.credits=0.15— Filter for specific methods
• criteria=S&weighting=2, etc. — Filter assessments by two (or more) appraisal fields

‍No action required. Existing configurations have been automatically migrated to the new improved syntax.

This update also resolves an issue where incorrect filter syntax—introduced due to changes in the previous release—could cause certain pages to fail. Additionally, validation has been improved and helpful tooltips have been added to assist with configuring both conditions and filters.

‍

Improved Performance and Stability During Imports – SG-484

Ongoing behind-the-scenes improvements have been made to enhance overall system performance and stability, with a particular focus on increasing reliability during import operations.

‍

Fixed: Misaligned Widget Fields in Sidebar Layout – SG-475 (Hotfix 2.49.1)

Fixed an issue that caused widget fields within the sidebar layout to appear misaligned.

‍

Fixed: Empty "Show More" Filter Popup – SG-475 (Hotfix 2.49.1)

Resolved an issue where the "Show more" filter popup was displayed without any filter options.

‍

Fixed: 'Expand All' Not Working in Structure Widget – SG-477 (Hotfix 2.49.1)

Fixed an issue where the 'Expand all' button in the structure widget failed to expand nested items as expected.

‍

Fixed: Final Page of Imports Not Processed Correctly – SG-480 (Hotfix 2.49.5)

Fixed an issue where the last page of import results from Curriculum was skipped, potentially causing certain objects—such as modules or studies—to be excluded from the import.

It is recommended to re-run the import to verify that all data is correctly imported.

‍

Fixed: Sort Selector Not Visible on Desktop – SG-481 (Hotfix 2.49.5)

Resolved an issue where the sort selector, for example to sort on credits, was not displayed in desktop view.

‍

Security

An integral part of our development and build processes is the automatic scanning for known security vulnerabilities. Fixes are prioritized based on impact: some may require an immediate hot-fix, while others are addressed in the current or next Sprint (release). For more information on reported vulnerabilities, see the central database of vulnerabilities.

‍

Fixed Security Issues - SG-462

Resolved vulnerabilities in third-party libraries:

• CVE-2025-52520 (7.5)
• CVE-2025-53506 (7.5)
• CVE-2025-48989 (7.5)
• CVE-2025-48924 (5.3)
• CVE-2025-7962 (8.7)
• CVE-2025-41242 (8.2)

‍

‍

Refer to the Study Guide manual for configuration guidance. Version release dates are provided in the Study Guide release schedule.

Improvements

New functionality, user experience refinements, and bug fixes. Issues marked as hotfix are developed in this sprint but applied to the previous release or directly to production, depending on impact.

‍

Condensed Consecutive Reports Filtering Improvements - EV-363

The "Condensed consecutive" report now honors your selection of evaluations when generating the report. You can refine this selection using existing filters such as Show mine (filtering to evaluations the user has a relation to), as well as faculty and program-based constraints, bringing its behavior in line with other report types.

This update enables faster, more accurate, and context-specific condensed reporting. If no evaluations are selected, the report defaults to returning all evaluations you are related to, preserving prior behavior.

Fixed: Report Display Issues - EV-363 (Hotfix 6.23.2)

Resolved an issue where certain reports were not displayed correctly before printing.

‍

Security

An integral part of our development and build processes is the automatic scanning for known security vulnerabilities. Fixes are prioritized based on impact: some may require an immediate hot-fix, while others are addressed in the current or next Sprint (release). For more information on reported vulnerabilities, see the central database of vulnerabilities.

‍

Fixed Security Issues - EV-367 (Hotfix 6.23.1)

Resolved vulnerabilities in third-party libraries:

• CVE-2025-54988 (9.8)
• CVE-2025-52520 (7.5)
• CVE-2025-53506 (7.5)
• CVE-2025-48989 (7.5)
• CVE-2025-48924 (5.3)
• CVE-2025-7962 (8.7)
• CVE-2025-41242 (8.2)

‍

‍

Refer to the Evaluation manual for configuration guidance. Version release dates are provided in the Evaluation release schedule.

This release focuses on performance enhancements and UI improvements to create a more efficient user experience.

This release is pushed to test and production at release date

Improvement

• In manual allocation, if the selected students exceed available capacity, the Allocate button is disabled and a message explains that the selection exceeds capacity.

Screenshot of Allocate button disabled, because too many students selected

• The Allocate button is now disabled when a proposal contains no suggested allocations, preventing unnecessary actions.

Screenshoot of proposal list where Allocate button is disabled because there is no allocations to be applied

• Information messages in Allocate Overview use a refreshed design and auto‑dismiss after 3 seconds.

Screenshot of information message

• Long‑running tasks such as updating the issue list now run in parallel and no longer block the interface. This will be available in test for about one week before release to production.
• After the registration period has closed, Auto‑allocate will no longer assign students to activities that have more than one group. This is part of a refactor to improve speed and robustness. Long term, Auto‑allocate will use the same allocation algorithm as proposal generation for these cases; previously it used a non‑optimized approach.

Improvements‍

New functionality, user experience refinements, and bug fixes. Issues marked as hotfix are developed in this sprint but applied to the previous release or directly to production, depending on impact.

‍

New Availability Request Report - CUR-1737

Added a report that can be enabled on organisation or faculty pages to display availability requests for all persons associated with the respective unit. The report shows the requested (un)availability periods  (e.g. holidays) along with their descriptions. It is accessible to  users with the VIEW_AVAILABILITY permission.

‍

Include Results from Sub-Organisations - CUR-2143

The following pages now display combined results from both an organisation and its sub-organisations. For example, when viewing at the Human Resources level, results from HR and its sub-units (e.g. Payroll Office) are included:

• Assignments
• Tasks (tasks-report)
• Availability report
• Effort report
• Vacancies
• Workload report
• Hour report (unchanged, already aggregated across the organisation tree)

This provides a consolidated view of activities across the organisational hierarchy.

‍

Added Objective Visibility in Assessment Matrix - CUR-2120

The assessment matrix now supports displaying module objectives, similar to the subject matrix. Objectives are shown when a module row is manually expanded, providing clearer insight into how modules contribute to study learning goals (subjects) across groups and the overall study structure.

Note that an expand objectives toggle or download button is not yet available on this page.

‍

Improved Description Propagation - CUR-2116

Updated the logic for propagating descriptions across academic years. For example, when a description is modified in 2024 and remains unchanged in 2025 (or later), it is now automatically overwritten in 2025 without generating an audit entry. However, if the 2025 description has already been edited, propagation only occurs when the content is identical, in which case the previous change is overwritten.

Note: propagation only occurs when propagate is enabled on the description element configuration.

‍

Assessment Credits Validation and Warning on Appraisals Page - CUR-1800

This new functionality checks whether the assessment credits in an object (e.g. module) align with the defined goal (optimum or minimum). A warning is now shown on the appraisals page if the total assessment credits differ from the credits set on the object.

‍

‍

Improved Activity Export - CUR-2147

Resolved multiple issues causing partially incorrect activity data to be exported to Data Manager from the Curriculum → Data Manager interface:

• Activities were compared using period external IDs instead of the correct way; by offering IDs.
• Inactive activities (deleted or not offered) were included in the export.
• Export mappings were processed for all activities across all offerings, causing performance issues.

This ensures only the intended offering activities are send to Data Manager.

‍

Read-Only Mode for Teacher Assign Page - CUR-2122

Added support for a configurable read-only mode on the teacher assign page, managed through the page admin interface.

‍

Display of Custom Fields in Study Modules Report - CUR-1723

Manually created custom fields (marked in bold on the admin page) can now be included in the study-modules-report, instead of only the default ones.

‍

Hiding Exam Warning Using Dash Syntax - CUR-2103

You can now hide the exam warning from the appraisals page by setting the label Static.Tab.Schedule.Activities.Exam.Info to a single dash (-) with no whitespace.

Previously, FAQ and Manual links (Static.Label.Faq.Url, Static.Label.Manual.Url) were hidden using #. These have been migrated to - for consistent behavior.

Note: this syntax may also work in other places, but the effect can differ. In most cases only the label text is hidden, while the surrounding container may remain visible.

‍

Enhanced Subject Matrix Configuration Options - CUR-2109

Added a page option Expand objectives that allows objectives on modules to be shown by default in the subject matrix. The user can still change this behavior themselves.

The "Related objects" filter was moved up in the UI and is now only visible when the custom field subject.relatedId is configured as visible.

Additionally, a new setting in administration > config subject.include_empty_related was added to configure whether to include subjects without a configured related object (empty, i.e. no related study) in the "Related objects" filter.

‍

Extended CSV Upload for Type RESOURCE - CUR-1973

Added support for importing both version-level and resource-level custom fields via CSV upload for resources.

‍

Conditional Display and Configurable Label for "Edit in Structure" Button on Appraisal Page - CUR-2074

The "Edit in structure" button on the appraisal page is now only shown when at least one (not counting assessmentId) appraisal field is visible.

Additionally, the button label is now configurable via Static.Page.Appraisals.Edit, instead of using the shared Static.Label.EditStructure key used on other pages.

‍

Fixed: Activity Edit/Create Allowed with EDIT_SCHEDULE(_WORKFLOW) Permission - CUR-2144

Fixed an issue where EDIT_SCHEDULE(_WORKFLOW) permission was not sufficient to enable editing or creating activities in the appraisal list or method list. The permission is now correctly recognized, ensuring the activity form is editable when the user has the correct rights. When the required permission is missing, the edit buttons are hidden.

Note: In addition to EDIT_SCHEDULE(_WORKFLOW), users must also hold EDIT_APPRAISALS(_WORKFLOW) (for the appraisal list) or EDIT_METHODS(_WORKFLOW) (for the method list) to edit activities on those pages.

‍

Improved Export Hook Reliability and Error Handling - CUR-2151

Optimized the execution of export hooks for better performance and stability. Failures in export hooks now:

• Trigger improved logging with detailed technical error messages
• Clearly mark the export as failed in the hook interface
• Show proper user-facing warnings when a hook fails

‍

Fixed: Reopen Button Not Visible for Module Coordinators on Assessment Workflows - CUR-1975

Fixed an issue where the reopen button was not shown on assessment-level workflows when the participant had a relation via the module owner (e.g., Module Coordinator), instead of directly on the assessment.

When determining if a user can reopen a process, the system now checks for participant status in the first workflow status.

This restores expected behavior for reopening processes and aligns assessment-level logic with other object types like groups.

‍

Fixed: Unintended Version Creation When Editing Subject Types - CUR-2137

Fixed an issue where selecting a typeahead option while editing subject types in the admin could incorrectly create a new version of the subject type linked to the selected typeahead option.

‍

Fixed: Assessment Role Permissions Not Applied Correctly - CUR-2007

Fixed an issue where users assigned a role on an assessment did not receive the corresponding permissions. Role-based permissions are now correctly applied when assigned at the assessment level.

‍

Fixed: Missing Modules in Route Overview Page - CUR-2150

Resolved an issue where modules with offerings were not shown in the route overview affecting periods with part-of-day configurations.

‍

Fixed: Cache Issue for Year and References - CUR-2152 (Hotfix 11.20.5)

Fixed a caching issue for year and reference data that could cause unexpected errors.

‍

Fixed: Subject-Matrix Expand/Collapse Button Issues - CUR-2138 (Hotfix 11.20.3)

Fixed multiple issues with the expand/collapse button in the subject matrix. The button now opens correctly and properly respects page configuration. such as the "expand objectives by default" setting.

‍

Fixed: Alignment on Method List Page - CUR-2129 (Hotfix 11.20.3)

Fixed misalignment issues on the method list page by standardizing column widths based on the table with the longest name. Text is now left-aligned except in the last column.

‍

Fixed: Errors on Appraisal Pages - CUR-2131 (Hotfix 11.20.3)

Fixed an internal issue that caused errors to occur when accessing appraisal pages.

‍

Fixed: Element Selector on Element Admin - CUR-2130 (Hotfix 11.20.1)

Fixed an issue that caused the element selector on the element admin interface to be non-functional.

‍

Fixed: Missing Data on Credits Pages - CUR-2132 (Hotfix 11.20.3)

Fixed an issue that prevented data from displaying on the credits pages.

‍

Fixed: Study Report Not Loading - CUR-2131 (Hotfix 11.20.3)

Resolved an issue where the study report failed to load and crashed with an error under certain conditions.

‍

Security

An integral part of our development and build processes is the automatic scanning for known security vulnerabilities. Fixes are prioritized based on impact: some may require an immediate hot-fix, while others are addressed in the current or next Sprint (release). For more information on reported vulnerabilities, see the central database of vulnerabilities.

‍

Fixed Security Issues - CUR-2154 (Hotfix 11.20.4)

Resolved vulnerabilities in third-party libraries:

• CVE-2025-54988 (9.8)
• CVE-2025-52520 (7.5)
• CVE-2025-53506 (7.5)
• CVE-2025-48989 (7.5)
• CVE-2025-48924 (5.3)
• CVE-2025-7962 (8.7)
• CVE-2025-41242 (8.2)

‍

‍

For further guidance on configuring and setting up Curriculum, refer to the relevant Curriculum manual.

You can now group reservations by Weekday, Month, or Year in Text view, matching the behavior of the Graphical view when the General page layout is set to Weekday, Monthly, or Yearly.

Improvement

Text view: Group reservations by Weekday, Month, and Year (new options).

• Group reservations by Weekday, Month, or Year directly in Text view
• Behavior matches Graphical view when General page layout is set to Weekday, Monthly, or Yearly

Screenshot of setting Group to weekday and resulting presentation, where reservations are grouped by weekdays

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 Study guide release schedule

Improvements

The issues in release mentioned under the section improvements are considered as new functionality, user experience improvements or bug fixes.

AI coach should respond and not keep spinning - SG-466

When prompting the AI coach for advice or assistance a small spinner was started to indicate the response was being searched and formulated by the coach. The answer however didn't come, since the spinner kept spinning. This has been fixed, so the spinner will be shown during the formulating of the answer and then the answer will be shown.

‍

Modules without externalId should still show entry requirements - SG-476

In case modules with links (entry requirements, substitutions, exclusions) are defined in Curriculum the, they are shown in Study Guide. It was noted sometimes one or more links were not shown. After further investigation this was caused by the fact a linked module didn't have an externalId and only a code. This has been fixed, so the link will be shown in case there is either a code, an externalId or both.

Search results should be shown in alphabetical order - SG-470

When searching using the search bar the drop-down quick-search showing the first matching results for direct selection was displayed in a pretty random order. To improve the user experience and provide a predictive result the quick search will be sorted alphabetically.

‍

Security

An integral part of our develop and build processes 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.

This release no vulnerabilities has been reported that require mitigation.

For more information on reported vulnerabilities, see the central database of vulnerabilities.

‍

‍For more guidance on configuration and setup of Study Guide, use the relevant Study Guide manual.

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 Evaluation release schedule

Improvements

The issues in release mentioned under the section improvements are considered as new functionality, user experience improvements or bug fixes.

‍

Evaluation members (staff) should be marked as 'employee' - EV-361

In case an Evaluation with  users and their associated roles in Curriculum are synced tho Evaluation, some are syncing to Evaluation without the "Employee" role ticked. This will cause the user to have hardly any rights and for instance not be evaluated as a member, e.g. lecturer, of an Evaluation.

The above situation occurred in case the user already exists in Evaluation and has been created without the Employee role. New synced users were created with the Employee role correctly set.

A fix is applied that in case a user is assigned to a role in Curriculum, the user will be synced to Evaluation, created if it doesn't exist yet (based on the setting generate_all or generate_persons is true) and the Employee role will always be set.

‍

The member report should be extended with student attributes - EV-357

The member report provides detailed information with respect to the answer to member (e.g. lecturer) related questions. A small usability change and extension has been made to the report to support easier usage and filtering and extend filter options by using the student attributes defined (e.g. enrolled study programme, former education, gender, ...)

The changes are:

• Split the column that contains the question code and question in two columns question code, question
• Add the defined student attributes as additional columns. The student attributes depend on the configuration and above samples are mentioned like the former education, gender. The report setup is done in such a way that all defined student attributes will be added as separate columns to the report.

‍

The consecutive PDF report should show all data  - EV-358

When generating and exporting the consecutive report as PDF, the report can exceed the page boundary and information that exceeds the page boundary is not visible anymore. This has been fixed, so the page boundaries (page width) is respected when generating the PDF and the information will be visible in the PDF report. In case the number of columns exceed the page width a 'second' page will be created. The first page will show the first fitting questions and responses, the second (and optionally more) page will show the pages exceeding the first page.

The graphical display of the question result should show the median  - EV-360

The graphical display of a question result shows information on the response in a graphical way. The standard information shown is extend with the median, meaning the graph will show:

• deviation
• average response
• number of responses
• median

The system should support reporting on a massive amount of evaluations  - EV-362

A change has been made to the 'loading and processing' of evaluation reporting to support combined reporting on many evaluations. The use case is a user responsible for just under 1000 evaluations in the system and reporting on these evaluations in a single report.

Since this high number was not anticipated, the implemented technique was to retrieve all evaluations and results in one go, which could freeze / block the server for a while and could take a long time causing the user to be detached and the result could not be shown to the user.

A change is made in retrieving the information and generating the reports by retrieving a smaller amount of evaluations and building up the result. Next to this 'pagination approach' some other optimisations have been applied to improve the retrieval speed. An initial test on the test server (limited CPU/memory power) learned the performance went from 10+ minutes to 30 seconds to retrieve and report on just under 1000 evaluations without freezing/blocking the server.

Security

An integral part of our develop and build processes 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.

This release no vulnerabilities has been reported that require mitigation.

For more information on reported vulnerabilities, see the central database of vulnerabilities.

‍

‍For more guidance on configuration and setup of Evaluation, use the relevant Evaluation manual.

This release focuses on performance enhancements and UI improvements to create a more efficient user experience.

This release is pushed to test and production at release date

Improvement

• Issue list loading times have been significantly reduced, with some users experiencing improvements of several minutes. In the coming releases we will change loading of the issue list into a background task so that you do not have to wait for it before starting to work in the allocate overview. This is a part of an initiative to make loading and computing large datasets more performant and robust.
• Enhanced drawer layout provides better visibility and organization of information.. This also includes expanding drop-down lists to fit all text. An example when this is useful is when selecting programmes when dedicating a group. Often the program name was truncated and hard to separate similarly named programmes.

Screenshot of drawer with new layout

Screenshot where dropdown has expanded to fit long program names

• Update of components in the UI, in most cases this will mean minor, often hard to notice, changes, one noticeable improvement improved navigation with keyboard in Allocate Overview filters

This release adds a profile switcher inside Viewer for users who have multiple profiles.

Improvement

You can now change to another profile from Viewer.

After switching profiles outside Viewer, re-entering Viewer can sign you back in with the previous profile. Starting the switch from within Viewer fixes this. When you initiate a profile switch inside Viewer, you will be signed in with the new profile when returning to Viewer.

This option is only available for users with profiles

Screenshot of the usermenu, with the new switch profile option 

Improvements

‍The issues mentioned under the section improvements are considered as new functionality, user experience improvements and 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.

‍

The usage of end-date and terminated in year copy and display should be clear and standardised - CUR-2062

Based on questions and feedback on the usage of the terminated flag and/or the start and end date on objects and the 'sometimes felt magic' we have standardised and streamlined the behaviour.

The standard (and implemented) behaviour is defined as:‍

1. Terminated flag will be used for the 'roll-over exclusion'
   
   • In case an object is marked as terminated, the object will be excluded from the year copy
     ‍
2. End date will be used for the ‘roll-over exclusion’.  
   
   • In case the end date is before the start date of the new year, the object will be excluded from the year copy.
   • The object will only be visible in Curriculum if the end date is not yet passed, thus end date >   start selected academic year. This use case supports ending objects that were not yet ended   before the year copy, but still should not be offered.
     ‍
3. Consistent usage of start and end date on the relevant objects specification (data), study, module-group, module, subject
   Based on the start date the functionality should be:  
   
   • The object should always be visible in Curriculum
   • The relevant pages (structure, list) will have a visual indicator to highlight objects with a start date in the future
   • The relevant pages (structure, list) should have a filter option to only show objects with a start date in or prior to the active academic year, to support visualisation of the ‘this year active setup’.  
     ‍
     
4. The integration should have a configuration option to filter out objects with a start date in the future.  
   
   • For integration with Core and Study Guide this filter should be applied.
   • Filter for other integration depends on the use case of the customer.  
     ‍
5. The integration should have a configuration option to filter out objects with an end date in the past.  
   
   • For integration with Core and Study Guide this filter should be applied.
   • Filter for other integration depends on the use case of the customer.
     ‍
6. On the general tab show the terminated, start and end date information

The behaviour mentioned above is not yet 100% percent finished yet. The main focus was on getting the behaviour defined and implemented for the year copy.
The 'filter option in the pages to filter on end date in current year, the configuration option for integration to filter on end date also requires some more work to be done in the next sprint(s).

‍

A terminated module-group should not be copied in the year copy - CUR-1873

Even if a terminated module-group was marked as 'terminated', the module-group was still copied to the next year. This has been fixed, so the terminated flag will prevent the object from copying over to the new year

‍

As an administrator I want to configure access to the appraisal page based on assessment and/or activity-serie - CUR-2084

A long awaited feature is the option to limit the access to the appraisal page to the different types of information. In the current setup if a user has access to the appraisal page, the user was allowed to manipulate (add, update, delete) assessments and manipulate the activity-series (add, update, delete). There was no option to limit access to only the activity-series, allowing to have the definition of the assessments done earlier in process or by other stakeholders.

A change has been made to the authorisation and the behaviour of the authorisation on the appraisal page. This will support the limitation of access to all options, or only activity-series.

Configuration options:

• Page configuration: Read-only
  All information is available in read-only mode only
• Authorization: EDIT_APPRAISAL
  - Allow access to manage the appraisal tree and the assessments
  - Allow access to the activities owned by the 'you'
• Authorization: EDIT_SCHEDULE
  - Allow access to manage the activity-series and activities

So in order to define the authorization for a role that is NOT allowed to manage the assessment but SHOULD manage the activity series, this should be:

• EDIT_APPRAISAL (not allowed)
• EDIT_SCHEDULE (allowed)

‍

The page template 'discussion' should show feedback, notes and advise - CUR-2090 (Hotfix)

The page template 'discussion' was broken, and didn't show any feedback, notes or advise that has been given. This has been fixed, so the information is shown again.

‍

The description change overview should show changes in numeric lists correctly - CUR-1897

The historic changes overview of the description pages didn't show the changes applied to a numeric list correctly. This has been fixed, so the changes in lists are shown as expected.

‍

Comments defined as while 'impersonating' should be defined under the impersonated person - CUR-1699

In case a user is logged in 'impersonating' another user, any changes or comments made should be registered as changed by X on behalf of. It was noted that not all comments applied this registration. This has been fixed, so all changes applied by an 'impersonating person' are registered with the relevant on behalf information.

‍

Propagation of descriptions to next year should not fail - CUR-2053 (Hotfix)

Descriptions marked to propagated to the next year on change weren't always correctly propagated. In this context propagation is a configuration option to keep data multiple years in sync in case these years are already created.

The use case is that a new year is created based on a copy of the previous year. This means all changes for the new year should be made in that new year. There are however still changes in the current year that would be nice to be synchronised/copied to the new year (even after the year copy). The propagation option is used to configure which fields should follow this synchronisation pattern after a year copy has been done.

‍

The read-only activity-grid should not be editable after reload - CUR-2102 (Hotfix)

In case the activity-grid was defined as a read-only page, the information was shown in read-only mode. However, in case the user did a refresh of the Browser (page), the page was reopened in edit mode. This has been fixed, so the read-only activity-grid will stay read-only even after Browser refresh.

‍

The planboard should support retrieval of multiple offerings in same period - CUR-2086

Since the introduction of the support for multiple offerings in the same period, we now and then get a bug request for a page-template that was missed / not fully corrected changed to support this multiple-offering implementation. The planboard was one of them, and has been extended to deliver support for the multiple offerings in the same period.

Next to this extension, also some usability have been applied to provide an even better user experience.

‍

The activity-grid should not duplicate the scheduled flag in case duplicate offerings in same period are defined - CUR-2015

In line with the above issue, the activity grid had a small issue when using multiple offerings in the same period. In case the 'schedule' flag was used, this was not only applied to the selected offering, but was also defined for the other offerings in the same period. This has been fixed, so the flag is set for the selected offering in period only.

‍

New created module-group in structure should be added to the structure - CUR-2110 (Hotfix)

In case a new module-group is created within the structure tree, it should be added to the module-group / study it was created on. This was not always the case, and after some investigation the cause was identified. The authorisation to change the structure tree, e.g. add the just created module-group, was not correctly for module-group added to module-groups that were deeper than 2 in the hierarchy. This has been adjusted, so the proper authorisation rule is applied, allowing to add the module-group to the structure tree.

‍

An authorised user should be able to remove a module from the structure tree - CUR-2098 (Hotfix)

In some cases an authorised user couldn't remove a module from the structure tree. The cause was the same to the issue above and was an incorrect validation of the authorisation rule on deeper nested module-groups. This is fixed for both issues.

‍

The page template 'methods' should show the defined methods - CUR-2096 (Hotfix)

The page template methods was broken and didn't show the defined methods anymore. This has been fixed, so the methods page will show the defined methods again.

‍

The  validation on activity-series should be limited to the activity-series - CUR-2092

The method-tree page template supports the option to show any validation rules in the defined methods and activity-series. In case the validation was applied, with duration as an required field, the validation always gave an error / warning even if the duration was set. This has been fixed, and the error/warning is only shown if relevant.

‍

The UI should align the columns correctly - CUR-1919, CUR-2070, CUR-2108, CUR-2113

A number of changes has been applied to the user experience / usability. Some small bugs, other to improve the visibility of data. Changes are made for:

• Subjects page columns should be correctly aligned
• Buttons in the structure tree should now exceed the page width
• Column headers in (all) reports should be correctly aligned
• @tag in comments should show the pop-up for user selection in the foreground, to enable user selection.

‍

Bulk select of subjects should respect the configured subject category- CUR-1912

When using bulk select to add multiple learning outcomes (subjects) in one action to a study or module, the provided subject options should be limited to the subject category defined on the page configuration. E.g., only show subjects of category 'skill' or 'learning outcome'. The subject category wasn't used as a filter, so the user could select subjects of any type. This has been fixed, so the shown subject for bulk select adhere to the configured subject category.

‍

The  subject page-template should show the subject categories based on the defined sequence - CUR-1821

In case the subject page shows more subject categories, the order in which the categories were shown was more or less random. This has been changed, so the order will now use the sequence number as defined on the subject category

‍

New page template subject-report launched - CUR-1877

A new report is launched that offers the option to report on all defined module subjects and its added custom-fields.

The report template is having the same options and behaviour as all other reports.

Configuration:

• Create a new custom-page of type subject-report (administration -> custom-pages)
• Add the page as a Tab (administration -> tabs) to for instance the study
  
  • Define the root type to define the object type the subjects should be reported on
    
    • Module: show subjects related to modules (report from faculty, study, module-group)
    • Study: show subjects related to studies (report from faculty)
• Open a study, select the tab to show all subjects defined for modules in context of that study

‍

The filtering on the route-planner should filter correctly - CUR-2022

The route-planner filter options didn't work as it should be. Depending on order of selecting and deselecting the select options could even get stuck, requiring a page refresh. This has been fixed, so the filtering should work as expected, independent of previous actions.

‍

Usage of elements and/or references should not give errors or numeric IDs - CUR-2060, CUR-2088

In the previous sprint (release) some performance optimisations were applied for elements and references. In some cases the created temporary cache was not populated correctly (internet speed, busy laptop, ...), which was not correctly flagged. This could cause that the 'cache' used was not properly setup, causing errors or showing numbers instead of names or codes. This has been fixed, so the cache will be populated, marked as correct and used, or re-populated till it's OK.

‍

The activity-series page template should respect the field configuration - CUR-2072

The activity-series page template provides information on the fields configured for the activity-series. What fields to show is configurable, like with all other objects, but in this case the page template didn't partly follow the configuration and threw in some fields by itself. This has been fixed, so the activity-series template will only follow the configuration.

‍

The offering info in the structure tree should provide a mouse-over - CUR-2048

The introduction of the option to define a pattern when showing offering information, e.g. period and location, the length of the information shown has grown. In the structure tree this could cause effects that the information was partial readable, or even information could be not visible when the column width was exceeded. In order to have access to all information a mouse-over is implemented.

‍

The underlying workflow page should be refreshed in case the data is changed using a workflow popup - CUR-2066

In case a workflow page uses a 'popup' to define information that is shown on the workflow page, after saving the information and closing the pop-up the workflow page wasn't automatically refreshed. The user had to refresh of 'guess' that it was OK. From a usability perspective this could be improved, and in this sprint we've added an automatic refresh of the workflow page in case information has been added / changed for that page using a pop-up.

‍

The changes to the cost calculation base details should only be accessible to the authorised user - CUR-1916

The cost calculation module annual settings on budget, cost division, student flow percentages, etc. were configurable at multiple places and by different roles. This has been standardised to only support configuration of the 'faculty / organisation' based settings at faculty level by the user (role) having access to this specific information.

The information could also (partly) be modified in the cost-structure page. This 'change' option is removed, and the information is only in read-only available.

‍

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 subject CSV to support related IDs - CUR-2015

The subject CSV is extended with support to define related ItDs. This allows when adding a subject to a module to define the study/studies the subject is related to.

‍

Improve error handling and messages for the routes-step CSV import - CUR-2085

The CSV import of route-steps didn't provide a proper functional error message, but more a technical error. This has been changed so in case import fails a more functional message is shown to help the admin in finding the root cause of the failure.

‍

Security

An integral part of our develop and build processes 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.

‍

This release no vulnerabilities has been reported that require mitigation.

For more information on reported vulnerabilities, see the central database of vulnerabilities.

‍

‍For more guidance on configuration and setup of Curriculum, use the relevant Curriculum manual.

With this release we improve the suport to copy allocations between groups and added a settings menu restricted to Administrator users.

Improvements

Manual allocation - Copy group

The manual allocation workflow is now improved for the use-case when you want to copy allocations from one group to another group, even between different modules. Allocate makes sure to only allocate enrolled students, making it perfect for maintaining consistent group composition.

Key benefits:

• Maintain student groupings across different activities and modules
• Save time by bulk-copying allocations instead of manual selection
• Reduce errors with automatic filtering of eligible students

Screen recording of user copying allocations from two tutorial groups (totally 8 students) to a lecture group.

Settings menu

We've added a dedicated settings menu in the top bar for Administrator users to improve discoverability of important functions restricted to Administrator users:

• Auto Allocate button is now "Run Auto Allocate" in this menu
• Clear cache has been moved from User settings to this menu

The release notes provide information on the features and improvements in the specified version.

Improvements

The issues in release mentioned under the section improvements are considered as new functionality, user experience improvements or bug fixes.

‍

Descriptive text marked as bold in Curriculum should be shown bold in Study Guide - SG-458

In case a (part of the) text in Curriculum was marked bold, it was not shown bold in Study Guide. At the end it was not an issue in Study Guide, but an issue that has been resolved in Curriculum.

‍

The period bar should be correctly aligned and not exceed the page boundary - SG-457

When opening the module details showing the period information as a bar on a Windows laptop, the information was not properly aligned and was exceeding the page width. After further investigation it looks like it's not Windows, but Browser related, since the issue could also occur on Mac in specific Chrome versions. A change is applied to alignment, to show the information as expected in the different Browsers.

‍‍

The accessibility of Study Guide should be improved - SG-468

Improving user experience and accessibility of the products is a constant process. This sprint we added a new version of the automated WCAG compliance validator and it noted 25 accessibility errors and warnings. The errors found all did not correctly implement one of the 4 underlying WCAG rules.:

• no-static-element-interactions
  Flags elements like <div> or <span> that have interactive behaviour (e.g. onClick) without proper semantics (e.g. <button>, <a>). Forces you to use actual interactive elements or explicitly assign roles.
• click-events-have-key-events
  Ensures that clickable elements are also keyboard-accessible (onKeyDown, onKeyPress, etc.). Fix is to add matching keyboard handlers.
• role-supports-aria-props
  Validates that ARIA props (like aria-expanded, aria-label) are only used on roles that actually support them. Prevents silent failures in screen readers.
• mouse-events-have-key-events
  Prevents mouse-only interaction traps. If an element uses onMouseDown or onMouseUp, it should also support equivalent keyboard interactions.

The advised / required changes has been applied to meet the WCAG rules and improve the accessibility.

‍

The configurable banner should support filtering on additional values - SG-465

The configurable banner that enables to show a banner in the study guide has been released recently. The support to configure when the banner is shown is extended with additional support for filtering, including additional values.

Just as a reminder how to configure the banner widget.

• Define a widget of type banner-widget
• Add an INFO field that will define the 'banner text' to be shown.

• Specify the field details, including the filter, title and the banner text (description) to be shown
  In the example the filter is on year. Be sure to use the code of the academic-year (or other fields) defined in Curriculum.

• Test the result.
  In the next image the banner is shown, since the selected year 2023 matches the defined filter.

• Test the result.
  In the next image the banner is not shown, since the selected year 2024 doesn't match the defined filter.

Persons assigned to a role should be shown on separate lines - SG-474

A bug has been introduced in the last version that causes persons assigned to a role, e.g. the module lecturers, where shown on one single line. This has been fixed, so the persons are shown again each on a separate line.

‍

Configuration option added to use the 'Broker' as the data source - SG-201

The 'Broker' is a read-only source that is fed by Curriculum, based on data published by Curriculum to the 'Broker'. The broker is optimised for reading and has 'complete documents' that are ready to process, where Curriculum has to combine all objects to a final document with all the required information.

The configuration option allows to define the broker as the source, using the published data from Curriculum. The (nightly) synchronisation will NOT use Curriculum, but use the published data in the Broker. Initial tests show that synchronisation taking 2 hours is now run within 10 minutes.

The setup of the Broker requires additional configuration that is best done in close cooperation with TimeEdit support.
In case test driving the Broker is desired, please sent a request to the support desk.

‍

Security

An integral part of our develop and build processes 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.

This release no vulnerabilities has been reported that require mitigation.

For more information on reported vulnerabilities, see the central database of vulnerabilities.

‍

‍For more guidance on configuration and setup of Study Guide, use the relevant Study Guide manual.

‍

The release notes provide information on the features and improvements in the specified version.

Improvements

The issues in release mentioned under the section improvements are considered as new functionality, user experience improvements or bug fixes.

‍

It should not be possible to create reports without a name - EV-350

When configuring a new report the name field was not a required field. When saving the report was created with no name, and could not be selected (for change) anymore since the 'edit select' is using the name as the selectable section.

A change has been applied to set the name of the report as a required field, and as part of the release any historic created report without a name will get a dummy name that allows selection and modifying them.

‍

Support usage of the new TE topbar - EV-352

The default TE topbar supporting switching between the different TE products is made available for Evaluation and changed to use the latest version.

‍

Change default help URL's to the TimeEdit academy - EV-358

The Evaluation help URL's were still pointing to the old, no longer existing, documentation. This has been adjusted and the links are updated to the new documentation on the TimeEdit academy.

‍

Security

An integral part of our develop and build processes 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.

This release no vulnerabilities has been reported that require mitigation.

For more information on reported vulnerabilities, see the central database of vulnerabilities.

‍

‍For more guidance on configuration and setup of Evaluation, use the relevant Evaluation manual.

‍

Available on Test & Production on Wednesday 13th of Aug 2025 for all customers

New functionality

• Added the ability to filter by (preferred) weekday(s) for activities in both Data Manager & Activity Manager
• Added the ability to filter by (preferred) start time for activities in both Data Manager & Activity Manager

Improvements & bug fixes

• Further performance improvements in the Study Combination workflow 
• Several minor bug fixes across the whole scheduling product area

Available on Test on Wednesday the 13th of Aug for all customers

SSO & TE accounts now available for recipients

• It's now possible for recipients to log in via the TE Auth service (in the same way as the rest of the product suite) enabling recipients to either log in via SSO or their TimeEdit account
• Recipients and users are matched via email address. So, when adding/importing recipients in Preferences, please make sure to use the exact same email address as the corresponding users have.

Notes

• Current ways of authenticating users (link sharing & pin code) still works exactly as is, but can't be combined with using SSO or TimeEdit accounts

Improvement

• Clearer guidance when a reservation needs confirmation so it is not automatically canceled.
• Removed the lock icon on bookings that needs to be confirmed (but not opened for confirmation), since it did not add value to the experience.

This release focuses on enhancing the user experience in the calendar view and improving information accessibility in the Allocate Overview.

Improvements

• In the calendar view within Manage Student and Registration, the timespan is now automatically adjusted to show only the first through last reservations of groups within the selected activity. This helps users focus on relevant weeks and reservations, particularly useful for activities with few or no recurring reservations when you don't need to view the entire semester.

Screenshot from calendar where timespan is reduced to the two weeks where the activity actually has reservations

• The Allocate Overview drawer now automatically expands in width when the Allocated Students section is expanded, providing better visibility of all student details.

Bugs

• Fixed a permissions issue where users with Allocate::user scope could incorrectly access the Registration period page.
• Resolved an issue where student conflicts weren't properly loading in the student adjustment view.

Improvements

‍The issues mentioned under the section improvements are considered as new functionality, user experience improvements and 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.

‍

The personal allocation should provide more granular insight - CUR-1749

The issue title doesn't fully cover the changes applied. A complete overhaul is done of the personal task list, but also the reporting on task assigned and spread of hours allocated has been extended with support to display on year, period and month basis. Next to that additional visualisation options are added to provide clear insight in over and under allocation, grouping of allocation per category, drill down per category to get insight in the underlying assigned tasks (both educational and non-educational).

The best way is to throw in some screen shots to visualise the changes, but first the overall list of changes applied is provided:

• Support for two display modes
  
  • Separated:
    
    • One table per task category, as before.
  • Nested (new default if not configured):
    
    • All categories collapsed by default.
    • Shows:
      
      • Allocation percentage (relative to total hours across all categories)
      • Total hours per category
      • Clicking a group expands the corresponding task table.
  • Configuration: Set the view-mode of the task list to nested or separated§§
• Added a general summary
  • Now shows available hours, allocated hours and remaining hours
  • And a progress circle, showing the utilisation percentage
    • Blue when <100%, outside year margin
    • Green when within year margin
    • Red when exceeding year margin

• Added extended period and month filter:
  • Dynamically generated based on the year config.
  • Uses the active browser language for month translations (so month labels are fixed).
  • When a period is selected, only months within that period are shown. Note that a month can appear in multiple periods, or the other way around.
  • Changing the period resets the month filter.

• Introduced a monthly detail overview
  • Respects period, month, period factor, and year-based task logic.
  • Only shows months overlapping with the selected period.
  • Month column header shows tooltip on hover:
    • Full month name and year
    • Total days in month
    • Days in this period
  • The following rows are shown:
    • Available hours: (correctedHoursOfTasks * period factor) * (daysInMonthOverlap / totalPeriodDays)
    • Allocated hours: Sum of corrected task hours in this month (based on overlap)
    • Remaining hours: available - allocated → Red cell if negative
    • Utilisation %: (allocated / available) × 100 → Cell background is green linear gradient from 0% (bottom) to 100% (top)
    • Task count: Total tasks in the month, note: includes non-period-based (year-based) tasks
    • Not yet implemented: unavailability tasks are not yet added, will be in the next release

‍

The personal taks overview structure

The personal task overview provides a number of panels showing relevant information on a specific area to the resource manager

Information panel

The top panel is the information panel that supports definition / showing of notes that are applicable for the staff member.

Utilisation panel

The utilisation panel is split in two different sub-parts:

• the first part provides the high level allocation information for the selected period
• the second part will provide the detailed information on a monthly base

The period selector and the Month selector can be used to limit the display.

Colouring highlighting is used to visualise the under / over allocation of the user.

Selecting a period or a specific month will filter the information.

Task overview panel

The task overview panel provides the grouped allocation for the defined task groups. The groups (tag) are configurable and depending on the installation more or less task grouping will be shown.

‍

The 'grouped task' can be expanded to enable change and visualisation of the underlying details (non-)educational tasks.

‍

The readability of the workflow information message should be better - CUR-1828

The workflow configuration provides the option to show an informative message to the users to inform what the workflow is for (introduction page) or what is expected from the user on the consecutive pages manipulating or validating data. The message display was pre-styled, having limited benefit from the offered HTML visualisation options to highlight specific points of interest to the user.

An improvement is applied to the display of the message. The message display is standardised and will appear in the same format on all pages. Furthermore the 'preset' styling is reduced to enable the benefits of the HTML styling options and highlight the relevant sections. The readability is improved by adjusting the alignment.

‍

The readability of the dashboard task overview should be improved - CUR-1722

Due to some recent adjustments to the dashboard taks overview, it was noted the readability was reduced. An improvement has been applied to get the readability up to the expected standards by grouping information, improving the visibility between the distinct tasks and other usability and readability improvements.

‍

The availability report should support export of a full year - CUR-2041

In case the person weekly availability pattern was captured based on years, it was not possible to report and export on the full year. This has been fixed, so in all cases (period and/or year based) the report can be generated and exported.

‍

Curriculum is considered much slower - CUR-2029 (Hotfix)

In the last release a UI-component was introduced that affected the users' performance. In fact the overall response time when requesting a page or report from Curriculum was significant slower. The cause was identified and a hotfix is applied to get back to the expected performance level.

‍

If the export type is set to ignore, the change should not be marked open - CUR-2014

The export type can be set based on change type. The export type will define if the change should be open and approved by a stakeholder in the process (manual), if it's automatically approved or if it's just ignored (and thus considered approved). The issue noted was that if the export type was set to ignore, the behaviour was that it was handled as a change to be approved manually. This has been fixed, so an export type set to ignore will be ignored and not require manual approval.

‍

Terminated modules should not be copied as part of the year roll-over - CUR-2038

The year rollover is used to create a new version of the Curriculum for the upcoming year. This will be the 'start version' for all change requests and approvals. In case modules are terminated, they should not be copied over to the new year, since they just ended in the last year. The year roll-over however didn't correctly process the terminated modules and copied them over to the new year. A fix is applied to guarantee terminated modules are not copied over during the year rollover.

‍

Offering values should not be duplicated as part of the year roll-over - CUR-1984

Another issue found in the year rollover was that offering values were duplicated. This was introduced by extending the option to offer the same offering period multiple times. The year rollover has been adjusted to cope with this change and only copy the values over to the relevant period, instead of duplicating the data to the different periods.

‍

Custom objects (item) defined on specification should be year-bound - CUR-1879

Most of the objects in Curriculum are fully year bound, and all changes and information resides within the context of the year. There are a few exceptions, like faculty, organisation and specification. These objects are not fully year bound, since they are not changed yearly and are considered more 'global stable' objects.

These 'less year bound' objects still have specific sub-objects that are year bound. For instance the descriptions of a specification are year bound, since this might change from year to year. In case a custom sub-object (item) is added to the specification it is considered as a 'global stable' object. This behaviour for custom sub-objects has been changed to a year-bound behaviour. This will allow to make and approve changes to the custom-objects that are year bound including the historic audit trail and historic view in the previous years.

‍

The activity-grid should not exceed the screen width - CUR-1885

In case a week had over 7 activities planned, the activities above seven were pushed outside the screen to the right. This has been fixed and in case the number of activities exceed the screen (browser) width, they will wrap-around and create second row.

‍

Activities disappear and appear when opening / closing a different period - CUR-2055

In case in the activity grid multiple offerings were defined for the same period the behaviour was incorrect. Depending on the sequence of actions the opening of a period could show the activities from the other (same) period, or just show nothing. Refreshing the page caused showing the correct data, which meant that it was a user interface issue and not a data issue. The cause has been found and fixed, so the correct activities will be shown for the selected period.

‍

The activity-serie-edit custom page template should support activity-series based workflows - CUR-1965

The activity-serie-edit custom page template is extended with support for edit based on a workflow configuration.

‍

Activity-planning custom page template should respect the field configuration - CUR-2020

The activity-planning custom page didn't respect the field configuration, and just showed all fields. This has been fixed, so the activity-planning page will use the configuration.

‍

The offering pattern (period + location) should be applied to all pages displaying period info - CUR-1999

In the previous release the option was introduced to define a display pattern for offerings. Allowing to define a pattern that would show the offering and its location, e.g. S1 (Rotterdam). The pattern was not yet implemented in all page templates. In this sprint the pattern has been extended to the following page templates:

• activity-grid
• activity-card
• activity-list
• teacher
• teacher-assign
• appraisal-scheme
• method-scheme

‍

Bullet points in HTML text shouldn't add extra bullets and/or empty lines - CUR-1950

When using bullet points in the HTML text editor during save 'new lines' where added and these new lines would changed to bullets. Causing a bullet list with a bullet that was defined by the user and an empty bullet underneath, effectively doubling the number of bullets. This has been fixed, so no 'empty bullets' will be introduced anymore.

‍

Time related information should be shown in hh:mm in the activities-series-report - CUR-1743

The display of time information has been standardised in the previous release. It was noted we missed to set the the displays to hh:mm for the activity-series-report template, which has been fixed in this sprint.

‍

The sum of columns in reports should show a maximum of 2 decimal digits - CUR-1944

In some report pages numeric fields are automatically added up and shown as an additional row underneath the last item. The display of the summed value was not consistent and in some cases the value was shown as a 'BigDecimal' that could lead to 12 decimals. This has been fixed, so any sum up number will either be shown as a whole number (all values are integer) or as a two-decimal value (any of the values is a decimal).

‍

Subject matrix header match shouldn't show the match counter upside down - CUR-2019

The subject matrix header provides information on the learning goals and the number of 'matching modules' that contribute to the learning goal. The matching modules number was shown upside down. This has been fixed, so the users don't have to put their laptop upside-down in order to read the number.

‍

Subject should support expand of groups with owner and without owner - CUR-1763

The management of learning outcomes is in previous versions extended to support assigning a learning outcome to a module in context of a specific study program. E.g. learning outcome A contributes to program A and not to program B, even though the module is in both programs.

This configuration supports the configuration and visualisation of pathways based on learning outcomes. Two filters should have been made available, one that filters either all matching modules from study level (default behaviour) and one that filters all 'directly study related' modules. We succeeded in mixing the filters up in the previous release, but has fixed it in this version.

‍

‍The scale shouldn't need a color - CUR-2017

In case a scale (level) was defined that has no assigned colour, an error was thrown when using that scale. This has been fixed, so scales can be used without error with and without colour assigned.

‍

The assessment matrix should behave like a matrix report - CUR-1902, CUR-1924

In a previous release the assessment matrix was introduced. This matrix report will provide an overview of all used assessment types in a program, and allow validating the spread of different assessment types, the usage of the correct type and other quality related validations. The implementation was technically finished, showing the data, but needed the proper functional reporting support that is available for all other matrix-based reports.

In this version the to be expected functional enrichment of the 'technical implementation' has been done with the following improvements:

• Sum of the number of assessments in the header (total), similar to subjects
• Filter on the assessment type, just like subjects. E.g., show all modules that offer a Digital
• Ability to add two columns, similar to subjects (e.g. period, phase)

‍Cost information shown at module, group and study level should be consistent - CUR-1930

The cost information defined using the 'cost lines' on activity-serie and module is reported in the structure by grouping and summing all data up to the parent level. The module-group will show the summed cost information from all underlying modules (and groups) and the study will show the sum of all underlying groups. An error was found in the 'summing' and the total shown at study and/or module-group could differ from the actual sum of all underlying modules. This has been fixed, so the summing will give the correct value based on the underlying information.

‍

Delete of news items should be supported - CUR-1968

A slightly usability / behaviour issue was found when deleting a new item. The message was shown the new items was deleted, but the news item was still visible in the overview. In fact the news item was deleted, but a manual refresh of the page was required to get it out of the list. This has been fixed, so after deleting a news item the list will be refreshed automaticallly.

‍

A change in custom-field data type from Element to Reference should not give an error - CUR-2027, CUR-2040

A tricky one that will only occur during implementation is the change of the type of a custom-field that is already populated with values from the old type. In this case the field type was changed from an Element to a Reference type. Since the field was already populated, an error was thrown when the user opened an educational object that was pointing to the 'Element value' instead of the 'Reference value'. In a production environment a 'repair' would have been executed on the data to set the correct values.

Since this situation might happen more often in test / acceptance / implementation settings a change has been made that will allow change of type and will 'ignore' the error in case data has been populated base on the previous type.

‍

A field updated on a form page should also be updated in the Admin tab -CUR-2023 (Hotfix), CUR-2047

Sometimes an issue pops up that everyone is puzzled. And this is considered a highlight in this area.

The basic setup it started with was a custom-page of type form with an editable date field and the same field was also available on the default administration page. In case the date field was changed on the form page it was saved. When opening the administration page, the 'old date' was shown. And when the administration page was saved the 'old date' was saved. The cause has been identified and fixed, so the administration page will show the correct data and will not save any 'old' data anymore.

‍

The access control for nested module-groups should be respected- CUR-1074

It was noted that the access control that is used to define the allowed rights on module-groups was only applied for the top-level module-group (the module-group(s) directly bound to the study program). This has been fixed, so the access control to module-group is applied to all module-groups in the structure.

‍

As an administrator I should be able to change the default login URL - CUR-2036 (Hotfix)

The default login URL is used to specify the handling of the standard login. It will allow redirecting users to the SSO login, but also to the 'support' login.
Based on system (test, acceptance, production) the login might vary. In some cases on test there is no SSO, or it might be implemented later, so the login may vary over time or system. The configuration was a technical configuration on the server to be done by an engineer, requiring restart. This has been changed and the default login is moved to the Administrator -> Config menu to support change of the URL without engineer or restart requirement.

‍

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 appraisal CSV to support external ID - CUR-1870

The appraisal CSV is extended with support for the external ID. This allows updating an existing appraisal by using the same external ID.

‍

Security

An integral part of our develop and build processes 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.

This release mitigates the following vulnerabilities:

• CVE-2024-43788 (6.1)
• CCVE-2025-30359 (5.3)
• CVE-2025-30360

For more information on reported vulnerabilities, see the central database of vulnerabilities.

‍

‍For more guidance on configuration and setup of Curriculum, use the relevant Curriculum manual.

Available on Test on Thursday the 31th of July for all customers

We’re proud to announce the first release of the Object manager, a powerful and modern tool designed to replace the legacy Java client and bring object management directly into the web-based Admin interface.

Why this matters

• Removes dependency on Java installations
• Enables wider accessibility and fewer IT hurdles
• Streamlines configuration directly in Admin
• Sets the stage for scalable object management workflows

Key Capabilities

Create and manage objects

• Create new objects with rich metadata
• Add related elements: memberships, organisation nodes, availability, and optional relations
• Compare object details side-by-side for clarity and control
• All edits now support instant field validation, improving feedback and accuracy during entry

Filter and search

Filter by:

• Object typ
• Organisation node
• Any field using flexible search parameters

User friendly editing

• Edit individual objects in a clear UI
• Designed to simplify routine object maintenance

Upcoming improvements

• When adding relations or memberships, all object types are currently displayed — even those without a rule setup for the displayed object type. With the next release, only object types that have a rule configured for the object type you are editing will be shown, ensuring a more relevant and streamlined selection.
• While the initial release focuses on single object creation and management, upcoming iterations will include:
  
  • Bulk editing – Edit fields, assign org nodes, inactivate or add multiple objects at once.
  • Import/Export – Support for batch import/export by object type and matching filters.

Required permission To access the Object Manager in Admin, the user must have the scope: TE_Admin::admin.

‍

Available on Test on Tuesday the 29th of July for all customers

Available on Test on Tuesday the 22th of July for all customers

The release notes provide information on the features and improvements in the specified version.

Improvements

The issues in release mentioned under the section improvements are considered as new functionality, user experience improvements or bug fixes.

‍

The member report should show the student participation- EV-348

The member report with the student responses provides only the total number of students that have responded the evaluation. A change has been applied to not only show the total number of respondents but also the response rate (%).

‍

The 'raw answers' report download should also include standard questions - EV-349

The 'raw answer' report download option only exported so-called member questions. This has been extended to not only export the member questions but also the standard questions.

‍

The teacher should only be evaluated once - EV-351

In case there are multiple member blocks defined, the persons (teacher) defined were shown multiple times (for each defined member block). A fix has been applied that will prevent this from happening and only show the person (teacher) once if there are multiple member blocks defined.

‍

Security

An integral part of our develop and build processes 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.

This release no vulnerabilities has been reported that require mitigation.

For more information on reported vulnerabilities, see the central database of vulnerabilities.

‍

‍For more guidance on configuration and setup of Evaluation, use the relevant Evaluation manual.

‍

The release notes provide information on the features and improvements in the specified version.

Improvements

The issues in release mentioned under the section improvements are considered as new functionality, user experience improvements or bug fixes.

‍

As a user I want to see which 'tab' I'm on in the Browser title - SG-473

The shown Browser title was always default to the standard configured title, e.d. Study guide. So in case multiple Browser tabs are openen showing different Study guide tabs, e.g. Programs, a Module, a Minor, these are all name 'Study guide' in the Browser Tab title. A change has been applied to use the name of te selected Tab or Product (individual Module, Program) and so improve user experience and usability of multiple tabs.

‍

As an administrator I should be able to select and configure descriptive texts - SG-464 (Hotfix)

Due to a change in the previous release the description select-box used to select and configure descriptive texts in the different widgets didn't show any items anymore. This has been fixed, so the Curriculum configured descriptive text items are available for selection again.

‍

Switching between the student and staff AI-agent should reset the conversation - SG-471

When switching between the student and staff AI-agent, the conversation and 'AI learned context' was not cleared but kept. This could cause incorrect results, since the context was considered in responding to the users prompt. This has been fixed, so changing the AI-agent tab will reset the context, so the proper AI-model and context is used.

‍

As an administrator I want to configure context relevant 'pre-set' AI prompts - SG-439

The AI function supports the usage of pre-set prompts that can be used to assist the users in providing ideas and reuse these prompts. Especially for the staff AI external (module) matching functionality that matches external obtained modules / minors against the institutes offered modules and minors preset prompts that only requires to paste the external module information to execute the match will be a great help and time-saver.

These pre-set prompts were hard-coded and not changeable by the admin, to improve prompts to the institutes context, create new prompts. In this release the administrator option has been added to define and configure prompts. The defined prompts will be shown to the user in the relevant AI agent (staff or student).

The staff AI-agent shows the different configured prompts above the prompt area. Clicking the pre-configured prompt will copy the prompt text into the prompt area.

Configuration

The administrator can configure prompts using the menu-option Chats.‍

• To add a new prompt, select the prompt button.
• To edit a prompt, click the 'pencil icon'

‍

The prompt information has 4 fields:

• Title: the title is shown as the clickable prompt information (balloon-button) above the AI-prompt section.
• Prompt: the prompt text that will be copied to the prompt area after clicking the prompt title (balloon-button)
• Authenticated: indicator if the AI-prompt is for the staff (authenticated is set) or the student AI-agent
• Visible: indicator if the AI-prompt should be shown. This supports definition of prompts, set them invisible instead of deleting and recreating them later.

Multiple different prompts can be defined as shown in the example. The list provides a mixture of prompts that are relevant and ease usage for the staff, but also provide helpful ideas and direct useful prompts for the students.

‍

Security

An integral part of our develop and build processes 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.

This release no vulnerabilities has been reported that require mitigation.

For more information on reported vulnerabilities, see the central database of vulnerabilities.

‍

‍For more guidance on configuration and setup of Study Guide, use the relevant Study Guide manual.

‍

• Added a functionality limiting very large object searches in the object selection box in Core, to help prevent performance issues by guiding users to narrow their search
• Add the possibility to filter on AutoPilot's error codes in AM, helping the users the find activities that couldn't be scheduled based on the same issue and thereby working more efficient to resolve the underlying issues
• Bug fixes/small improvements:
  • Made the sorting on alphabetic order of members working in membership exceptions 
  • Adjusted so size reservations are shown correctly when booked side by side 

• Improvements of Study Combinations:
  • Performance improvements to the Student Set generations, decreasing the generation time substantially
  • Shared activities are now taken into consideration when generating Student Set, marking the final process step of Shared Activities in it's first version completed
  • Student Set generation can now handle diverging sizes of track, in cases where the sizes are different on the different tracks in the same activity series
• It's now possible to add exact start time and weekday(s) when importing activities, letting you use these when scheduling as soft or hard constraints
• Introducing Calculated Fields, letting you have an activity field in Data Manager and Activity Manager that sums the values of a field on one or several objects
  • A common example is your student group sizes, where this field now can give you the total value of several student groups sizes to reflect the most recent enrollment estimations
  • The field is configured in DM by extending an existing import template or adding it while creating a new import template, adding a new column to your activities

Improvements

‍The issues mentioned under the section improvements are considered as new functionality, user experience improvements and 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.

‍

The styling should be consistent - CUR-1986, CUR-2004 (Hotfix)

Due to the migration to using a different UI components the visualisation of some screens and components was not as clean and crisp as it should be.

• In some cases the content of the page was not shown in a clean white area, but was partly shown in the blue footer. This has been fixed in all cases identified.
• The date-time component could cause a loop when reloading or refreshing the page.

‍

Expressions used on specification should be year dependant - CUR-1959

When using expression on fields at specification level, the academic year was not respected, the values and operators used in the expression always used the first year the specification was created. This has been solved, so the year will be respected in expressions.

‍

The edit/create button for references should not disappear from the screen - CUR-1929

In case references were defined with a long definition, the definition display was not truncated causing the buttons to manipulate the reference were moved outside the screen. This has been solved to limit the shown length of the condition, so the various buttons are always visible.

‍

Offering pattern should be shown correctly - CUR-2000

In the previous sprint a pattern has been added to the offering to support configuring the display. There was an error in the shown formula example. This has to be:

• ‍join(:name, ' (', :(offering) location, ')') (instead of join(:name, ' (', :location, ')')

Next to that the pattern was only used in the structure tree. This has been extended and the pattern will now be used in all pages showing offering information.

‍

Add filter to subject matrix to support filtering on directly assigned subjects - CUR-1952

In case a subject (learning outcome / skill) is assigned to a module, based on configuration the module/subject combination can be assigned to specific programs. This means the module can have subjects that are just defined, and subjects that are defined and related to one or more programs. If a module has different subjects, they can be assigned to different programs.

The standard behaviour of the subject-matrix is that all modules and their subjects are shown if the module is part of the program. The new added filter allows for filtering to only show the modules that have a defined relation with the program at subject level.

‍

Module sorting in program overview is incorrect - CUR-1964

Due to the change with the offering pattern the filter order for modules in the program overview (structure) didn't sort correctly on period. This has been fixed, so the sorting is as it was before

‍

Add support for Finnish - CUR-1967

A new language pack to support Finnish has been made available.

‍

Column headers should be shown more compact - CUR-1977

The display of the column headers was broken, showing the column header and its options spread over 3 lines instead on a single line. This has been fixed.

‍

Dashboard tasks should be shown more compact - CUR-1978

The display of the dashboard tasks was broken, showing the task information spread over 3 lines instead on a single line. This has been fixed.

‍

Date information shown on a form page and admin tab should be equal - CUR-1961

There was a difference in displaying (and storing) dates between the admin tab and the form tab. This has been fixed.

‍

When deleting a task, this should be removed - CUR-1943

When deleting a task from a persons assignment list a message was shown 'task successfully deleted', but not in all cases the task was actually deleted. The cause has been found and fixed, so it's now possible to delete the tasks.

‍

Performance

The main focus for this sprint was on the performance issues reported when using extensive Workload Management based on large numbers of activities and using the Teaching structure / Schedule preferences screens with large numbers of activities (>200). A deep dive is done to find the cause and solutions to tackle these performance issues and give expected response times in these cases.

Activity hour and course budget calculation should not give server timeout on calculate - CUR-1921

There were indeed cases the server ended with a server timeout, depending on the number of activities and lecturers to be calculated when hitting the calculate button. The processing and calculation method has been improved and for the provided real-life cases that showed this behaviour the response is change from 'server timeout' (60 seconds) to an almost instant response.

‍

The activity report should provide proper response when filtering - CUR-1860

When using the activity report at faculty or program level having hundreds or even thousands of activities the behaviour was to always retrieve all data and then show the screen. At that moment the user could use the filter to select for instance the activities from a specific program or module(s).

Besides the performance changes in retrieving the activity information the page has been changes slightly. The user is first asked to provide a filter, since in most cases a filter list is required, before fetching the activities page by page. This will immediately give a proper response in a much shorter timeframe, and thus improving usability and user experience. The user can than filter within this subset.

‍

The activity report performance should be improved - CUR-1981

When retrieving the activity report, the performance was not good with high numbers of activities. This was caused by the fact the activity list validated each activity shown on validity. Where validity is the check if all required fields are defined on the activity. This could lead to a lot of checks.

In a proper designed process, the activities should be created correctly. The main role of the activity report is to provide an overview of the activites and manage the shown activities. This task does not require a full validation of each activity.

Since there are cases a full validation is still required, and there are cases the validation should not bother the function executed at that moment a configuration option is added to support 'validation' and 'no validation'. The default behaviour is 'no validation', by checking the option validate the validation behaviour is activated.

‍

Reduce the requirement to use individual activities - CUR-1858

Part of the performance issues are caused by a huge amount of activities. The original design is based on activity-series that contain activities. This leads to a reduced number of object compared to single activities and has the benefit of keeping track which activities are related.

Due to the fact activities in an activity-serie should all be the same (except for the activity week), in case for instance the title of an activity in a serie was used to express to students the content of the activity this was not possible. The fall-back in this case was to create all individual activities. Leading to a usage of the system in a non-anticipated way, with the mentioned drawbacks.

Based on the analysis a change has been made to stimulate and improve the usage of activity-series. The change applied is that activities within an activity-serie can have a different name and remark (multi-lingual).

‍

Retrieving the effort-list performance should be improved after recalculation - CUR-1951

The retrieval of the effort-list after a recalculation could take quite some time, depending on the number of tasks and staff assigned. The calculation, refresh of the information and retrieval of the information have all been revised and changed to provide a proper performance.

‍

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.

‍

Gradually stop support for Basic Authentication - CUR-2001

As part of the migration from all test and acceptance environments to the shared TimeEdit Google stack, the support for authentication using Basic Authentication will be reduced. Existing configurations will be supported, but the advise is to migrate the interfaces using Basic Authentication will be migrated to using Bearer tokens for authorisation.

No action is required, but be aware that new integration requiring authentication will only support Bearer Token.

‍

Extend API and CSV support for standard routes - CUR-2001

Some time ago support to define and use standard routes for curriculums is added. A standard route provides a way of defining multiple routes with an advised path for students including modules, period and advised year. This can be used to provide specific info for September and February start, but also a route for a specific qualification or diploma.

Support for CSV upload is added, where the documentation is available via the Administration / CSV menu option.

Support for API upload and retrieval is added, using the endpoint route. The implementation details are available in the API documentation at https://timeedit.readme.io

‍

Security

An integral part of our develop and build processes 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.

This release mitigates the following vulnerabilities:

• CVE-2025-49146(8.8)
• CVE-2025-22233(2.29)
• CVE-2025-41232(9.3)
• CVE-2025-41234(7.4)
• CVE-2025-48988(7.5)

For more information on reported vulnerabilities, see the central database of vulnerabilities.

‍

‍For more guidance on configuration and setup of Curriculum, use the relevant Curriculum manual.

This release improves the manual allocation workflow with improved group drawer functionality, allowing users to view and select students more efficiently.

The release will be available in test environments 10-07-2025, and in production environments 17-07-2025.

Improvements

Manual allocation

When it's not possible to automatically allocate students you sometimes need to resort to manually allocate students to the student groups. In this release we improve the system support to do this in a safe and efficient manner directly from the group drawer.

In the drawer its now possible to see allocated students

From the drawer, you can select from a list of enrolled students, to allocate to the group

In the next release we will also make it possible to copy allocations from another group, this group could be any group from any module. This feature will be useful when you want to keep a group of students together between different activities within or between modules.

Automatically update allocate proposal table status

The allocate proposal table is now updated is now updated every time its expanded, and as soon as status is updated removing the need to update the table.

Bug fixes:

• Fixed an issue where the number of students with incomplete allocations was incorrectly reported at the module level when only one activity was selected. The count now accurately reflects the number of students with incomplete allocations at the activity level.

Improvements

The issues in release mentioned under the section improvements are considered as new functionality, user experience improvements or bug fixes.

‍

Extend AI support for external course matching - SG-441

An add-on to study guide has been launched supporting administrative staff an AI-supported way to find matching modules for (new) students with external obtained credits. This AI-assistant is separated from the student AI-coach that helps students searching for programs, minor and/or courses that match their requirements.

In this release the employee AI-assistant response model has been changed to improve the behaviour, matching and response. Next to that the pre-configured question support is enhanced to only limit copy/past of the external module transcript that need to matched against an own module.

‍

The tab (order) of the AI-assistant and AI-coach should be configurable - SG-443

The tab and tab order of both the staff AI assistant and the student AI-coach was pretty 'hard-coded'. This has been changed in order to support the both AI entries as standard widgets with all the configuration options of standard widgets and the ability to add them to tabs. This includes providing an own title, AI introduction text, tab title and tab order.

Next to the standard Tab configuration two new options are added:

• authenticated - indicator to only show the AI-tab when authenticated. Typically used for the employee AI-assistant
• icon  - font awesome icon , used to add an star icon in front of the Tab title. For instance the ai-starts

Configuration:

• Add a widget with no Object type selected
• Set the widget type to Coach
• The label is used as the page introduction shown on the AI widget

• Add a new Tab
• Select the just created widget
• Define a Label for the tab
• Set the Sequence for the tab
• Optionally add an Icon shown in front of the label, e.g. wand-sparkles
• Set Authenticated if the widget configured is only for authenticated users (staff)

The assessment widget should be properly aligned - SG-447

The information message shown in the assessment widget was incorrectly aligned and dragged to the left. This has been fixed, and the information shown is again properly aligned.

‍

The study guide subject matrix should display colours and icons - SG-453

In Curriculum enhancements have been applied managing subjects with respect to using colours and icons displaying the level of the related subject. This release added support to the study guide subject matrix representation for the defined colours and levels.

Ideally it should be possible to use banner-like information display to users - SG-452

The functionality of the study guide is enhanced to support 'banner-like' information display. For example an highlighted information message shown in a tab or all tabs to highlight a year is not fully published.

The information display is available as a widget, which means all options of using widgets on tabs are supported for this new banner widget. Let's first look at the configuration and display the corresponding notification display.

Configuration:

• Add a widget of type Banner
The widget can shown:
  
  • Main tabs, between topbar and breadcrumbs. Usable on main tabs (e.g. study list)
  • Detail tabs (e.g. study ABC-1)
  • Sub-tabs (e.g. study/detail)
  • Fixed positions (e.g. sidebar sequence 4).
• Select widget field type Info
The widget is shown as an alert with configurable Severity. Severity is only shown for INFO widget fields; cleared otherwise.
• Use  Title and details (where other widgets use label and tooltip) .
• Optional define a Filter to restrict the display of the widget. Added shortcuts:
  • credits → credits.[opt/max/min]
  • language → language.externalId
  • year → currently selected year.id (the year selected in the dropdown)
• Add the banner to the relevant Page(s)