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.
Condensed reports should be exportable to excel/csv - EV-373
The condensed report sounds like a compact report, but is in most cases an extensive report with many columns (and rows). In the previous sprint(s) some changes have been made to optimise the visualisation of the condensed report on screen and improve the PDF printed result.
Especially the PDF printed result is tricky, since the number of columns can be so extensive that a lot of manipulation of creating 'virtual pages' is required to get a more or less consistent and readable PDF result.
To cater for the actual requirement of 'getting the data out of evaluation in a usable format', the initial user story has been adjusted to support just that in the form of a Excel export. The condensed report can now be exported as Excel to allow access to all the data in the report, even allowing manipulation of the columns to show, filter, sort, etc. The Excel can then be printed as PDF in case the PDF is still required, using the different Excel options to fit to page, adjust the printing direction, etc.
Production shouldn't crash - EV-369 (hotfix)
After the migration of the production environments to the new stack, the production environment could just 'stop functioning correctly / become unresponsive'. Analysing the logs revealed the root cause, that pointed to a specific configuration in the network traffic where the server could just drop a random database connection. This caused the production 'crash'.
This has been fixed, by adjusting the network configuration to prevent the random database connection drops.
The FTP archive function should be more resilient - EV-370
The FTP archive function copies the Evaluation generated PDF reports to a central location for further processing in the customer infrastructure. The FTP didn't have a retry mechanisme in case of a network hick-up, so any hick-up would cause a failing FTP archive data exchange.
A fix is applied to add a retry mechanism to the FTP archive function in case of an error. The retry mechanism will retry the failed file and then continue with the next report files making the FTP archive function more robust and resilient.
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. Version release dates are provided in the Evaluation release schedule.