Release Notes

Available on 17th of March on Production.

Naming update

• Our new Exam product has from today been re-named to Assessment, to better reflect the long term vision of the product. Our previous Exam product will continue to be named Exam.
• The name separation will also make it easier to distinquish between the versions across release notes, support tickets and so on.
• As part of the naming update, we have also enabled the ability to run both versions in parallel, making future migrations significantly smoother.

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.

Customer logo should be shown - SG-564

A change has been applied in previous sprint that has broken the display of the Logo. This has been fixed, and the customer logo is shown again.

Import jobs incorrectly marked as completed - SG-562

In case the import job to synchronize the data between Curriculum and Study guide failed, it sill showed it was successful. This has been fixed and in case the synchronisation fails, the correct message is shown.

The failure was caused by the faculty not having an externalId. For Study Guide the Faculty externalId is required and therefor for an installation having both Curriculum and Study Guide make sure there is a Faculty externalId in Curriculum.

Module-group descriptions should be shown respecting the configuration - SG-569

The study structure shows all module-group descriptions, but should respect the configuration:

• Default show the visible marked module-group description with the lowest sequence
• In case 'Show all' is set, show all the module-group descriptions when clicked the 'show all' button

This was not the case, and has been fixed to adhere to the above behaviour.

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.

No security vulnerabilities have been reported that require mitigation.

‍

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

‍

• Reserve Icon is removed from the product selector when signing in. This icon used to link to the same page as the Viewer icon, to Viewer entrances. Removing it reduces the amount of information users are presented with making the selection.This change is released to production.

• Going forward, the Reserve icon will be removed from the product selector dropdown menu in the top bar. Also, when you select Viewer, it will open in a new browser tab. This prevents situations where a user navigates to Viewer and then cannot return to the previous product.This change will be released gradually as our different products update the top bar in coming releases.

Timezone information is now always visible in reservation details and the account menu, and error pages will automatically reload every 5 minutes to better support unattended public displays.

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

Improvements

• Timezone is now always visible in Reservation details and in the Account menu in the top bar (including guest users) to make it clearer to users what timezone is being used.

• Viewer error pages now auto-reload every 5 minutes.
  • This is especially useful for public displays, which previously could require a manual refresh after an issue.

Bug fixes

• Fixed an issue where editing multiple reservations could show “&object= is mandatory in URL”.
• Fixed an issue where Hide columns in My bookings did not work.
• Fixed an issue where hovering objects in search results could fail to show additional details.
• Fixed an issue where Info reservations could be included in the AutoCancel process (depending on page configuration), causing confirmation prompts for the person who added the info reservation.

Bugs

• Allocate Overview crash after large proposal jobs

  When applying large proposal jobs, a memory leak could cause the Allocate Overview tab to crash. This has now been fixed.

Available on Test for all regions on 10th of March and 17th of March on Production.

• Bulk editing of objects
  • Fields
  • Memberships
  • Relations
  • General info
  • Organization nodes
  • Read more in TE Academy: Bulk edit objects
• Improved user management
  • Bulk activate users in UI
    • Edit > Activate users
• Bug fixes
  • Sorting in user management broke the export
  • Week 53 2026 was missing in Periods
  • All periods was not visible in UI
  • It was not possible to create a new user with a deleted users email
  • Long field names were cut off
  • Selected objects showed negative values
  • Multiple text field was not working, “+” was missing

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.

‍

Groundwork for version support per offering - CUR-2673, CUR-2674, CUR-2672

The standard behaviour of Curriculum is the support of a version per academic year. E.g., a module is published once a year and during that year the module will be bound to that version. Changes could be made, but they would just overwrite the initial state.

This release the technical groundwork is done for support of multiple versions per year. A version will be bound to an offering, since this is the most logical publishable unit. This will support for instance publishing a version for a module for quarter 1 and a version for the same module for quarter 3.

The definition of changes allowed in a version and changes that require a new module are different per institution and are still applicable. This means that a version can also be a 'new' module. In case a module is offered in a program, the new module will substitute the 'old' one and a new program version is created based on the offering period.

The version support can not only be used for the regular programs following the standard academic year and its periods, but is also applicable to the more commercial oriented short programs or modules. In those cases an ad-hoc offering is used to support the distinct versions of a module between offerings.

For the next release the user experience will be adjusted to ease the creation of a version by a user. Then also the various new configuration options and the behaviour in year roll-over will be explained.

Educational tasks should support display per period or per offering - CUR-3441 (Hotfix)

The previous release a change has been made to support display of the Educational task per offering. With the intention to provide a more detailed overview per offering, e.g., location. This extended detail was not expected and desired by all customer. The original grouping per period was in some cases the desired visualisation.

To support both visualisation the task definition is extended with an option to define the used grouping method. The default behaviour will use the grouped per period, as it was prior to the previous release. The added configuration option can be used per task template to use the offering based display option.

Configuration:

• Open the administration -> educational tasks menu
• For the tasks that can be bound to offerings and the grouping is not desired set 'Separate offerings'

Predefined facilities should be visible on the activity-card - CUR-3412 (Hotfix)

The predefined facilities were no long shown (or at least the data) on the activity card. This has been fixed, so both the label and data are shown for the predefined facilities.

Activity series should not shown an error from other offerings - CUR-3420 (Hotfix)

The validation of data uses in activity series could cause an error not directly related to the offering being managed. This was due to an issue in the validation routine, and is fixed so errors are only shown in case there is an error in the activity-serie being managed.

As a user it should be possible to impersonate another user - CUR-3397 (Hotfix)

The user impersonation was broken and caused a 'server error' when selected. This has been fixed, so if you feel the need to impersonate this is possible again.

Various small usability / user interface issues - CUR-2706, CUR-3339, CUR-3256, CUR-3402, CUR-3424, CUR-3433

• When adding a period, after save the added period is directly shown in the period overview
• The effort template information for numeric values is correctly (right) aligned
• Deletion of a new item is possible without showing an error after a successful delete
• Various messages containing 'unexpected JSON' solved, so the information requested is shown again.
• Highlighting the applied changes to descriptions including formatting in history mode is corrected

A generated field using a formula should be saved - CUR-3401

A custom field using a formula to define the value in a offering context was not saved. This was caused by the formula in the UI was properly executed based on the information at hand, but at save the calculation is performed in the back-end and there the root of the offering information was not correctly set.

A change is made to the validation of the formula and the option to identify a field is bound to an offering. By prefixing the value with offering to specifically define the offering should be used, e.g. take(:(offering)periodId, 2) to use the first two characters of the period for the specific offering.

Roll-over per faculty should keep relations bound to other faculties - CUR-3423

In case a roll-over is performed per faculty, all programs and its related data living within that faculty are rolled over. In case a faculty is rolled over with for instance program relations to modules to another faculty those relations and modules are not copied over.

As a user I want to be able to define a offering period that is before the module start date - CUR-3256

In the previous release support for adding methods to a module where the offering period was starting prior to the module start date. This was only added for methods, and has now been added to the appraisal too.

Configuration:

• Open or create a page based on the appraisal page template
• Set the checkbox 'Ignore validation', to support users to proceed when validation fails.

Datetime parameter should be respected - CUR-3368

The configuration supports the definition of the date (time) format to be used when showing date information. It was noted that defined datetime format was not respected in all cases, especially when entering data the datetime was not adjusted to the configured setting. This has been fixed, and the configured datetime is respected in all cases.

Creating a calendar should not cause an error - CUR-3411

When creating a new calendar and not setting the external ID an error was thrown. Since the external ID is required in the database, the data entry page is modified to require the external ID. The user can now only create (save) a new calendar when all the required fields, including the external ID are set.

Data should not be duplicated on save - CUR-3436

It was found that when using a slow network the save button could be clicked multiple times during the save action. This could cause duplication of the data being saved. A change is applied that will disable the save button while the save is in progress. This will prevent the user to click the save multiple times and cause creation of duplicate data.

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.

‍

During this release no changes are made that affect the API(s).

‍

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 security issues needed 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.

‍

Educational tasks should support display per period or per offering - CUR-3441 (Hotfix)

The previous release a change has been made to support display of the Educational task per offering. With the intention to provide a more detailed overview per offering, e.g., location. This extended detail was not expected and desired by all customer. The original grouping per period was in some cases the desired visualisation.

To support both visualisation the task definition is extended with an option to define the used grouping method. The default behaviour will use the grouped per period, as it was prior to the previous release. The added configuration option can be used per task template to use the offering based display option.

Configuration:

• Open the administration -> educational tasks menu
• For the tasks that can be bound to offerings and the grouping is not desired set 'Separate offerings'

Activity series should not shown an error from other offerings - CUR-3420 (Hotfix)

The validation of data uses in activity series could cause an error not directly related to the offering being managed. This was due to an issue in the validation routine, and is fixed so errors are only shown in case there is an error in the activity-serie being managed.

As a user it should be possible to impersonate another user - CUR-3397 (Hotfix)

The user impersonation was broken and caused a 'server error' when selected. This has been fixed, so if you feel the need to impersonate this is possible again.

A generated field using a formula should be saved - CUR-3401

A custom field using a formula to define the value in a offering context was not saved. This was caused by the formula in the UI was properly executed based on the information at hand, but at save the calculation is performed in the back-end and there the root of the offering information was not correctly set.

A change is made to the validation of the formula and the option to identify a field is bound to an offering. By prefixing the value with offering to specifically define the offering should be used, e.g. take(:(offering)periodId, 2) to use the first two characters of the period for the specific offering.

Datetime parameter should be respected - CUR-3368

The configuration supports the definition of the date (time) format to be used when showing date information. It was noted that defined datetime format was not respected in all cases, especially when entering data the datetime was not adjusted to the configured setting. This has been fixed, and the configured datetime is respected in all cases.

Data should not be duplicated on save - CUR-3436

It was found that when using a slow network the save button could be clicked multiple times during the save action. This could cause duplication of the data being saved. A change is applied that will disable the save button while the save is in progress. This will prevent the user to click the save multiple times and cause creation of duplicate data.

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.

‍

During this release no changes are made that affect the API(s).

‍

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 security issues needed mitigation.

‍

Refer to the Workload Management manual for configuration guidance.

Available on Test on Tuesday the 3rd of March and Production the 10th of March 2026

Improvements

Available on Test on Tuesday the 3rd of March and Production the 10th of March 2026

Support for Significantly Larger Jobs

The system now handles job sizes more than 10x larger than before, resulting in improved solution quality across most scenarios.

Improvements in our tests for larger, complex activities jobs shows:

• Successfully scheduled activities moved from around ~80% to ~90%, with majority of remaining activies impossible to schedule due to lack of required resources
• Solution rate for previsously failed activities, improved by ~2-10x compared to before

Faster Validation

Validation and optimization are now separated. This significantly reduces the time required to detect invalid input, instead of waiting for the full auto-scheduling process to complete.

Immediate validation is checking for:

• Missing data that is mandatory on the reservation template
• Objects are not existing anymore
• Mismatch between activity and reservation status

Improved Scheduling Quality

Autopilot now applies penalties to less preferred times of day. As a result, it actively avoids scheduling activities in early mornings and late afternoons/evenings when possible

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.

‍

List and Table settings should be respected in search results - SG-555

The behaviour of the main tab showing the list of results can be configured to either use the list or table view. In case the list was defined as the default behaviour it started as table. This has been fixed, and the defined default behaviour is respected.

Next to that if a user toggles their view, the selected display behaviour is stored for the selected page, instead of global for all search result pages.

‍

How to handle Disclaimer, Privacy and other footer links - SG-557

We regularly get questions / remarks that the footer links navigate to the study guide landing page. This was the default behaviour in case no configuration of the desired URL was defined.

This has been changed, and now the footer links will no longer be shown if the URL configuration is set to - (minus).

The footer links are 'labels' and can be configured with the correct URL by the administrator.

• FOOTER.FOOTER.COOKIES.URL
• FOOTER.FOOTER.COPYRIGHT.URL
• FOOTER.FOOTER.DISCLAIMER.URL
• FOOTER.FOOTER.PRIVACY.URL

Expired groups and modules should not be shown - SG-553

Module groups and modules that were rolled over to the next year and after the roll over were given an end data that lies before the start of the year, were still shown in the study structure.

A fix is applied that validates on end data. If the end date of the module or module group is before the start date of the year the module or module-group will be excluded.

‍

The study guide should be configurable to be excluded from search engines  - SG-558

A configurable option is added to exclude the study guide from being indexed and searchable via search engines.

This will be done by setting a header on all the pages: <meta name="robots" content="noindex,follow" />

Configuration:

• Set the parameter analytics.disabled to true

‍

The Tab filter should support more complex options - SG-549

The Tab filters only supported simple filtering, e.g. type=BA or type in (BA,MA). The support for filters is extended with support for more complex filter options using and operators.

Configuration

The configuration is 'URL style' where the AND is replaced by an &, for example:

• faculty=FDR&type=BA&modeOfStudy=part-time
  Will select all part-time Bachelor studies of the FDR faculty

For direct linking the verb mainTab has been added and can be used in the URL:

• https://<myStudyGuideURL>/studies?mainTab=<myTab>&modeOfStudy=part-time&faculty=ART
  Will open the defined tab and show all part-time studies for the ART faculty

Improve UX compliancy for tooltips - SG-560

To improve readability the exclamation icon has been replaced by the question mark icon.

‍

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.

‍

Fixed Security Issues - SG-556

Resolved vulnerabilities in third-party libraries:

• CVE-2026-22029 (8.0)
• CVE-2026-25639 (7.5)
• CVE-2025-15284 (8.7)
• CVE-2025-13465 (6.9)
• CVE-2025-66400 (6.9)
• CVE-2025-68470 (6.5)
• CVE-2026-24001 (5.3)
• CVE-2026-2391 (3.7)
• CVE-2025-68458 (3.7)
• CVE-2025-68157 (3.7)

‍

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.

‍

My evaluations should be available in the Hub - EV-406

As part of enhancing the student / user experience for TimeEdit customers a generic portal called Hub is developed. The Hub will eventually be the landing page for users of TimeEdit products, making the different functions per stakeholder in a central page. This will include student where access is provided to schedules, exams, exam rooms, etc. But also for invigilators that can define their availability, see there schedule.

The 'My evaluations' has been added as a selectable function (panel) to add to the Hub. It will provide an overview of all outstanding evaluations for the logged in user, e.g. a student, an external examiner.

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.

To help customers prepare for the upcoming SOAP namespace enforcement in Production on March 12, 2026, we are introducing stricter input validation in the test environment.

It will be applied in the test environment today, February 24, and included in the SOAP namespace update taking effect on March 12.

Why this update?

We received feedback that it has been difficult to validate whether SOAP integrations are correctly implemented. Previously, requests with incorrect namespaces or invalid input parameters could execute without clear errors.

What’s changing in test

Effective immediately in the test environment:

• Invalid namespaces will return validation errors.

• Missing or incorrect input parameters will fail explicitly.

• Requests must match the documented SOAP structure.

This makes it easier to verify that your integration is fully compliant before Production enforcement.

What you should do before March 12

• Review your SOAP implementation against our documentation examples.

• Test all SOAP calls in the test environment.

• Ensure requests both succeed and return the expected functional results.

If your integration passes validation in test, it will work correctly once enforcement begins in Production on March 12, 2026.

For questions, please contact support.timeedit.net.

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.

‍

Planned versus Actual

This new development is part of the Workload Management solution. In this case it is added to the Curriculum release notes to actively point out this new development to Curriculum users having both Curriculum and Workload Management.

‍

This release a first step is made to provide a tighter integration between the planned activities in Workload Management and the schedule activities in Core. This is part of enriching the AOP (Academic Operations Platform) vision in closing the gap between planned, scheduled an as a third layer actual information.

This will provide different options to improve insight to improve curricula and steer on changes between planned and scheduled. It also allows to use combination of planned (non-educational) and scheduled/delivered (educational) data for validation of the workload posed on staff. This again can be used for compensation or other actions to prevent over allocation.

The third pilar of actual hours is also implemented. This to support situations where scheduled is not a 100% correct representation of the actual hours. In those cases the 'authorised' user can define the actuals.

The basic idea is to open up and provide access to planned, scheduled and actual information. The functionality will be extended in the future. This first iteration is focussing on the fundamental ground work including the integration with Core, definition of the pillars planned, scheduled and actual, storing the data for the pillars and providing insight on module and person level.

‍

As a System I want to retrieve reservations from Core - CUR-2666

The first story covers the integration with Core and the retrieval of the reservations for the selected module in Curriculum. The new page template reservation-list is added to support the display of the retrieved reservations.

From a 'user' perspective this is not the most useful report, but just for validating the data retrieved the report is ideal. The relevant information used to match the data with the internal Curriculum data (staff member and activity-type) is shown, including the data to filter (select only the last 2 weeks or last month) and the values for calculation (duration) are shown.

As a user I want to see the scheduled activities for a single module - CUR-2665

From a module perspective, the first story is to get both the planned and scheduled activities in one overview.  This overview includes both educational tasks (activities) and non-educational tasks. Based on the selected period the information will be shown.

For the non-educational tasks the hours will be calculated based on the default spread for the selected period. This means in case a module coordinator has 110 hours for a full semester (22 weeks), the hours for a 2 week period are 10 hours.

For the educational tasks (activities) the scheduling based hours are the nett hours, e.g. the duration of the activity. Based on the defined calculation rule for the activity type the calculation of the gross hours will be performed. E.g., an activity of type workgroup with a duration of 120 minutes could be 210 minutes, based on the rule: workgroup hours = 1.5 * duration + 30 minutes preparation.

‍

The calculation can only be done correctly in case the formula is based on the activity hours.

‍

The image below provides an overview of the activities per module, using the worklog page-template. This is the same end result as the report defined under the last story in this section, the report providing a full insight on planned versus scheduled versus actual. In a next iteration the screen will be made configurable to only show the 'desired' information.

‍

As a user I want to see my personal planned and scheduled activities - CUR-2667

This story is similar to the story mentioned above, and uses the same worklog page-template. In this case the information is not shown from the module perspective, but from the users personal overview. This overview includes both educational tasks (activities) and non-educational tasks. Based on the selected period the information will be shown, including the above mentioned calculation method.

As a user I want to define my actual hours, and get them approved by my manager - CUR-3303

Based on the fact that there are cases where the scheduling result is not 100% representing the actual hours for a single user, an additional option is added. This option allows the user to see the personal overview of planned and scheduled, and fill-out an additional column with the actual values.

As said this is not required / desired in all cases, since if scheduling is 100% representing the scheduled is equal to the actual hours. But in cases where the fit is not 100% this allows for defining the actuals.

The definition is steered using the standard processes and workflows, allowing the user to see the planned and scheduled results and define the actuals. The next stakeholder in the process (e.g. HR manager) will validate and approve the changes.

The screenshot below shows the final report of the manager providing an overview of the users, activities and their planned, scheduled and actual result. Hover over the planned or scheduled hours will show the calculation rule used to transform the nett duration of the activity to the actual workload.

An indicator shows if the actual hours have been approved.

As a user I want to have an overview of planned versus actual hours - CUR-2667

As a user I want to get insight in the scheduled versus actual hours for a single module.  The implementation got a little out of hand, so the report providing the insight can be used at different levels, e.g. study, module-group and module, and is using the hour-report page-template.

The example below shows the overview from a study perspective. In this case the information of one module is shown. In case the report is used at module level, the view is the same, and only reduced to the selected module.

‍

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.

‍

Admin pages look & feel improved & usability improved - CUR-3289

The administrator interface has had a major overhaul. We will not bother you with the list of changes applied, but just show the end result in three pictures.

The admin interface will first open in the traditional way, showing all the options on a single page. Once selected the first admin function the screen will change as shown in the next picture.

• The Admin function will be clearly displayed, including a brief explanation of the function
• A left side menu bar will appear, using the icons used on the  main page too.
• At the bottom a new icon appears that supports the unfolding of the side-bar menu.

Once selecting a menu-group  option in the left side-bar, the sub menu items appear. Just select the desired sub menu to quickly navigate to another admin function.

The unfold icon on the left bottom can be used to expand the side-bar and show the menu-group names instead of the icons.

Some visualisation issues and bugs addressed  - CUR-3323, CUR-3326, CUR-3300, CUR-3325, CUR-3313, CUR-3312, CUR-3297, CUR-3304 (Hotfix)

Along with the above change in appearance some issues introduced in the move of the administration pages to the new look and feel and technology stack have been addressed. Since they were annoying and sometimes considered blocking these have already been hotfixed:

• The admin page should not require two clicks to open
• The breadcrumbs should be shown correctly and be accessible
• The person and tab configuration filter should filter (correctly)
• The configuration menu should not freeze the screen
• The period ribbon configuration should show the root type
• The calendar save should save the (changed) data
• Multi-value fields should be displayed correctly

‍

The year switcher should follow the year of the selected task  - CUR-3320 (Hotfix)

In case a task on the dashboard is selected that is not in the currently selected academic year, the year switcher at the top should follow the year of the task. This was technically the case, but the display of the  year switcher didn't change along. This has been fixed and the year switcher will follow the task and display the correct year.

‍

As an administrator I want to define a label with a  placeholder  - CUR-3239

The edit option for labels with a placeholder was broken. When opening such a label, the 'edit' field was shown empty. Only by fully retyping the new label including the placeholder, the text could be changed. This has been fixed, so the active placeholder will be displayed in the 'edit' field and can be changed and saved.

‍

As an administrator I want configure Welsh  as UI language - CUR-3352

A  new language pack has been installed. Welsh is from this release an officially supported user interface language in Curriculum.

‍

Supported module types in a module-groups should be respected - CUR-3359

The group type configuration can be used to define the supported module types for that module group, including their status (new, existing, new and existing, none). A mix up was made that caused the configuration of existing only to show new, and vice-versa. This has been fixed, and the configuration is respected again.

‍

As a user I should NOT be forced to type a code for an ad-hoc period- CUR-3280

When using ad-hoc offerings, the user is requested to type a code and the start and end date. For an ordinary user it makes no sense to come up with a code, that even has to be unique. The system didn't support any option to automate the generation of a unique code, which is a common practice for all other objects.

A change is applied to supports the configuration of a 'rule' to automatically generate a unique (period) code when using ad-hoc periods.

Configuration:

• Create a page using the offerings template to support ad-hoc offerings
• Set the checkbox 'Adhoc'
• Define the 'Adhoc period formula' that will auto-generate the code
• Set the 'Adhoc period read only' checkbox to disable the option to edit the code

‍

Filter option in activity-list should support empty week - CUR-2567

The activity list filter could cause situation where previous filters were remembered even after clearing the filter fields. This has been fixed, and clearing the field will also clear the filter.

‍

The overall person availability hours should match the sum of hours per month - CUR-2507

The personal overview of a person shows an overview for the person, including the allocated hours. The detail part shows the division of the allocated hours over the different months.

It was noted that the values shown in the monthly view didn't add up to the shown total in the general part. The cause has been identified and the mis-match is solved by using 6 decimals instead of 2 in the calculation.

‍

As a user I want multiple offerings to be calculated consistent - CUR-2654

In case an educational task, e.g. module leader, is assigned to a module that has two offering periods and per offering 2 offerings (e.g. in different locations), the educational task was calculation for the two periods.

This has been adjusted and the calculation of the hours will be based on the (4) offerings, to provide a more consistent and understandable calculation.

‍

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.

‍

API documentation extended with the related endpoint - CUR-2519

The API documentation on https://developer.timeedit.com/ is extended with information on the usage of the Related endpoint. The related endpoint provides an overview of all related objects, e.g. all related studies for a module (and not only the parent).

‍

API documentation Broker added - CUR-3204

The API documentation of the Broker is added and a new administrator guide to provide more context of the Broker is added to the academy.

‍

API import of persons should support FTE - CUR-3299

The API person service can be used to define a person assignment and the related FTE, however it seemed the FTE update has been broken. This has been fixed and the FTE can again be set for the default year.

‍

The Curriculum -> Data Manager integration configuration should support more characters - CUR-3310

When the configuration definition for a Curriculum to Data Manager mapping of activities exceeded a specific length, an error was thrown. This was not caused by the limit of the configuration field, but by the administrator audit trail. A fix is applied to solve this issue and allow for extensive configuration definitions.

‍

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.

‍

Results mitigation from the security assessment

The regular security assessment has been executed and this time two minor issues has been reported. Both  are immediately picked up and mitigated in this version.

• Image upload via the HTML editor should be restricted
• The HTML editor should not support images not hosted by Curriculum

‍

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.

‍

Admin pages look & feel improved & usability improved - CUR-3289

The administrator interface has had a major overhaul. We will not bother you with the list of changes applied, but just show the end result in three pictures.

The admin interface will first open in the traditional way, showing all the options on a single page. Once selected the first admin function the screen will change as shown in the next picture.

• The Admin function will be clearly displayed, including a brief explanation of the function
• A left side menu bar will appear, using the icons used on the  main page too.
• At the bottom a new icon appears that supports the unfolding of the side-bar menu.

Once selecting a menu-group  option in the left side-bar, the sub menu items appear. Just select the desired sub menu to quickly navigate to another admin function.

The unfold icon on the left bottom can be used to expand the side-bar and show the menu-group names instead of the icons.

Some visualisation issues and bugs addressed  - CUR-3323, CUR-3326, CUR-3300, CUR-3325, CUR-3313, CUR-3312, CUR-3297, CUR-3304 (Hotfix)

Along with the above change in appearance some issues introduced in the move of the administration pages to the new look and feel and technology stack have been addressed. Since they were annoying and sometimes considered blocking these have already been hotfixed:

• The admin page should not require two clicks to open
• The breadcrumbs should be shown correctly and be accessible
• The person and tab configuration filter should filter (correctly)
• The configuration menu should not freeze the screen
• The period ribbon configuration should show the root type
• The calendar save should save the (changed) data
• Multi-value fields should be displayed correctly

‍

The year switcher should follow the year of the selected task  - CUR-3320 (Hotfix)

In case a task on the dashboard is selected that is not in the currently selected academic year, the year switcher at the top should follow the year of the task. This was technically the case, but the display of the  year switcher didn't change along. This has been fixed and the year switcher will follow the task and display the correct year.

‍

As an administrator I want to define a label with a  placeholder  - CUR-3239

The edit option for labels with a placeholder was broken. When opening such a label, the 'edit' field was shown empty. Only by fully retyping the new label including the placeholder, the text could be changed. This has been fixed, so the active placeholder will be displayed in the 'edit' field and can be changed and saved.

‍

As an administrator I want configure Welsh  as UI language - CUR-3352

A  new language pack has been installed. Welsh is from this release an officially supported user interface language in Curriculum.

‍

The change log should show values instead of numbers (IDs) - CUR-3338

The change log (history) displays all the changes applied to the curriculum data. The information provides details that show the 'old' and 'new' data. It was found that on assessments level the information for selectable fields was not shown, instead the internal ID was shown. This has been fixed.

‍

Supported module types in a module-groups should be respected - CUR-3359

The group type configuration can be used to define the supported module types for that module group, including their status (new, existing, new and existing, none). A mix up was made that caused the configuration of existing only to show new, and vice-versa. This has been fixed, and the configuration is respected again.

‍

As a user I should NOT be forced to type a code for an ad-hoc period- CUR-3280

When using ad-hoc offerings, the user is requested to type a code and the start and end date. For an ordinary user it makes no sense to come up with a code, that even has to be unique. The system didn't support any option to automate the generation of a unique code, which is a common practice for all other objects.

A change is applied to supports the configuration of a 'rule' to automatically generate a unique (period) code when using ad-hoc periods.

Configuration:

• Create a page using the offerings template to support ad-hoc offerings
• Set the checkbox 'Adhoc'
• Define the 'Adhoc period formula' that will auto-generate the code
• Set the 'Adhoc period read only' checkbox to disable the option to edit the code

As a user I want to be able to define a offering period that is before the module start date  - CUR-3256

A request was made to support adding methods to a module in the cased where the assignment of offering periods was starting prior to the module start date. This is a rare case, and could cause down-stream data issues. The process configuration was set-up in such a way that these errors were fixed in a later stage, e.g. by fixing the module start date. And the person assigning the method was not allowed to change the module start date.

To support this situation a additional configuration option has been added to the method-tree template. This option allows to configure the behaviour of the error. Should the error be blocking and prevent from saving the data, or should the error be considered a warning and allow saving the data.

Configuration:

• Open or create a page based on the method-tree page template
• Set the checkbox 'Ignore validation', to support users to proceed when validation fails.

‍

Filter option in activity-list should support empty week - CUR-2567

The activity list filter could cause situation where previous filters were remembered even after clearing the filter fields. This has been fixed, and clearing the field will also clear the filter.

‍

The overall person availability hours should match the sum of hours per month - CUR-2507

The personal overview of a person shows an overview for the person, including the allocated hours. The detail part shows the division of the allocated hours over the different months.

It was noted that the values shown in the monthly view didn't add up to the shown total in the general part. The cause has been identified and the mis-match is solved by using 6 decimals instead of 2 in the calculation.

‍

As a user I want multiple offerings to be calculated consistent - CUR-2654

In case an educational task, e.g. module leader, is assigned to a module that has two offering periods and per offering 2 offerings (e.g. in different locations), the educational task was calculation for the two periods.

This has been adjusted and the calculation of the hours will be based on the (4) offerings, to provide a more consistent and understandable calculation.

‍

Planned versus Actual

This new development is part of the Workload Management solution. In this case it is added to the Curriculum release notes to actively point out this new development to Curriculum users having both Curriculum and Workload Management.

‍

This release a first step is made to provide a tighter integration between the planned activities in Workload Management and the schedule activities in Core. This is part of enriching the AOP (Academic Operations Platform) vision in closing the gap between planned, scheduled an as a third layer actual information.

This will provide different options to improve insight to improve curricula and steer on changes between planned and scheduled. It also allows to use combination of planned (non-educational) and scheduled/delivered (educational) data for validation of the workload posed on staff. This again can be used for compensation or other actions to prevent over allocation.

The third pilar of actual hours is also implemented. This to support situations where scheduled is not a 100% correct representation of the actual hours. In those cases the 'authorised' user can define the actuals.

The basic idea is to open up and provide access to planned, scheduled and actual information. The functionality will be extended in the future. This first iteration is focussing on the fundamental ground work including the integration with Core, definition of the pillars planned, scheduled and actual, storing the data for the pillars and providing insight on module and person level.

‍

As a System I want to retrieve reservations from Core - CUR-2666

The first story covers the integration with Core and the retrieval of the reservations for the selected module in Curriculum. The new page template reservation-list is added to support the display of the retrieved reservations.

From a 'user' perspective this is not the most useful report, but just for validating the data retrieved the report is ideal. The relevant information used to match the data with the internal Curriculum data (staff member and activity-type) is shown, including the data to filter (select only the last 2 weeks or last month) and the values for calculation (duration) are shown.

As a user I want to see the scheduled activities for a single module - CUR-2665

From a module perspective, the first story is to get both the planned and scheduled activities in one overview.  This overview includes both educational tasks (activities) and non-educational tasks. Based on the selected period the information will be shown.

For the non-educational tasks the hours will be calculated based on the default spread for the selected period. This means in case a module coordinator has 110 hours for a full semester (22 weeks), the hours for a 2 week period are 10 hours.

For the educational tasks (activities) the scheduling based hours are the nett hours, e.g. the duration of the activity. Based on the defined calculation rule for the activity type the calculation of the gross hours will be performed. E.g., an activity of type workgroup with a duration of 120 minutes could be 210 minutes, based on the rule: workgroup hours = 1.5 * duration + 30 minutes preparation.

‍

The calculation can only be done correctly in case the formula is based on the activity hours.

‍

The image below provides an overview of the activities per module, using the worklog page-template. This is the same end result as the report defined under the last story in this section, the report providing a full insight on planned versus scheduled versus actual. In a next iteration the screen will be made configurable to only show the 'desired' information.

‍

As a user I want to see my personal planned and scheduled activities - CUR-2667

This story is similar to the story mentioned above, and uses the same worklog page-template. In this case the information is not shown from the module perspective, but from the users personal overview. This overview includes both educational tasks (activities) and non-educational tasks. Based on the selected period the information will be shown, including the above mentioned calculation method.

As a user I want to define my actual hours, and get them approved by my manager - CUR-3303

Based on the fact that there are cases where the scheduling result is not 100% representing the actual hours for a single user, an additional option is added. This option allows the user to see the personal overview of planned and scheduled, and fill-out an additional column with the actual values.

As said this is not required / desired in all cases, since if scheduling is 100% representing the scheduled is equal to the actual hours. But in cases where the fit is not 100% this allows for defining the actuals.

The definition is steered using the standard processes and workflows, allowing the user to see the planned and scheduled results and define the actuals. The next stakeholder in the process (e.g. HR manager) will validate and approve the changes.

The screenshot below shows the final report of the manager providing an overview of the users, activities and their planned, scheduled and actual result. Hover over the planned or scheduled hours will show the calculation rule used to transform the nett duration of the activity to the actual workload.

An indicator shows if the actual hours have been approved.

As a user I want to have an overview of planned versus actual hours - CUR-2667

As a user I want to get insight in the scheduled versus actual hours for a single module.  The implementation got a little out of hand, so the report providing the insight can be used at different levels, e.g. study, module-group and module, and is using the hour-report page-template.

The example below shows the overview from a study perspective. In this case the information of one module is shown. In case the report is used at module level, the view is the same, and only reduced to the selected module.

‍

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.

‍

API documentation extended with the related endpoint - CUR-2519

The API documentation on https://developer.timeedit.com/ is extended with information on the usage of the Related endpoint. The related endpoint provides an overview of all related objects, e.g. all related studies for a module (and not only the parent).

‍

API documentation Broker added - CUR-3204

The API documentation of the Broker is added and a new administrator guide to provide more context of the Broker is added to the academy.

‍

API import of persons should support FTE - CUR-3299

The API person service can be used to define a person assignment and the related FTE, however it seemed the FTE update has been broken. This has been fixed and the FTE can again be set for the default year.

‍

The Curriculum -> Data Manager integration configuration should support more characters - CUR-3310

When the configuration definition for a Curriculum to Data Manager mapping of activities exceeded a specific length, an error was thrown. This was not caused by the limit of the configuration field, but by the administrator audit trail. A fix is applied to solve this issue and allow for extensive configuration definitions.

‍

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.

‍

Results mitigation from the security assessment

The regular security assessment has been executed and this time two minor issues has been reported. Both  are immediately picked up and mitigated in this version.

• Image upload via the HTML editor should be restricted
• The HTML editor should not support images not hosted by Curriculum

‍

‍

‍

Refer to the Curriculum manual for configuration guidance.

This release includes a cleanup of legacy sign-in functionality and minor improvements.

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

Improvement

Bugfix

• Graphical view: Collection of grouped reservations could in some cases appear duplicated. This has been fixed.

We are releasing an update to how SOAP requests to the TimeEdit SOAP API are handled in Production to improve reliability and alignment with documented standards.

This update has been available in the test environment since December and will be enforced in Production starting March 12, 2026.

This update aligns request handling with our documented SOAP structure.

The most important requirement is that requests correctly use the documented XML namespaces (the prefix before the colon in example code, e.g., tns:). This is the main difference compared to some older implementations.

Requests that do not follow the documented structure may still be accepted but may not behave as intended or return expected results. Because strict validation is not performed on our side, it is important to functionally verify integrations in the test environment.

Action if applicable

• Compare your implementation with the SOAP examples in our documentation
• Ensure namespaces and structure match the documented examples
• Verify in the test environment that requests produce the expected functional results, not only that they execute without errors
• If it works correctly in the test environment, it will work in Production after the release

For any questions, please reach out via support.timeedit.net.

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.

‍

Optimize batched import (synchronisation) - SG-546, SG-547, SG-552

A number of changes had been applied to the batch import option that is used for ad-hoc or nightly synchronisation of Curriculum data to the Study guide. The execution and management of the synchronisation has been moved to a dedicated server. This eases the management and reporting on the synchronisations executed. A centralised dashboard provides insight in all executed synchronisations including failures that occurred. Another positive side-effect is that the synchronisation itself is reduced in execution time.

For scheduled synchronisation jobs no effect (except the mentioned benefits) are visible for the administrator. For ad-hoc synchronisations the job will handed over to the general server and the report line stating the synchronisation is started will only appear after the general server has started the job. This means that after starting it can take between 10 - 60 seconds for the report line to appear.

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.

‍

Today, the new Top Bar in Core is released to Production.

Activity Manager has also received a visual update, which has been available in the Test environments since early December. This update brings AM more in line visually with our other products. There is no functional change, just a new cleaner look.

For any questions regarding the Top Bar in Core, please reach out through support.timeedit.net

Note: Users in the ANZ region will see this change a day later due to the fact that Core will reload when it is released.

• Personalised timezones in Allocate and Registration

  Users can now view times in their preferred timezone. This makes it easier to work across locations and reduces confusion when the organisation’s default timezone differs from the user’s.

• Exception (Registration period times)

  In Allocate Overview, registration period times are stored and shown in the organisation’s default timezone.

  In Registration and Manage student, the registration period is shown in the user’s timezone.

The following is released to the Test environment and will reach Production next week. (Some of these have already been released to Production)

Improvements

• When adding multiple objects of the same type by clicking and holding down the modifier (ctrl/cmd), if the selected object in the selection list is a request object, the object will remain selected. Previously, and in other situations, the most recently added object will be selected. This behaviour makes it quicker to select multiple objects related to the same request object

Bug fixes

• Resolved an issue where using the back button in the selection list could cause reservations to be created in a draft despite the calendar no longer being in draft mode
• Resolved an issue where calendars would not adjust in whole weeks when going to today’s date (In Production)
• Resolved an issue where  showing overlapping reservations in the calendar would only display the first reservation (In Production)

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.

‍

Competence management and applications

The first version a new functionality is released that allows management of user competences using processes and workflows for entry, amendment and validation. Reporting is made available to provide an overview on users and their competences, including deadlines nearing or being passed for certified competences with end dates.

Furthermore a function is added for internal system users to apply for a role at an educational object, using their competences as proof. The application is designed and developed generic, based on the requested use case to support the application for a role as lecturer to a module for internal users. The application is supported by a configurable process and workflows to enable the application and the 'hire'.

Remark: Since this is a first release that requires additional internal testing by TimeEdit and the generation of user documentation the releases options should in this release be considered as a first iteration to test and validate. Any feedback is more than welcome.

‍

The stories below have been built to support the functionality:

As an administrator I must be able to manage the set of qualifications (competences) options - CUR-2632

The first step in supporting the above mentioned functions is the ability to define and manage qualifications (competences) by the administrator. Users will use these to select and define the required 'personal' information regarding the selected competence.

Competences can be grouped using a type, allowing improved management for the admin and filter options for users. The required competence fields are configured by the administrator, and may for instance have the following configuration:

• Code: unique identifier of the competence (required)
• Name: name of the competence (required)
• Type: the grouping mechanism to allow for filtering
• License: indicator if the users requires a license (certificate, ...) as proof for the competence
• Start date: in case of a license, the start date can be provided
• End date: in case of a license that expires, the end date should be provided

The above configuration is based on the usage of the Element Competence. This element can be configured and extended with additional fields, e.g. license.

‍

As a user I must be able to manage my own competences - CUR-2635

The user should be able to define and maintain their own competences. This story is designed and defined in such a way the page developed supports the following options:

• User can view own competences, default behaviour
• User can manage (add, edit) own competences, requires authorisation EDIT_COMPETENCE or EDIT_COMPETENCE_WORKFLOW
• Manager (authorised role) can view user competences, requires authorisation VIEW_COMPETENCE
• Manager can manage (add, edit) user competences, requires authorisation EDIT_COMPETENCE or EDIT_COMPETENCE_WORKFLOW

The data to be entered by the user is based on the configuration of the competence and includes the option to add a document as proof for the license.

As a authorised user (manager) I must be able to validate and approve (self-managed) competences - CUR-2637

In case a user manages the own competences, a added or change competence requires validation. In this first iteration the approval is steered from the above shown report. The manager can filter on competences that are awaiting approval and 'approve' or 'reject' the competence.

As a user I should be able to apply for an educational object, e.g. Module - CUR-2639

The application can be configured using the standard configuration options for processes and workflows. The first step in the process is the support for a user to apply for an educational object, e.g. Module.

The application will provide the following information:

• Specify the desired module (standard search box: code, name)
• Select the role (lecturer, examiner, ...)
• Specify the competence(s) that are relevant for the application, from the own list of competences.
• Specify additional information to will clear the why and help the management decision

The user will have an overview of the applications.

As an authorised used (e.g. manager) I should be able to manage a single application - CUR-2640

Based on the process mentioned above, when the staff members has filled in the application it will be sent to the next stakeholder.
The next stakeholder (manager) will get the task to approve the request.

The approval flow provides the information provided by the staff member to assist in the decision making and either approve or disapprove the request.

‍

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.

‍

Using a formula hook to update specification fields should work  - CUR-2703 (Hotfix)

The formula hook can be used for bulk change of information, e.g. codes, based on a formula. Then applying this hook with a formula including the academic year on a specification, this fails. This has been fixed by enabling the usage of the academic year in code generation for specifications.

Configuration should be respected - CUR-3278, CUR-3259, CUR-3264, CUR-2606

In this release some issued with fields not respecting the configured behaviour have been fixed:

• Activity type should not be editable, in case it is defined as read-only
• Duration marked as required, should behave as required (and not optional)
• Reference and Element fields in select options should show both code and name when configured

The end date of reference type should be respected and only show reference values that are still active

‍

Reporting should support 'separate' fields to be selected - CUR-2282

The reporting offers the option to select for instance the modules offered by a program. The module in the report was shown as a combination of the module code and the module name (one column). In case only the module code was needed, in Excel a macro should be defined to separate both values.

To improve the usability, separate values are made available for code, externalId and name.

‍

Correctable should be honoured when configured - CUR-3277 (Hotfix)

A task configured to be correctable should follow to configured calculation rule and allow the user to correct the calculated value. The option to correct the calculated value was not shown. This has been fixed, to enable correcting calculated values based on the configuration setting.

Delete button should be available on activity-grid, list and card (acceptance only) - CUR-3274 (Hotfix)

In the previous release a bug was found where the delete button was only shown in case the activity-grid was empty. As soon there was data, the delete button was no longer available. This has been hotfixed prior to the release to production.

‍

The behaviour of availability-preferences should be improved - CUR-3273

In case a user is requested to enter their availability preferences, the default configuration (everything set to available) or their last saved preferences are shown. In case the users navigates away (e.g. next button in workflow), the data is not saved since no 'changes' were made. And thus the preferences from last year were not saved to this year.

A fix is applied to improve / correct the behaviour:

• If the preference data is never changed in the context of the requested period, it will be marked as 'new' and when preceding in the workflow it will be saved.
• If the preference data is already saved and no changes were made the user can continue the workflow, and no data will be saved.

‍

Team members should not receive tasks when they have been end dated - CUR-3260

Team members no longer member of a team based on a set end-date were still getting tasks assigned in a new year. This has been fixed, and the end-date of the team membership assignment will be respected.

‍

General page behaviour should be more consistent and show correct data - CUR-2596,  CUR-3258, CUR-2603, CUR-3238

Some issues were reported concerning the general page not being consistent and label and corresponding value data not showing correctly. Some fixes are applied to the general page to solve these issues:

• Only show fields that are configured to be shown on the page
• Use the labels of the fields, instead of 'fixed' labels
• Show the label and its value next to each other
• Respect 'visible' condition settings
• Support display of team email address in case roles are assigned a team

Administrator configuration:

Since fields are no longer 'automagically' shown on the general page, but only based on configuration the configuration for fields to be shown should have the checkbox 'Display on general' set.

‍

Fields with formulas should work on form pages - CUR-3253 (Hotfix)

In case a field with a formula on a form page was changed, the data was not save. When changing the same field on the standard 'additional' page the data was saved. The cause was found and has been hotfixed, and fields can be changed when used on additional and form pages.

‍

Long (reference) text should be fully readable in read-only mode - CUR-3255

Long texts, considered to be displayed on a single line, where cut-off when showing in read-only mode. In fact it also happens when not in read-only mode, but then the text was fully accessible moving the cursor.

A fix is applied where single line texts and reference list values exceeding the page size are cut-off, but will have a mouse-over option that will fully expand the text. This is not only applied on read-only values, but also for select boxes with values that exceed the select box width.

‍

As a user I want to define a note - CUR-3247, CUR-2937

In case a user selected the option to create a  note, e.g. add a note for a specific assignment, the screen freezed. Only after refresh the user could continue without having the option to specify the note. This has been fixed, and it is again possible to create notes.

‍

Fix usability issues - CUR-3242, CUR-3231

Two small, but annoying usability issues introduced in the previous release, are fixed:

• Improve contrast in select boxes where the highlight and text color were (almost) the same
• Prevent admin pages to require two clicks to open the page

‍

The schedule weeks on teacher page should respect the configuration - CUR-2523

When creating activities, the schedule weeks are displayed according to the configuration settings in both the activity-grid and list. However, on the page of type 'teacher' the week number shown is always the academic year week number. In case for instance the schedule week is configured, a difference occurred in the display on the activity-grid/list and the teacher assign page.  This has been fixed, and all week numbers shown will follow the generic configured week-display configuration.

‍

Integration

The issues mentioned under the section integration are considered as extension, improvements or bug fixes related to the WLM/Curriculum API, OOAPI and/or CSV import functionality.

‍

API documentation should show the correct response page - CUR-3281

It was noted the API documentation didn't show the correct response page (message format) in all cases. This has been fixed.

‍

API users should be informed when open changes are reapplied to their import - CUR-3261

The standard behaviour using the API so update information in WLM is that the API will not overwrite / override any pending manual applied changes. This behaviour was implemented silently, sometimes raising questions why updates via the API were not processed.

To improve a better understanding of the above use case, the logging is extended with an information message informing the object is 'updated', but not all fields due to pending manual changes. This helps in not being puzzled why it seems the API doesn't work, but understand it works, but the result is different due to the pending change.

‍

API calendar service extended  - CUR-2944

The API calendar service is extended with the start and end date of the academic year. The underlying periods already provided the dates, but the year itself not.

‍

Offering code should be saved using the API - CUR-3271

When using the API is was noted the offering code was not saved. This has been fixed.

‍

Security

An integral part of our development and build process is automatic scanning for known security vulnerabilities. The vulnerabilities will be fixed based on their impact, which means that in some cases an immediate hot-fix will be applied, and in other cases the vulnerability will be fixed in the current or next Sprint (release). The security section provides an overview of the vulnerabilities mitigated. For more information on reported vulnerabilities, see the central database of vulnerabilities.

‍

In this release no security vulnerabilities were reported requiring a fix.

‍

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.

‍

Using a formula hook to update specification fields should work  - CUR-2703 (Hotfix)

The formula hook can be used for bulk change of information, e.g. codes, based on a formula. Then applying this hook with a formula including the academic year on a specification, this fails. This has been fixed by enabling the usage of the academic year in code generation for specifications.

‍

Configuration should be respected - CUR-3278, CUR-3259, CUR-3264, CUR-2606

In this release some issued with fields not respecting the configured behaviour have been fixed:

• Activity type should not be editable, in case it is defined as read-only
• Duration marked as required, should behave as required (and not optional)
• Reference and Element fields in select options should show both code and name when configured

The end date of reference type should be respected and only show reference values that are still active

‍

Reporting should support 'separate' fields to be selected - CUR-2282

The reporting offers the option to select for instance the modules offered by a program. The module in the report was shown as a combination of the module code and the module name (one column). In case only the module code was needed, in Excel a macro should be defined to separate both values.

To improve the usability, separate values are made available for code, externalId and name.

‍

Correctable should be honoured when configured - CUR-3277 (Hotfix)

A task configured to be correctable should follow to configured calculation rule and allow the user to correct the calculated value. The option to correct the calculated value was not shown. This has been fixed, to enable correcting calculated values based on the configuration setting.

‍

The cost calculation should not adjust the original costs - CUR-3268 (Hotfix)

In case an additional offering period was added to a module, the calculation not only changed the 'new costs' (upcoming year costs), but also changed the 'original costs' (previous years costs). The original costs should not be changed by a change for the upcoming year. This has  been fixed.

‍

Delete button should be available on activity-grid, list and card (acceptance only) - CUR-3274 (Hotfix)

In the previous release a bug was found where the delete button was only shown in case the activity-grid was empty. As soon there was data, the delete button was no longer available. This has been hotfixed prior to the release to production.

‍

The behaviour of availability-preferences should be improved - CUR-3273

In case a user is requested to enter their availability preferences, the default configuration (everything set to available) or their last saved preferences are shown. In case the users navigates away (e.g. next button in workflow), the data is not saved since no 'changes' were made. And thus the preferences from last year were not saved to this year.

A fix is applied to improve / correct the behaviour:

• If the preference data is never changed in the context of the requested period, it will be marked as 'new' and when preceding in the workflow it will be saved.
• If the preference data is already saved and no changes were made the user can continue the workflow, and no data will be saved.

‍

The Next button in the workflow should be available when using the HTML editor - CUR-3269 (Hotfix)

The Next button was not always shown in the workflow when using the HTML editor, but showing an error 'invalid' data. This was a 'nice' issue, with a root cause being a combination of configuration settings combined with a longer text. A fix is applied to properly work with the configuration combination causing the issue.

Team members should not receive tasks when they have been end dated - CUR-3260

Team members no longer member of a team based on a set end-date were still getting tasks assigned in a new year. This has been fixed, and the end-date of the team membership assignment will be respected.

‍

General page behaviour should be more consistent and show correct data - CUR-2596,  CUR-3258, CUR-2603, CUR-3238

Some issues were reported concerning the general page not being consistent and label and corresponding value data not showing correctly. Some fixes are applied to the general page to solve these issues:

• Only show fields that are configured to be shown on the page
• Use the labels of the fields, instead of 'fixed' labels
• Show the label and its value next to each other
• Respect 'visible' condition settings
• Support display of team email address in case roles are assigned a team

Administrator configuration:

Since fields are no longer 'automagically' shown on the general page, but only based on configuration the configuration for fields to be shown should have the checkbox 'Display on general' set.

‍

Fields with formulas should work on form pages - CUR-3253 (Hotfix)

In case a field with a formula on a form page was changed, the data was not save. When changing the same field on the standard 'additional' page the data was saved. The cause was found and has been hotfixed, and fields can be changed when used on additional and form pages.

‍

Long (reference) text should be fully readable in read-only mode - CUR-3255

Long texts, considered to be displayed on a single line, where cut-off when showing in read-only mode. In fact it also happens when not in read-only mode, but then the text was fully accessible moving the cursor.

A fix is applied where single line texts and reference list values exceeding the page size are cut-off, but will have a mouse-over option that will fully expand the text. This is not only applied on read-only values, but also for select boxes with values that exceed the select box width.

‍

As a user I want to define a note - CUR-3247, CUR-2937

In case a user selected the option to create a  note, e.g. add a note for a specific assignment, the screen freezed. Only after refresh the user could continue without having the option to specify the note. This has been fixed, and it is again possible to create notes.

‍

Fix usability issues - CUR-3242, CUR-3231

Two small, but annoying usability issues introduced in the previous release, are fixed:

• Improve contrast in select boxes where the highlight and text color were (almost) the same
• Prevent admin pages to require two clicks to open the page

‍

As a user I want to print the advice defined in a report page - CUR-2604

Using the rows template a report page can be configured based on existing pages. When adding the Advice page to the report, it was shown on screen. However, when selecting the print button it was not printed to the generated PDF. This has been fixed, and the advice will not only be shown on screen, but is also printed.

‍

Extend study-modules report with study-module relation fields - CUR-2704

A few releases ago the option has been added to define relationship information between a module and a study. This to support the definition of study context specific information to a module.
In this version support is added to the study-module report to select (and display) the configured study-> module relationship fields.

‍

The activity-groups-report functionality is extended - CUR-2697

The first release of the activity-groups-report, providing an overview of the user groups assigned to activities, is delivered a few releases ago. Based on the backlog and feedback some improvements are added:

• Add support for the configuration of the method type (e.g., teaching, exam) to be shown
• Add additional fields, such as method type, to the report to provide a better and more useful overview
• Add/improve filter options with support for filter on period, faculty and study. For a study the 'owned' modules and their activities will be reported.

‍

The schedule weeks on teacher page should respect the configuration - CUR-2523

When creating activities, the schedule weeks are displayed according to the configuration settings in both the activity-grid and list. However, on the page of type 'teacher' the week number shown is always the academic year week number. In case for instance the schedule week is configured, a difference occurred in the display on the activity-grid/list and the teacher assign page.  This has been fixed, and all week numbers shown will follow the generic configured week-display configuration.

‍

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.

‍

API documentation should show the correct response page - CUR-3281

It was noted the API documentation didn't show the correct response page (message format) in all cases. This has been fixed.

‍

API users should be informed when open changes are reapplied to their import - CUR-3261

The standard behaviour using the API so update information in Curriculum is that the API will not overwrite / override any pending manual applied changes. This behaviour was implemented silently, sometimes raising questions why updates via the API were not processed.

To improve a better understanding of the above use case, the logging is extended with an information message informing the object is 'updated', but not all fields due to pending manual changes. This helps in not being puzzled why it seems the API doesn't work, but understand it works, but the result is different due to the pending change.

‍

API calendar service extended  - CUR-2944

The API calendar service is extended with the start and end date of the academic year. The underlying periods already provided the dates, but the year itself not.

‍

API documentation using the Broker should be available 

The Curriculum Broker provides a dedicated read-only database optimised for querying Curriculum information. The API documentation is published.

‍

Offering code should be saved using the API - CUR-3271

When using the API is was noted the offering code was not saved. This has been fixed.

‍

It should be visible if an activity is offered more than once a week - CUR-3270

In Curriculum it is supported to defined an activity is delivered more than once a week. Integrating to other systems may cause issues in case multiple activities per week is not supported. In those cases errors are raised, rejecting the activity.

In order to get more insight if (accidentally) activities are defined with multiple occurrences in a single week the activity report has been extended with the field 'duplicate weeks'. This will not solve the integration issue, but will help identifying the failing activity and the option to adjust it.

‍

Security

An integral part of our development and build process is automatic scanning for known security vulnerabilities. The vulnerabilities will be fixed based on their impact, which means that in some cases an immediate hot-fix will be applied, and in other cases the vulnerability will be fixed in the current or next Sprint (release). The security section provides an overview of the vulnerabilities mitigated. For more information on reported vulnerabilities, see the central database of vulnerabilities.

‍

In this release no security vulnerabilities were reported requiring a fix.

‍

Refer to the Curriculum manual for configuration guidance.

This release improves timezone transparency in Registration and fixes a filtering regression in Copy from other group.

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

Improvement

• Timezone visibility in Registration
• What changed: Registration now displays the timezone being used in the detailed information view, showing explicitly when times are displayed in the organization's default timezone rather than a user's personal timezone preference.
• Why: Currently, Registration uses the organization's default timezone for all users, regardless of their personal timezone settings. This can cause confusion for users attending teaching in a different timezone than the organization default.
• Benefit: Users can now see which timezone is being applied, reducing confusion about session times.
• What's next: Full support for personalised timezones in Registration and Allocate is under development and will be released later, allowing each user to view times in their preferred timezone.
• Note: This improvement is being released directly to production without the usual test period.

Bugs

• A regression was introduced with Search for students in Student adjustment, in the Copy form group in Allocate students stopped filtering out students not in the source group. This is now fixed.

The following was released to the Test environment today February 5 and is expected to be rolled out to Production on February 12

Improvements

• It is now possible to import reservations with Capacity and Size on them. This works across XML importer and both SOAP and REST API. The Capacity and Size values are currently limited to customers using the new Exam workflow and usually represents a "one off" exam slot.
• It is now possible to also restore cancelled reservations with a Capacity and Size 

Bug fixes

• Resolved an issue where Custom Week names would not be shown correctly in AM. Note: This has also been released to Production.

The new Top Bar has been in Test environments for quite some time, and we have received lots of great feedback! After some tweaking it is now ready to go live in Production environments.

So next week February 12, the new Top Bar in Core will be released to production

The new Top Bar will make it easier to switch between applications and provides a more natural place for:

• Core administration and logout, now under the user icon on the right side of the top bar
• The help center link, shortcuts, and about TimeEdit under the question mark icon, next to the user icon
• We're also moving Views to the top bar as a top navigation item. Our goal is to follow navigation and information hierarchy standards by separating different types of functionality—all to make Core more user-friendly.

The latest version of Data Manager has been available on the Test environment for a while, but as of today, it is available on Production for all customers with Data Manager enabled. 

Most customers already have this enabled, so they will experience no change.

The improved Data Manager includes (among many improvements):

• Better filtering options
• Bulk editing actions
• Edit duration and weeks of Activities
• Add or remove Tracks in an Activity Series

If you do not have access to Data Manager, but would like to try it out for managing Activities, please reach out through support.timeedit.net.

This release is pushed to production at release date.

Improved

• As a step to reduce system load driven by iCal subscriptions, we have changed the order of evaluation of an iCal subscription. We have found that many old subscriptions are still running, requesting reservations from long-gone time windows. We have made two changes:
  • Changed the evaluation order of subscriptions so that if the subscription is "out of date," Viewer returns without doing anything more
  • Changed the HTTP return code from 500 to 410 (Gone), with the intention of having the subscribing server cancel the subscription and not to send the request at all

Bug fix

• When editing a reservation status, Confirmed was selected by default, even though the reservation might be in another state (e.g., Planned). If a user wanted to change the status to Confirmed, this was not possible as the front end would not detect a change, preventing the user from saving the change. This has now been fixed so that the UI correctly reflects the actual status, allowing users to change the status.

• Improved user management
  • Profiles are now supported in export and import
    • DO NOT CHANGE THE PROFILE ID AFTER EXPORT (column A) when importing
  • The Export file contains the profiles with the default profile first. Admin can see which users belong together via the e-mail and user name columns
  • To create a new Profile via the import, keep the user name and email the same, but leave the Profile ID (column A) empty. An ID will be generated.
• Additional app permissions can now be added by TE_ADMIN::admin
  • TE_ACTIVITIES::readReservationTemplates
  • TE_ADMIN::manageObjects
• Bug fixes
  • When setting a Period in Admin the end date reflected incorrectly in Core and Viewer

These items have been on the Test environment for a week, and have now been released to Production

Bug fixes

• Resolved an issue in the Calendar, where removing the Sub Header would sometimes remove the Parent Header instead
• Resolved an issue where some Reservation Fields that should be editable, would sometimes not be editable

The following has been pushed to the Test environment this week and will reach Production next week.

Improvements

• Unscheduling activities in AM will now correctly use the logged in user for permission checks to make sure that the user is allowed to cancel the reservations. This also means that it will be visible on the cancelled reservation who actually cancelled it.

Bug fixes

• Resolved an issue where using a week header would sometimes prevent you from navigating to the last week of the time period
• Resolved an issue where “Allow double reservation for all” in the selection list, would sometimes not appear if the first item in the list was abstract
• Resolved an issue where “Follow date” would sometimes not work if a multi-week calendar is following a single-day calendar

Additional Info

We have also reverted a change to the UI in Core, where the side panels received new styling. This was released to the Test environment by mistake, as it’s part of an ongoing development effort to modernise the appearance of Core. More information regarding this will be communicated in the future.

These items have been on the Test environment for a week, and have now been released to Production

Improvements

• When editing Activities in bulk, it is now possible to choose between different actions for each value: Keep as is, Replace, and for Objects and Object Filters: Add, Replace all or Remove all
• It is now possible to have activities with a duration of more than 24 hours
• It is now possible to nominate sticky columns in the Activity Series and All Activities list, i.e. they will be visible even when scrolling horizontally

Bug fixes

• Resolved an issue where Column headers would sometimes disappear when updating activities while all rows were expanded.

The following has been pushed to the Test environment and will reach Production next week.

Time Constraints on Activities

It is now possible to set Time Constraints directly on Activities (Activity Series for now). Simply select two or more Activity Series in the table and click Edit Activities → Time Constraints.

There are three different constraints to choose from: “Same day of week”, “Same time” and “Same day and time”.

Same day of week means that all selected activities must be scheduled on the same day

Same time means that all selected activities must be scheduled on the same time of day, but could be scheduled on different days.

Same day and time is a combination of the two above, i.e. the included activities will be scheduled at the exact same time.

Note that this applies across multiple weeks as well

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.

‍

Generating a report should be faster and not generate an error - EV-398, EV-401

When generating a report using evaluation tags the generation time could be up to 10 seconds. The 'download box' providing access to the generated report was shown immediately after requesting the report and offering the download. A user clicking the link to the report would get an error.

Based on the above, multiple fixes have been done:

• Enhance the report generation speed by adjusting the query retrieving the data. Resulting in reports taking 10 seconds to under 2 seconds.
• Improve the user experience downloading reports:
• Download box will show information on the progress of the report, instead the link to the report
• Once the report is finished, the status is updated to finished and the link will be accessible
• Once the report is downloaded, the report is removed from the download box and removed from the server.

Uploaded images should not give an error 'image not found' - EV-397

Using the new, enhanced error logging analyser, we identified that in rare cases an error was thrown when an image to be shown in the evaluation could not be found. The evaluation could be proceeded, but the images used in the evaluation (could be a question, or the closing page) were not shown.

After some detailed investigation the cause was found and the code to store and retrieve images has been adjusted to prevent this incidental errors from occurring.

Median calculation should be correct - EV-403

It was reported the median calculation did not match the raw response distributions. This was caused by an error in the algorithm calculating the median. The algorithm has been fixed and the median will have the correct value.

Search filter should 'forget' the search value - EV-402

When using the standard search box to filter the evaluations the matching evaluations were shown. When clearing the filter on screen, the evaluations matching the previous filter were shown. So not all evaluations were shown.

This has been fixed and both the search on a filter value and clearing the filter will act as it should do.

‍

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.

‍

Modules should be shown in the correct order - SG-545

The order modules are shown in the curriculum structure in the study guide could differ from the order as shown in Curriculum. This was caused by the fact Study Guide and Curriculum both implemented their own sorting algorithm, instead of sharing the algorithm.

This has been fixed, and the order will be the same in Study Guide and Curriculum.

‍

Synchronisation should be more robust - SG-544

The importer updating the study guide information directly from Curriculum or the Curriculum Broker stopped the import in case an error occurred. The importer is updated and will now not fail on an error retrieving a single object, but skip the object and continue with the import.

A practical use case is a module or module-group not being published, that is referenced from the published study. The import will not 'find' the object and raise an error. In the previous version this would stop the import, in the new importer the 'missing' object is skipped and the import continues.

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 refreshes the drawer in Allocate Overview to make key information easier to read and act on. The layout is more compact and accessible.

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

Improvements

• Drawer in Allocate Overview
  • Improved accessibility, with clearer hierarchy and better contrast for key information.
  • Removed redundant or low‑value information creating a more compact layout so more content fits on screen without scrolling.
  • Program of study is preselected as dedication type as it is the most commonly selected option

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 user I should be able to logout  - CUR-2661 (Hotfix)

When logging out of Curriculum, the user session was not properly destroyed. This meant the users logged out, got information logout was successful. But when the curriculum URL was entered, the user was still logged in. This prevented users having multiple logins to easily switch between accounts.

‍

The teaching weeks display should respect the configuration - CUR-2679 (Hotfix)

The configuration parameter schedule.display_week with parameter options period / calendar / schedule, is not respected in displaying the schedule weeks. This has been fixed, so the correct week will be shown.

Next to the fix, an UI addition has been applied to support mouse-over showing additional information for the user.

Reports showing the calculated contact hours should show the correct value - CUR-2577 (Hotfix)

When having a page showing both the management of the contact hours and the report of the contact hours it was noted the information was not correct. It seemed the reported information was incorrect.

The issue however had a different cause. The shown information on the edit part was performing the new calculation and showing the result. The information should be saved, but was not properly saved. This caused the mismatch, where based on actually stored data the report was correct. The issue on save has been fixed and for customers affected the recalculation of the values, including saving them has been executed.

‍

Person related tabs should not be named workflow - CUR-3229 (Hotfix)

In the previous release an issue was introduced that caused Person tabs to use the incorrect label, and therefor showing Workflow. This has been fixed, so the proper label is used.

‍

Topbar message should be shown - CUR-2714 (Hotfix)

The topbar message was no longer shown. This has been fixed.
Next to that the title of the news message, used as topbar message, is shown instead of only the text.

The configured display type should be respected - CUR-2716

In case the display type vertical checkboxes was configured for list values (element, references), the display was horizontal. This has been fixed, so both horizontal and vertical checkboxes are showing the selectable options in the expected manner.

‍

Using a select list exceeding 250 items should search in the entire list - CUR-3233

There has been a first solution implemented to support lists exceeding > 250  items. This was not working in all cases and was not offering an intuitive option. A change has been applied to make it more intuitive:

• Inform the user to Search for a value (there will be no full list in a dropdown, search is required)
• Extend the shown search results to not only show the first 5, but show up to 250 items found

Configuration:

Set the value display type to autocomplete for select lists exceeding 250 items.

‍

It should be possible for a user to edit the availability - CUR-3235 (Hotfix)

A user, even having the correct authorisation (EDIT_AVAILABILITY_PREFERENCE or EDIT_AVAILABILITY_PREFERENCE_WORKFLOW), was not allowed to change its availability. This was caused by an incorrect interpretation of the 'read-only' setting. This has been fixed, and the users can again edit their availability.

‍

Ad-hoc offerings should respect the field configuration - CUR-2627

When adding a new ad hoc offering the conditions on the offering fields were respected. When editing an existing ad hoc offering the conditions on the offering fields were not respected. A fix is applied, and both the create and edit will respect the field configuration.

‍

Contact hours should be displayable at the method-tree - CUR-2934

When defining the fields to be shown in the method-tree, the 'contactHours' field were only selectable when  the 'Show fields of' was set to 'Method'. A fix is applied to allow selection of contactHours without setting 'show fields', since both the method-tree and the contactHours are implicitly bound to a method.

‍

Unsaved changes window should only appear once and not 'random' - CUR-2662

In some cases it happened the 'Do you want to save your changes' window popup up multiple times, feeling like a more random action. The cause is found and fixed, so the changes window should only pop-up when expected / needed again.

‍

Search on ( should not throw an error - CUR-3248

The search function generated an error in case the search term contained a (. This has been fixed, and no error will be thrown, but the ( will be used in the search.

‍

FTE should be shown on the person general page - CUR-2619

The general page information for a person is extended with the display of the FTE.

‍

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 support update of module-group type - CUR-2711

When creating or updating module-groups using the module-group endpoint, the type provided was not saved. This as been fixed, and the API will enable setting / updating the module-group type using the 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.

‍

Fixed Security Issues - CUR-3232

Resolved vulnerabilities in third-party libraries:

• CVE-2025-61795(5.3)

‍

As an unauthorised user I should not see the Take-over option - CUR-3249

The validation of the authorisation to execute process management functions was not working correctly on the detail screen of an individual object (module, study, ...). This has been fixed, and the authorisation is respected not only in the overall process manager, but also in the individual object process management.

‍

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.

‍

Using a formula hook to update specification fields should work  - CUR-2703 (Hotfix)

The formula hook can be used for bulk change of information, e.g. codes, based on a formula. Then applying this hook with a formula including the academic year on a specification, this fails. This has been fixed by enabling the usage of the academic year in code generation for specifications.

This might be a rare case, since specifications is a 'non-year' dependant object, where only the additional information is considered year specific.

‍

As a user I should be able to create a new simulation - CUR-3245 (Hotfix)

Creating a new simulation did not work. The cause is found and fixed. Users are able to create new simulations again.

‍

Side-by-side display of descriptions should work properly  - CUR-2628

The side-by-side (sideways) option managing descriptions should show the multiple languages next to each other. It was  noted that based on screen width and/or browser the boxes were not properly positioned. This has been fixed, and the boxes are positioned correctly side-by-side,

‍

As a user I should be able to logout  - CUR-2661 (Hotfix)

When logging out of Curriculum, the user session was not properly destroyed. This meant the users logged out, got information logout was successful. But when the curriculum URL was entered, the user was still logged in. This prevented users having multiple logins to easily switch between accounts.

‍

The teaching weeks display should respect the configuration - CUR-2679 (Hotfix)

The configuration parameter schedule.display_week with parameter options period / calendar / schedule, is not respected in displaying the schedule weeks. This has been fixed, so the correct week will be shown.

Next to the fix, an UI addition has been applied to support mouse-over showing additional information for the user.

Reports showing the calculated contact hours should show the correct value - CUR-2577 (Hotfix)

When having a page showing both the management of the contact hours and the report of the contact hours it was noted the information was not correct. It seemed the reported information was incorrect.

The issue however had a different cause. The shown information on the edit part was performing the new calculation and showing the result. The information should be saved, but was not properly saved. This caused the mismatch, where based on actually stored data the report was correct. The issue on save has been fixed and for customers affected the recalculation of the values, including saving them has been executed.

‍

Person related tabs should not be named workflow - CUR-3229 (Hotfix)

In the previous release an issue was introduced that caused Person tabs to use the incorrect label, and therefor showing Workflow. This has been fixed, so the proper label is used.

‍

Topbar message should be shown - CUR-2714 (Hotfix)

The topbar message was no longer shown. This has been fixed.

Next to that the title of the news message, used as topbar message, is shown instead of only the text.

The configured display type should be respected - CUR-2716

In case the display type vertical checkboxes was configured for list values (element, references), the display was horizontal. This has been fixed, so both horizontal and vertical checkboxes are showing the selectable options in the expected manner.

‍

The configuration of tab sequence should be respected - CUR-2702

In the previous release a new functionality was added where the tab sequence for new or existing objects could be configured. This worked correctly in the structure page for managing module-groups, but didn't work for managing modules. A fix is applied that will use the defined sequence for both module-groups and modules.

‍

A new module-group created on the structure page should be shown immediately - CUR-2945 (Hotfix)

When adding a new module-group on the structure page, the module-group was created and saved, but not shown on the screen. Only after refreshing the page the module-group was shown. This has been fixed, and the created module-group is shown in the structure directly after create.

‍

Using a select list exceeding 250 items should search in the entire list - CUR-3233

There has been a first solution implemented to support lists exceeding > 250  items. This was not working in all cases and was not offering an intuitive option. A change has been applied to make it more intuitive:

• Inform the user to Search for a value (there will be no full list in a dropdown, search is required)
• Extend the shown search results to not only show the first 5, but show up to 250 items found

Configuration:

Set the value display type to autocomplete for select lists exceeding 250 items

‍

It should be possible for a user to edit the availability - CUR-3235 (Hotfix)

A user, even having the correct authorisation (EDIT_AVAILABILITY_PREFERENCE or EDIT_AVAILABILITY_PREFERENCE_WORKFLOW), was not allowed to change its availability. This was caused by an incorrect interpretation of the 'read-only' setting. This has been fixed, and the users can again edit their availability.

‍

Ad-hoc offerings should respect the field configuration - CUR-2627

When adding a new ad hoc offering the conditions on the offering fields were respected. When editing an existing ad hoc offering the conditions on the offering fields were not respected. A fix is applied, and both the create and edit will respect the field configuration.

‍

Contact hours should be displayable at the method-tree - CUR-2934

When defining the fields to be shown in the method-tree, the 'contactHours' field were only selectable when  the 'Show fields of' was set to 'Method'. A fix is applied to allow selection of contactHours without setting 'show fields', since both the method-tree and the contactHours are implicitly bound to a method.

‍

Unsaved changes window should only appear once and not 'random' - CUR-2662

In some cases it happened the 'Do you want to save your changes' window popup up multiple times, feeling like a more random action. The cause is found and fixed, so the changes window should only pop-up when expected / needed again.

‍

It should be possible to show/hide add and delete on the structure page using configuration - CUR-2710

The behaviour of the structure page showing add and delete is bound to the authorisation of a user. But not in all cases a structure page should be offered based on the authorisation. In some cases the requirement is to only show the Add or the Delete button. 

A change has been made to the configuration option of the structure template, supporting the management of the Add and Delete button using configuration. This allows steering the display of the Add and Delete button. The option will overwrite the display of the button in case the user has the rights to see/use them.

Configuration

• Set the setting 'Hide Add' to not show the Add option
• Set the setting 'Hide Delete' to not show the Delete option

‍

Search on ( should not throw an error - CUR-3248

The search function generated an error in case the search term contained a (. This has been fixed, and no error will be thrown, but the ( will be used in the search.

‍

FTE should be shown on the person general page - CUR-2619

The general page information for a person is extended with the display of the FTE.

‍

‍

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 support update of module-group type - CUR-2711

When creating or updating module-groups using the module-group endpoint, the type provided was not saved. This as been fixed, and the API will enable setting / updating the module-group type using the 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.

‍

Fixed Security Issues - CUR-3232

Resolved vulnerabilities in third-party libraries:

• CVE-2025-61795(5.3)

‍

As an unauthorised user I should not see the Take-over option - CUR-3249

The validation of the authorisation to execute process management functions was not working correctly on the detail screen of an individual object (module, study, ...). This has been fixed, and the authorisation is respected not only in the overall process manager, but also in the individual object process management.

‍

Refer to the Curriculum manual for configuration guidance.

This release is pushed to production at release date.

Bugfix

• When grouping reservations in Viewer, the grouping made a difference of when a reservation field had no value or the reservation field was missing all together. This resulted in reservations not being grouped if one of them had a value set and then removed. This has now been fixed.

This release enables searching for students without first selecting a module, and adds more granular control over Auto‑allocate.

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

Improvements

• Search for students in Student adjustment view

  In Student adjustment, it is now possible to search for a student directly, without first selecting a module. This has been a long‑awaited improvement, since students do not always provide their enrolled modules when contacting student services. Previously, staff often had to look this up before they could bring up the student in the Manage student interface.

  Note: It is only possible to search in fields that are marked as Searchable. For example, Email fields are not searchable, so it is not possible to find students by email address.

• Granular control of automatic allocation

  Admins can now choose which parts of Auto‑allocate to run and when:

  • Automatic Allocation: Allocate students to activities where there is only one option (group), ignoring conflicts
  • Automatic De-allocation: Deallocate students who are allocated to groups where they are no longer enrolled in the module
  • Daily: Runs at 06:00 CET. It will take all modules within the filter of the current period into account.
  • Hourly: Runs every hour at 17 minutes past the hour. It will look at students modified within the last hour and update their allocations. The student has to be enrolled or a member of a group related to a module within the filter.
  • Only run Auto‑allocate manually when needed (Run Auto-allocate manually)

  Action required: All Auto‑allocate settings default to Disabled. You need to update Automatic allocation configuration in Admin to enable Auto‑allocate to run automatically again.

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.

‍

There has been a release, but no actual (relevant) fixes or new features were in this release. Some technical findings have been solved that were derived from the logfiles.

Using the new, enhanced implementation of a dashboard that provides error information from all customer systems. This highlights issues that are maybe happening once or twice a day per installation, but over the whole installed base the number will be more significant. More information is available, allowing for enhanced investigation and fixes.

‍

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.

‍

Pagination should support 10 items per page - SG-538

Information shown in the list overview can be shown using pagination. The standard pagination offers different options, including 10 items per page. In case 10 items was selected, this was not respected, and 50 items were shown.

This has been fixed, and the selected number of items per page will be respected.

‍

As an administrator it should be more intuitive to set the active year(s) - SG-542

The configuration of the active academic years could be found in the configuration menu. This has been moved to the academic year menu, where it is clearly visualised which academic years have been defined and which ones are active / visible.

Via the standard Academic year edit option the configuration can be set. As part of the release the configured active years are moved automatically from the configuration setting to the academic year configuration.

‍

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.

‍

Improvements for User management

• Support for sorting logic for users on organisation language
• Language set on organisation, for example swedish, sorts users with names containing å, ä, ö according to Swedish collation, not English
• The user page has been moved to top of side menu
• Export button has changed name from “Template” to “Export”
• Export now contains date for last login of user
• New app permisson for Objects access: TE_ADMIN::manageObjects
• Used for non Admins
• Scope TE_ADMIN::user + app permission TE_ADMIN::manageObjects
• Improved function for adding user objects
• Functionality consistent with object list in Objects
• Select object type to show all columns of object

• Organisation tree now expands to show the searched organisation node

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 should not incorrectly be set to read-only - CUR-2601, CUR-2602 (Hotfix)

Some standard fields defined as editable were shown as read-only. This has been hotfixed.

‍

Dropdown lists should respect the defined sequence and configuration - CUR-2563, CUR-2549 (Hotfix)

Values in a drop-down lists were shown in a 'random' order and sometimes arbitrary add a NaN value. This was the case for both text and numeric / time based values. The drop-down list should use the defined sequence. This has been fixed (restored), so the drop-downs are shown in the correct, defined order.

A second issue was that the drop-down value only showed the code and didn't respect the configured display. This has been fixed, so the drop-down value can now be shown and search for using both code and/or name.

‍

The offering should respect the configuration to display code, name and location - CUR-2579, CUR-2617(Hotfix)

The offering location was not always shown according to the configured pattern that was set to show both the period and its location. The analysis learned this was only the case when using alternative offerings. The location is then defined on the original offering and not on the alternative. The logic tried to show the (not available) location of the alternative offering. A fix is applied to cover this case.

The second use case was that the offering dropdown only showed the code instead of the code and the name in the offering modal. This is also fixed in this release.

‍

Added language support for French  - CUR-2566

Language support for French is added to the user interface. By setting the language configuration to fr, the user interface will be available in French.

‍

User experience configuration enhanced - CUR-2259

The configuration page is migrated to the new look and feel. The information shown to the administrator is improved with labels and additional background information when editing a configuration option.

The appraisal page should support additional options for enabling assessment management  - CUR-2509

A new option is added to steer / limit the access to add and remove buttons on the appraisal page. This allows for a further distinction in if and when buttons should be accessible to manage the assessments.

The added options to the appraisal page added are:

• Hide add: hide the add appraisal button
• Hide delete: hide the delete appraisal button

The configuration will be applied on top of the defined authorisation roles. So in case a user has rights to add an appraisal based on the role, the hide add configuration on the appraisal page can restrict this by hiding the add button.

‍

The process widget on the general page should be enlarged - CUR-2106

The proces widget on the general tab was always cut off at 4.5 processes (but scrollable to show more). A change is applied to improve the user experience by enlarging the box to show more processes. In case the number of processes even exceed the enlarged proces widget, a scroll-option is provided.

‍

As an admin I want to be able delete an activity-serie - CUR-2429

An created activity-serie didn't have an option to be deleted from the system. Only the relation to the method-scheme could be 'removed'. To cover for mistakes or unwanted activity-series the option is introduced for the Administrator to removed an activity-serie.

The implementation is similar with all other objects, e.g. Study, Module. An admin page is added to the activity-serie and the admin page will provide the option to delete the activity-serie.

‍

User experience should be standardised for information labels and buttons - CUR-2450, CUR-2610, CUR-2559

On some pages when using both buttons and labels the distinction between a button and a label was limited. For instance, the delete button was very similar to the label information deleted, confusing users.

This release a user experience improvement is applied to standardise the buttons and labels, improve the difference in visualisation and improve the user understanding and experience.

An example of a form both showing labels and buttons using the new user experience is shown below. The buttons are when possible using the TimeEdit standard icon set. The labels are slightly different, and show relevant information using standard colouring.

The calculated group number should be saved  - CUR-2638

In case a formula is defined to determine the numberOfGroups field, the groups are calculated, shown, but not saved. A fix is applied to not only calculate and show the number of groups, but also save the calculated value.

‍

UI for academic year management is redesigned - CUR-2591

As part of the overall migration to the new look and feel the administrator academic year and calendar pages have been redesigned and transformed to the new look and feel. Changes applied are:

• The Edit button on /admin/calendar and /admin/academic-year now opens an edit drawer
• Clicking a row, code, or View details link in the drawer navigates to the detail page
• A warning is shown when there is not exactly one default Academic Year
• A warning is shown if there is no default Calendar
• Edit drawers now include additional sections with read-only fields and visual separators
• Start and end values in the ribbon period list are displayed as full periods instead of numeric values
• Redesigned expression input and validation modal, with filtering by type (full search)

The academic year will show a warning in case a misconfiguration is noted.

The calendar management is redesigned, using new buttons.

Selecting the Edit button will open the slider to manage the calendar settings.

The evaluation validation is extended with the filtered search for objects. * This evaluation adjustment is currently only available when managing the calendar.

As a user I want insight in tasks assigned to another user - CUR-2539

When using the workflow option to enable assignment of tasks in case multiple users are assigned the distinction between 'not yet assigned' and 'assigned' tasks was not intuitive. The assigned tasks were shown at the bottom of the list and showed a small 'person' icon to show it was assigned. A change is applied to provide a more intuitive user experience by greying out the assigned tasks.

‍

Year rollover should support rollover for multiple faculties in one go - CUR-2595, CUR-2597

When creating a new year and roll-over the data from the previous year an error occurred. It was found the error only occurred in case multiple faculties were selected and rolled-over. The roll-over per faculty offered a work-around. In this release a fix is applied that will enable the roll-over of multiple (or all) faculties again.

‍

The duration should only show the dropdown options - CUR-2609

The new duration field implementation always showed the 'other' option enabling to define a non-standard duration. The default behaviour should be that the user can select from the default defined values and select other from these values in case a non-standard duration is required. The change to support this has been implemented in this release.

ACTION REQUIRED:

The change applied may have impact for existing users that use the 'Other' option. The default behaviour was that the 'Other' option was standard added to the defined list. Based on requests to not provide the option to define another value, a choice is made to make the visibility of the Other option configurable.

To use 'Other' in activities make sure to add a new element with a '-1' external ID in the "Lecture duration" or Assessment duration" element list.

Dropdown fields used on a read-only page should be shown as read-only - CUR-2605

Dropdown fields defined on a form page that was marked as read-only where not shown as read-only. A fix is applied to show the dropdown field value as a read-only value.

‍

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.

‍

Import of module group modules should support usage of module code - CUR-2594

When importing a module group and its module relations, the modules were not always set correctly. Further investigation learned that modules not having an external Id where considered and left out setting the relation. A fix is applied to take all modules into consideration.

‍

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.

‍

Take-over option should only be available for authorised users - CUR-2576 (Hotfix)

In some cases the 'Take over' button was shown to user not having the appropriate role or rights. The cause was found and has been hotfixed.

‍

Admin pages should only be accessible for administrators - CUR-2511

Sometimes a ticket delivers more then initially thought of ...  The use case was that a normal user could get access to an admin page by entering the fully qualified URL. This allows this user to see data, not to manipulate it.

A fix is applied to shield the access to the admin pages completely for standard users, even if they manually enter the fully qualified URL. But there it didn't stop.

The implementation standardised the route to the different admin pages and while changing the route the full admin interface is changed and migrated to the new look and feel. The different admin options are grouped in a more logical way, a search is added to directly find an admin option.

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

A separate section is added to create a distinction with the issues following the standard release pattern. 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.

‍

Fields should not incorrectly be set to read-only - CUR-2601, CUR-2602 (Hotfix)

Some standard fields defined as editable were shown as read-only. This has been hotfixed.

‍

As a user I want to add images to descriptions using the Markdown editor - CUR-2574 (Hotfix)

When including an image to a description using the markdown editor, the image was included as binary. This is a bad practice since the image is then part of the data. A fix is applied to use the same approach as used in the HTML editor. The image is uploaded to the image server and a href is used to define the link to the image.

‍

SECURITY: Take-over option should only be available for authorised users - CUR-2576 (Hotfix)

In some cases the 'Take over' button was shown to user not having the appropriate role or rights. The cause was found and has been hotfixed.

‍

Dropdown lists should respect the defined sequence and configuration - CUR-2563, CUR-2549 (Hotfix)

Values in a drop-down lists were shown in a 'random' order and sometimes arbitrary add a NaN value. This was the case for both text and numeric / time based values. The drop-down list should use the defined sequence. This has been fixed (restored), so the drop-downs are shown in the correct, defined order.

A second issue was that the drop-down value only showed the code and didn't respect the configured display. This has been fixed, so the drop-down value can now be shown and search for using both code and/or name.

‍

The offering should respect the configuration to display code, name and location - CUR-2579, CUR-2617(Hotfix)

The offering location was not always shown according to the configured pattern that was set to show both the period and its location. The analysis learned this was only the case when using alternative offerings. The location is then defined on the original offering and not on the alternative. The logic tried to show the (not available) location of the alternative offering. A fix is applied to cover this case.

The second use case was that the offering dropdown only showed the code instead of the code and the name in the offering modal. This is also fixed in this release.

‍

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.

‍

Added language support for French  - CUR-2566

Language support for French is added to the user interface. By setting the language configuration to fr, the user interface will be available in French.

‍

The appraisal page should support additional options for enabling assessment management  - CUR-2509

A new option is added to steer / limit the access to add and remove buttons on the appraisal page. This allows for a further distinction in if and when buttons should be accessible to manage the assessments.

The added options to the appraisal page added are:

• Hide add: hide the add appraisal button
• Hide delete: hide the delete appraisal button

The configuration will be applied on top of the defined authorisation roles. So in case a user has rights to add an appraisal based on the role, the hide add configuration on the appraisal page can restrict this by hiding the add button.

‍

As an admin I want to configure the tab sequence for new or existing objects - CUR-2259

When adding a group or module to a structure, you get a popup with tabs for Add existing or Create new. To support management of the order shown, two configuration options are added:

• structure.add.module.tabs.default = existing or new
• structure.add.groups.tabs.default = existing or new

While creating the new options the configuration page is migrated to the new look and feel and the information shown to the administrator is improved with labels and additional background information when editing a configuration option.

The process widget on the general page should be enlarged - CUR-2106

The proces widget on the general tab was always cut off at 4.5 processes (but scrollable to show more). A change is applied to improve the user experience by enlarging the box to show more processes. In case the number of processes even exceed the enlarged proces widget, a scroll-option is provided.

‍

Code generated 'on save' should not always increase the  sequence number - CUR-2423

Using the standard (formula) option to automatically create a code, the generate option is frequently used to support generating unique codes. The generate options will create a new sequence number instead the 'base' of the code already exists. When re-triggering the code generation (on save), the generation was too strict and always generated a new sequence since the code already exits. Which is obvious, since that was the code of the object being changed. The regeneration is adjusted to only generate a new sequence when relevant and not in all cases.

‍

The start character using generate in formulas should be respected - CUR-2625

When using the generate option to create a new code, the first created value (sequence) is 0. This could lead to a code like ABC000. A change is applied to not start with 0, but with 1 to start with a code like ABC001.

‍

As an admin I want to be able delete an activity-serie - CUR-2429

An created activity-serie didn't have an option to be deleted from the system. Only the relation to the method-scheme could be 'removed'. To cover for mistakes or unwanted activity-series the option is introduced for the Administrator to removed an activity-serie.

The implementation is similar with all other objects, e.g. Study, Module. An admin page is added to the activity-serie and the admin page will provide the option to delete the activity-serie.

‍

General page should respect the field configuration (for credits) - CUR-2504

Some fields shown on the general page are pre-configured, e.g. the credits. In case the field configuration disabled all credit fields, the credits label was still shown. A fix is applied to only show labels that are defined as visible (available) in the system.

‍

User experience should be standardised concerning information labels and buttons - CUR-2450, CUR-2610, CUR-2559

On some pages when using both buttons and labels the distinction between a button and a label was limited. For instance, the delete button was very similar to the label information deleted, confusing users.

This release a user experience improvement is applied to standardise the buttons and labels, improve the difference in visualisation and improve the user understanding and experience.

An example of a form both showing labels and buttons using the new user experience is shown below. The buttons are when possible using the TimeEdit standard icon set. The labels are slightly different, and show relevant information using standard colouring.

The calculated group number should be saved  - CUR-2638

In case a formula is defined to determine the numberOfGroups field, the groups are calculated, shown, but not saved. A fix is applied to not only calculate and show the number of groups, but also save the calculated value.

‍

The method page should show the original credits  - CUR-2562

A change was applied to the method page in a previous release. This change caused an issue in not showing the original credits. This has been fixed, so the improved method page also shows the original credits.

‍

The management options of a method-field should respect the publication date  - CUR-2508

When a field at method is set to be adjustable until publication, it should respect the publication date of this method. This was not the case, since the publication date of the owning module was used. This has been adjusted and the publication date of the method will be used to validate the adjustability option.

‍

UI for academic year management is redesigned - CUR-2591

As part of the overall migration to the new look and feel the administrator academic year and calendar pages have been redesigned and transformed to the new look and feel. Changes applied are:

• The Edit button on /admin/calendar and /admin/academic-year now opens an edit drawer
• Clicking a row, code, or View details link in the drawer navigates to the detail page
• A warning is shown when there is not exactly one default Academic Year
• A warning is shown if there is no default Calendar
• Edit drawers now include additional sections with read-only fields and visual separators
• Start and end values in the ribbon period list are displayed as full periods instead of numeric values
• Redesigned expression input and validation modal, with filtering by type (full search)

The academic year will show a warning in case a misconfiguration is noted.

The calendar management is redesigned, using new buttons.

Selecting the Edit button will open the slider to manage the calendar settings.

The evaluation validation is extended with the filtered search for objects.
* This evaluation adjustment is currently only available when managing the calendar.

As a user I want insight in tasks assigned to another user - CUR-2539

When using the workflow option to enable assignment of tasks in case multiple users are assigned the distinction between 'not yet assigned' and 'assigned' tasks was not intuitive. The assigned tasks were shown at the bottom of the list and showed a small 'person' icon to show it was assigned. A change is applied to provide a more intuitive user experience by greying out the assigned tasks.

‍

Year rollover should support rollover for multiple faculties in one go - CUR-2595, CUR-2597

When creating a new year and roll-over the data from the previous year an error occurred. It was found the error only occurred in case multiple faculties were selected and rolled-over. The roll-over per faculty offered a work-around. In this release a fix is applied that will enable the roll-over of multiple (or all) faculties again.

‍

The duration should only show the dropdown options - CUR-2609

The new duration field implementation always showed the 'other' option enabling to define a non-standard duration. The default behaviour should be that the user can select from the default defined values and select other from these values in case a non-standard duration is required.

The change to support this has been implemented in this release.

ACTION REQUIRED:

The change applied may have impact for existing users that use the 'Other' option. The default behaviour was that the 'Other' option was standard added to the defined list. Based on requests to not provide the option to define another value, a choice is made to make the visibility of the Other option configurable.

To use 'Other' in activities make sure to add a new element with a '-1' external ID in the "Lecture duration" or Assessment duration" element list.

‍

Dropdown fields used on a read-only page should be shown as read-only - CUR-2605

Dropdown fields defined on a form page that was marked as read-only where not shown as read-only. A fix is applied to show the dropdown field value as a read-only value.

‍

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 should expose the teaching languages - CUR-2554

The OOAPI implementation has been moved to use the read-only Broker. This due to the heavy load generated from specific OOAPI implementation retrieving data from Curriculum. In this migration the field teaching languages was not migrated correctly. This has been fixed to be OOAPI v5 compliant again.

‍

OOAPI should support the programs/{programId}/courses endpoint - CUR-2555

The OOAPI defines a set of endpoints that should or could be made available. A new endpoint is added to the already supported set of endpoints. The new endpoint allows the retrieval of all courses (modules) defined for a specific program.

‍

Import of module group modules should support usage of module code - CUR-2594

When importing a module group and its module relations, the modules were not always set correctly. Further investigation learned that modules not having an external Id where considered and left out setting the relation. A fix is applied to take all modules into consideration.

‍

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.

‍

Permission for page advise should follow the defined authorisation - CUR-2550

To create or change of an advice on study the page permissions 'EDIT_ADVICE' or 'EDIT_ADVICE_WORKFLOW' should be assigned. It was noted that the implementation of the 'EDIT_ADVICE_WORKFLOW' was incorrect and showed an error on save. This has been fixed, so advise an be defined and saved both in workflow and direct on the page.

‍

Admin pages should only be accessible for administrators - CUR-2511

Sometimes a ticket delivers more then initially thought of ...  The use case was that a normal user could get access to an admin page by entering the fully qualified URL. This allows this user to see data, not to manipulate it.

A fix is applied to shield the access to the admin pages completely for standard users, even if they manually enter the fully qualified URL. But there it didn't stop.

The implementation standardised the route to the different admin pages and while changing the route the full admin interface is changed and migrated to the new look and feel. The different admin options are grouped in a more logical way, a search is added to directly find an admin option.

Validated and adjusted permissions - CUR-2582

During the process of validating the the defined permissions two issues were noted, considered as an error and has been changed.

• Report showing the module assigned module-groups was bound to the permission VIEW_STUDIES and is changed to use the permission VIEW_GROUPS
• Report showing the faculty qualifications was bound to the permission VIEW_STUDIES and is changed to use the permission VIEW_QUALIFICATIONS

ACTION REQUIRED:

In case reports are used to show groups or qualifications using the 'incorrect' permission rule, this should be adjusted in the relevant roles.

‍

Refer to the Curriculum manual for configuration guidance.

The Evaluation 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 2026

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

‍

2026

‍

Sprint 120  (4 weeks)

• Version: 6.31
• Acceptance: 19-12-2025‍
• Production: 13-01-2026

‍

Sprint 121

• Version: 6.32
• Acceptance: 16-01-2026‍
• Production: 27-01-2026

‍

Sprint 122

• Version: 6.33
• Acceptance: 30-01-2026‍
• Production: 10-02-2026

‍

Sprint 123 - No release

• Version: -
• Acceptance: -‍
• Production: -

‍

Sprint 124

• Version: 6.34
• Acceptance: 27-02-2026‍
• Production: 10-03-2026

‍

Sprint 125

• Version: -
• Acceptance: -‍
• Production: -

Sprint 125 is skipped, since there were no issues to be solved.

‍

Sprint 126

• Version: 6.35
• Acceptance: 27-03-2026‍
• Production: 07-04-2026

‍

Sprint 127

• Version: 6.36
• Acceptance: 10-04-2026‍
• Production: 21-04-2026

‍

Sprint 128

• Version: 6.37
• Acceptance: 24-04-2026‍
• Production: 05-05-2026

‍

The Study guide 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 2026

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

‍

2026

‍

Sprint 120  (4 weeks)

• Version: 2.57‍
• Acceptance: 19-12-2025‍
• Production: 13-01-2026

‍

Sprint 121

• Version: 2.58‍
• Acceptance: 16-01-2026‍
• Production: 27-01-2026

‍

Sprint 122

• Version: 2.59‍
• Acceptance: 30-01-2026‍
• Production: 10-02-2026

‍

Sprint 123

• Version: 2.60‍
• Acceptance: 13-02-2026‍
• Production: 24-02-2026

‍

Sprint 124

• Version: 2.61‍
• Acceptance: 27-02-2026‍
• Production: 10-03-2026

‍

Sprint 125

• Version: 2.62‍
• Acceptance: 13-03-2026‍
• Production: 24-03-2026

‍

Sprint 126

• Version: 2.63‍
• Acceptance: 27-03-2026‍
• Production: 07-04-2026

‍

Sprint 127

• Version: 2.64‍
• Acceptance: 10-04-2026‍
• Production: 21-04-2026

‍

Sprint 128

• Version: 2.65‍
• Acceptance: 24-04-2026‍
• Production: 05-05-2026

‍

‍

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 2026

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

‍

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

‍

There has been a release, but no actual (relevant) fixes of new features were in this release. The release only covered a fix for a user setup requiring some specific filtering to exclude a user group from  a specific study.

‍

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.

‍‍

As a user I wan to view group descriptions in the structure page - SG-502

Within the study structure the first module group description field that is marked ‘default’ in curriculum (elements, module group description) is shown to users (shown when filled, not shown when empty).

A new feature is added that allows a user to view the other group descriptions by clicking a button in the structure,. This administrator can configure this option to be available. The default setting is 'only show the default marked description.

The button clicked will open a modal that shows all available descriptions. the button is only visible if there are additional descriptions having data and if the parameter is enabled. The administrator can enable/disable the feature by setting the description.showAll setting to true or false / empty.

‍

It should be supported to select custom textfields - SG-528, SG-526

When defining a widget and selecting the custom-fields to be shown, the fields configured as text or number (e.g. credits) where not selectable. This has been fixed, so all defined custom-fields, including text and number are available for selection.

Since the credits are not really selectable but has to be defined, the field to be shown was created but since it is a number field it wasn't shown either. Just as a recap, the convention to show credits is:

• credits -> will show the credits.optimum
• credits.optimum => will show the credits optimal value, which is the default used credtis fields
• credits.minimum -> will show the credits minimum value
• credits.maximum -> will show the credits maximum value

‍

It should be supported to define a reference type filter - SG-525

When defining a filter based on a reference type, the filter was not saved (correctly). The issue was caused by an invalid mapping of the values. The mapping is adjusted and the issue is resolved.

‍

The structure view should only show the configured offerings - SG-524

When using the structure view in table view the modules are shown including the relevant offerings in the context of the study. However, in case the list view was used, the module showed all defined offerings. This has been fixed, so both views will only show the defined offerings in context of the study.

‍

Adding pictures should be supported when using Markdown - SG-521

A picture defined in a Curriculum description when using markdown as the formatting language was not shown in the study guide. When using HTML as formatting language the picture was shown.

A fix is applied that will support the definition and visualisation of pictures in both HTML and Markdown.

‍

A condition on a button should be respected - SG-516

When using the budget widget and adding a widget having a filter the button will always be shown. E.g. only show the button in case the study is a minor or a module has over 15 credits. This has been fixed and now you can not only define the filter on the button, but it will also be respected and only shown if the filter is matched.

‍

Link widgets should support 'configuration'' of the shown information - SG-513

When using a link widget, e.g. to show the studies that are using a specific modules (used by: ...), the visualisation option was defaulted to show the name.

A new option is added to manage the display of the information using the default ${field} convention:

• ${name} - default, will show the name
• (${code) ${name} - will show the code between brackets and the name. E.g., (ABC123) Bachelor of Arts
• ${name} (${type}) - will show the name and the type between brackets. E.g. Bachelor of Arts (BA)

And any other combination using these fields.

‍

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 makes class capacity handling more predictable by treating missing or zero max class size as “no seats” everywhere, adds program of study information to the Manage student view, and improves how conflicts are shown in Registration and Manage student.

This release is pushed to test on December 17th and is planned for production on December 18nd. The test period is shorter than normal due to the Christmas holidays.

Improvements

• Consistent interpretation of Max class size

• What changed: When a groups capacity is set to 0 or not set at all, it is now consistently treated as 0 in both the UI and the allocation algorithms. Previously, some parts of the UI presented missing data or 0 as infinite capacity (∞). 0 (or missing) now always means no students will be allocated to that group, which removes ambiguity.

• Program of study in Manage student

• What changed: The student’s Program of study is now shown alongside existing student information in the Manage student view.
• Benefit: Easier to understand the student’s context when adjusting allocations.
• Clearer conflict information in Registration and Manage student

• What changed: In the expanded information view, groups with reservations at different times during the week show those times individually. Conflict information is only shown on the specific times where there is an actual conflict.
• Benefit: A clearer picture of when a conflict occurs, reducing noise and helping staff and students make better choices.

Improvements

• Objects
  • Improved column resizing and auto-adjustment in table views
  • Object search now includes subtypes
• Org node tree
  • Enhanced view of objects connected to organisation nodes
    • Field data per object type available
    • Direct link to filtered view in Objects
• User management
  • Login and modification history available (hover to view details)
  • New filter component
    • Filters can now be customised and saved
  • Added filtering by Standard Organisation and Organisation Node
  • New available columns
    • Last modified
    • Created

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.