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.
Module link relations should be shown - SG-571
Modules having a link relation with another object, e.g. requires, excludes should show the relation on both modules. Only the outbound relations were shown. A change is applied to show both outbound and inbound relations, e.g. excludes and excluded by on the two modules.
As an administrator I should be able to define labels in EN - SG-594
An error was introduced that prevented the administrator to manage and save labels in EN. This has been fixed and labels can be managed again in each of the supported languages.
The faculty page should provide an overview of faculties- SG-590
The faculty page was no longer showing the faculties, but an error. This has been fixed and the faculties are shown again.
Visualisation of HTML should be supported in additional fields - SG-574
Additional fields containing HTML data were shown as 'text' and showing the HTML-tags instead of the visual representation. This was a architectural/design decision to prevent security issues introduced by entering HTML / scripting in a field.
A change is applied to support display of HTML in additional fields, by marking the individual fields that should be rendered based on HTML input. This will provide the administrator the option to configure the relevant fields only and not open all additonal fields with the mentioned security risk on any field.
As an administrator I want to get insight in usage details - SG-551
Some months ago we got the request to provide more insight in usage details. We performed some detailed investigation and decided to select an external tool to support the requested insight.
The implementation of the Dashboard will first be based on a full anonymous set of measurements.
More in-depth analytics are supported, but they require a cookie and the corresponding user (student) consent. Based on demand we will investigate further on the usage of cookies for tracking and based on the result extend the analytics options (or not).
OPT-IN
The insight dashboard is an OPT-IN option. To get access to the dashboard for your environment, please file a ticket in Zendesk. The setup of the dashboard will be done and the credentials will be supplied.
Branding configuration should be centralised - SG-589
The branding configuration (logo, highlight colour) is configured in the different applications. This has been centralised in TE-admin, and each of the products will use the same logo and highlight colouring defined.
Usability, look & feel improvement of the administration section - SG-613
All admin pages got a visual refresh and are even more user-friendly and accessible. Part of the change is running past all admin filters and fix the ones that were not working as expected.
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.
No security vulnerabilities have been reported that require mitigation.
For more guidance on configuration and setup of Study Guide, use the relevant Study Guide manual.