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 general page should be fully configurable - CUR-3498
The general page was partial hard-coded. A change is made to enable full configuration of the general page and only show the custom-fields marked as 'show on general'.
In case no fields are marked as 'shown on general', the generic fall-back is to show the externalId, code and name(s). If one field is marked, then these four fields will no longer show, unless they are marked as 'show on general'.
The change of the duration type should not block the subtype selection - CUR-3476
When changing the value type of the duration to Minutes, the subtype selector was set to read-only. Since the subtype is a required field, this prevented to make any changes to the duration field. This issue is fixed and the duration can be switched to a minute display again.
When adding a new application or competence the field configuration should be respected - CUR-3382, CUR-3383
The application and competence configuration provides the option to add additional custom-fields and define their sequence. When using the application or competence template, the fields were shown, but the defined sequence order was not respected. This has been fixed and the fields are shown in the defined order.
Selecting a search result or details from the menu should not require two clicks - CUR-3426
Due to the transition to a new front-end and underlying library sometimes issue pop-up due to the gradual migration where part of the application is still using the 'old' library. One of those is that the search result and other selections to check the details of an object requires two clicks instead of one. This has been fixed in this release.
URL.title should be visible in the browser header - CUR-3509
An issue in line with the above mentioned cause is the display of the URL.title in the Browser header. The issue is for 90% solved, there are still edge-cases by following a specific order in hitting the 'new' and the 'old' library based functions that will change the browser header to the generic naming.
Offering registration start and end date should be saved - CUR-3513
When changing the offering registration start and/or end date, the changes were not save. The cause is found and solved. Both dates are saved again.
In the personal workload report the sum of the monthly availability exceeds the year total - CUR-3438
It was noted that when summing the values of the monthly available hours, the total was not equal to the total year available hours. The cause was found and is solved. The total of monthly and year available will be the same.
The Ad-hoc page configuration should show the ad-hoc related custom-fields - CUR-3568
When configuring an offering page to be used in an ad-hoc context, the selectable fields were the fields of the standard offering. A fix is applied and based on the configuration of the 'Ad-hoc' flag (bottom of the paged configuration) the fields of the standard or ad-hoc offering are shown for selection.
The change report for faculty should show the changes of the current year - CUR-3615
The faculty based change report didn't show the changes from the selected year, but from the previous year. This has been fixed and the changes related to the selected year will be displayed.
As a user I want to copy a module from a previous year - CUR-3470
If you create a new module in a year and there are already future years defined, the module is not automatically copied over to the new years. This is on purpose, since it's not only the module, but also it's relations that may cause issues. Since there are situations where you still want the module in future years, and don't want to create it in completely manually, the COPY module function is extended. Support is added to copy a module from a previous year to the current year.
The copy will perform a check if the module (code) already exists in the new year. If so, the copy will be canceled. Only a module that doesn't exist will be copied over to the new year.
Configuration:
- Add a new field on module named originalYearId, which allows to select a year.
- Value type for originalYearId: Entity
- Subtype for originalYearId: Academic Year
- Then on the existing originalId field (also in module) add a “filter” to show original modules based on the above selected original year. The original modules is only shown when a year is selected using the “condition”.
- Filter on originalId: :academicYearId.id = ':originalYearId'
- Condition on originalId: :originalYearId > 0
- Drag both fields in a new page (or the existing page to create a new module
- Set the create page of custom type “module” to this new page if a new page is created
- When creating a module, use the new fields: first select the year and then the module
- The copy copies the additional/offering etc. from the original year to the new year
As an administrator I want to be helped with configuration questions (AI feature) - CUR-3616
When switching to Experimental the Admin section will get a 'purple' icon at the button that will launch the administrator AI support option. The AI support will the information published at the academy as resource to assist in question
By default some 'short cut' questions are provided some assistance in formulating a question.
To be honest we were pleasantly amazed with the quality of the answers provided.
The AI-function but will be launched during the TimeEdit Summit next week.
Experimental
Since some major changes are made to the user interface due to the migration to a new front-end library a new Administrator option 'Experimental' is introduced. This option will allow administrators to already have a preview on certain pages and functionality coming in the near future.
As an administrator I want to view the new look and feel for pages - CUR-3331
Some pages have already been defined according to the new look and feel. These are only available in the new format when switching to Experimental.
The pages are:
- The Study admin page
- Add a new application
- Review and approve an application
- Add a new personal competence
- Review the personal competence
Not all functionality is already fully supported (most is), but we still wanted to give access to the experimental view.
In case you have feedback, don't hesitate to tell us, we really appreciate it. It will help us enhance prior to releasing to the users.
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.
Hook 'remove from Broker' should remove the selected object - CUR-3597
The hook to remove an object from the Broker, with a sub sequent removal from the study guide didn't work. The hook is solved and the execution of the hook to remove the object from the Broker will actually remove it.
The csv upload of relations should not freeze the system - CUR-3588
When importing a (large) csv of relations in a system with active processes the system could freeze. This was a highly technical issue with synchronous, a-synchronous and thread handling that was caused by the spin off to generate all tasks for the imported relations. This has been solved and the upload of relations can no longer freeze the system.
Add support for multi-value information exchange to Data Manager - CUR-3612
Using a multi-value field in Curriculum will sent both values to Data Manager. The Curriculum default is sending multi-values separated by a comma. For the DM integration the values will be separated by a pipe (|), to meet the DM requirements for exchanging multi-value 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.
In this version no vulnerabilities needed to be addressed.
Refer to the Curriculum manual for configuration guidance.