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.