Improvements

The issues in release mentioned under the section improvements are considered as new functionality, user experience improvements and bug fixes.

‍

An evaluation page (block) with only informative information is skipped - EV-315

In case an evaluation is build up of different pages with informative pages (with only informative questions) in between the returning respondent might skip the informative page. This was the situation in case the respondent save the answers on the page preceding the informative page and quit the evaluation. When the respondent then returns the informative page is skipped, since the standard behaviour of an informative page is that it is successfully answered. This means that the first page with outstanding questions after the informative page was shown and thus skipping the informative page.

The behaviour as released last sprint was not in all cases 100% perfect, this has been fixed in this release and the information page will be shown in case it precedes the page with the outstanding questions.

‍

Import failed due to incorrect handling of date formats - EV-320

The import of evaluation information from an external source could fail due to an unexpected date format or date format handling. The date handling has been altered and made more robust.

‍

Added retry button to resend failed email notifications - EV-322

The notification mailer function has numerous configuration options, especially to handle the limits opposed by the Cloud based (microsoft) mail functionality. Incidentally it is noticed that a notification may not be sent due just hitting the boundary. When noticed, the configuration will be adjusted to slightly decrease the throughput and prevent notifications not being sent.

A function (button) is added that in cases the boundary is hit and incidental mails are marked as 'not sent', they can be resend.

‍

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.

‍