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 Study guide 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 are developed in this sprint but applied to the previous release or directly to production, depending on impact.
WCAG 2.2 compliancy improvements - SG-508
The WCAG compliancy improvements performed in the previous release left the following issue as part of the full AA compliancy requirement.
The following changes are applied:
- The environment tag should have sufficient contrast. Since the tag is not used on production environments this was not solved in the previous release.
- A skip navigation shortcut should be available as defined in the WCAG guidelines.
- The user selected language should be correctly set and accessible. The language is always set to en (lang="en"), even when another language is active. The application responds in the correct language, but a screen reader is not correctly informed about the actual selected / active language.
- Modals should be announced to screen readers.
Reference setting invisible should be respected - SG-511
In case a reference value has been assigned to a field in Curriculum, and the reference value is set to 'invisible' the end result should be the value should not be shown in study guide. This was not the case, but has been solved so the invisible setting for reference values is respected.
The table / list setting on the structure tab should be respected - SG-500
The configuration of the study structure tab offers the option to define the default display behaviour to be set to table or list view and which of the options should be available for the users to select from. The configuration was not correctly used by the page shown to the users, but is fixed and works as expected.
Automated jobs (e.g. nightly import) should respect the timezone - SG-503
The configuration of automated jobs didn't use the correct timezone, resulting in executing a job schedule at 3:00 AM during the middle of the day. This has been fixed and the correct timezone is used that will execute a job scheduled at 3:00 AM at 3:00 AM.
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 vulnerabilities were reported that require mitigation.
For more guidance on configuration and setup of Study Guide, use the relevant Study Guide manual.