The release notes provide information on the features and improvements in the specified version.
The release dates that are related to the version of the release are published in the Evaluation release schedule
Improvements
The issues in release mentioned under the section improvements are considered as new functionality, user experience improvements or bug fixes.
Evaluation members (staff) should be marked as 'employee' - EV-361
In case an Evaluation with users and their associated roles in Curriculum are synced tho Evaluation, some are syncing to Evaluation without the "Employee" role ticked. This will cause the user to have hardly any rights and for instance not be evaluated as a member, e.g. lecturer, of an Evaluation.
The above situation occurred in case the user already exists in Evaluation and has been created without the Employee role. New synced users were created with the Employee role correctly set.
A fix is applied that in case a user is assigned to a role in Curriculum, the user will be synced to Evaluation, created if it doesn't exist yet (based on the setting generate_all or generate_persons is true) and the Employee role will always be set.
The member report should be extended with student attributes - EV-357
The member report provides detailed information with respect to the answer to member (e.g. lecturer) related questions. A small usability change and extension has been made to the report to support easier usage and filtering and extend filter options by using the student attributes defined (e.g. enrolled study programme, former education, gender, ...)
The changes are:
- Split the column that contains the question code and question in two columns question code, question
- Add the defined student attributes as additional columns. The student attributes depend on the configuration and above samples are mentioned like the former education, gender. The report setup is done in such a way that all defined student attributes will be added as separate columns to the report.
The consecutive PDF report should show all data - EV-358
When generating and exporting the consecutive report as PDF, the report can exceed the page boundary and information that exceeds the page boundary is not visible anymore. This has been fixed, so the page boundaries (page width) is respected when generating the PDF and the information will be visible in the PDF report. In case the number of columns exceed the page width a 'second' page will be created. The first page will show the first fitting questions and responses, the second (and optionally more) page will show the pages exceeding the first page.
The graphical display of the question result should show the median - EV-360
The graphical display of a question result shows information on the response in a graphical way. The standard information shown is extend with the median, meaning the graph will show:
- deviation
- average response
- number of responses
- median
The system should support reporting on a massive amount of evaluations - EV-362
A change has been made to the 'loading and processing' of evaluation reporting to support combined reporting on many evaluations. The use case is a user responsible for just under 1000 evaluations in the system and reporting on these evaluations in a single report.
Since this high number was not anticipated, the implemented technique was to retrieve all evaluations and results in one go, which could freeze / block the server for a while and could take a long time causing the user to be detached and the result could not be shown to the user.
A change is made in retrieving the information and generating the reports by retrieving a smaller amount of evaluations and building up the result. Next to this 'pagination approach' some other optimisations have been applied to improve the retrieval speed. An initial test on the test server (limited CPU/memory power) learned the performance went from 10+ minutes to 30 seconds to retrieve and report on just under 1000 evaluations without freezing/blocking the server.
Security
An integral part of our develop and build processes is automatic scanning for known security vulnerabilities. The vulnerabilities will be fixed based on their impact, which means that in some cases an immediate hot-fix will be applied, and in other cases the vulnerability will be fixed in the current or next Sprint (release). The security section provides an overview of the vulnerabilities mitigated.
This release no vulnerabilities has been reported that require mitigation.
For more information on reported vulnerabilities, see the central database of vulnerabilities.
For more guidance on configuration and setup of Evaluation, use the relevant Evaluation manual.