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.
Notifications are duplicated when using teams - CUR-3956 (Hotfix)
In case notifications are sent from a process to a team with not generic team email, the email was sent to each of the team members. That was OK, but since the de-duplication was not implemented correctly, the number of notification sent to the each member was equal to the number of members in the team. E.g. 5 members ment that each individual member would get 5 notifications. This has been fixed, and each member will get one notification.
In case multiple offerings for a period, both should be shown in the workflow - CUR-3868 (Hotfix)
The case multiple offerings are defined for the same period, in the workflow activity-overview only the first offering was shown. This has been fixed, and activity-overview will show all offerings both in the structure page and the workflow page.
As a manager I want to have access to the uploaded proof for a user competence - CUR-3924 (Hotfix)
In the last version the upload of documents as proof of a person competence has been added. The competence-report was not yet updated (accidentally missed this), so the report was not accessible in the report. Several changes have been made to the competences report, that amongst others solves the reported issue:
- Add the option to configure the fields to be shown in the competence report by the admin. Using the standard drag and drop, the fields to be shown in the report can be configured.
- Add the option for users to create their own template definition.
- Document fields show the name of the document and are clickable to view the document content
As a user with a new HR role, delete of old WLM tasks must be supported - CUR-3770
When using tasks bound to HR/Contract roles, these tasks are automatically generated for the user. In case the user gets a new role, a change of contract is expected. Which means the old contract is ended and a new is started. In case the role change was made on the current contract, the generated tasks generated for the old role were not deleted. A change is made to cover for this case. The generated tasks are not automatically deleted, but can be deleted manually.
The reason for the manual delete is that automatic deletion feels like 'magic', for a use case not happing very often. By giving control to the responsible person to delete the task, this is less magical.
The process manager filter should respect the validity of roles and persons - CUR-3870
The role filter in the process manager returned not only results for the selected year, but also from previous years. A change is made to only return persons with that role in the selected academic year.
As a user I don't want to see the copy button for each person - CUR-3321
The relation page shows a copy button next to each person or role, to allow copy the person or full role person list. The button is cluttering the page and is not the best user experience. We decided to remove the button, but not the functionality. The copy function is still available, but only appears when hovering (mouse-over) a persons name or the role.
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.
Publishing the staff availability to TE Server should be more verbose - CUR-3943
In case errors occurred when publishing availability to TE server, the error message was not very helpful. It showed the number of failures and the exceptions. In case of a list of errors, the majority is caused due to already existing availabilities that cannot be altered, or a non-existing user.
Several changes have been made to optimise the data exchange and the error reporting:
- The integration chopped the data exchange in blocks of 5 users and their availability. In case one in the block failed, the rest was skipped and all were marked as failed. A change is made that in case of an error of one, the rest will still be processed, limiting the amount of 'errors'.
- The error will show the names of the first 10 failing users, to easily identify the affected users and perform a cross-check in TE server for the user.
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.
Implemented security fixes - CUR-3972, CUR-3983, CUR-3861, CUR-3949, CUR-3922
Based on an audit performed a few weeks ago, the high issues were immediately fix. This sprint the majority of the medium and low issues have been solved.
Refer to the Curriculum manual for configuration guidance.