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.
As a user I wan to view group descriptions in the structure page - SG-502
Within the study structure the first module group description field that is marked ‘default’ in curriculum (elements, module group description) is shown to users (shown when filled, not shown when empty).
A new feature is added that allows a user to view the other group descriptions by clicking a button in the structure,. This administrator can configure this option to be available. The default setting is 'only show the default marked description.
The button clicked will open a modal that shows all available descriptions. the button is only visible if there are additional descriptions having data and if the parameter is enabled. The administrator can enable/disable the feature by setting the description.showAll setting to true or false / empty.
It should be supported to select custom textfields - SG-528, SG-526
When defining a widget and selecting the custom-fields to be shown, the fields configured as text or number (e.g. credits) where not selectable. This has been fixed, so all defined custom-fields, including text and number are available for selection.
Since the credits are not really selectable but has to be defined, the field to be shown was created but since it is a number field it wasn't shown either. Just as a recap, the convention to show credits is:
- credits -> will show the credits.optimum
- credits.optimum => will show the credits optimal value, which is the default used credtis fields
- credits.minimum -> will show the credits minimum value
- credits.maximum -> will show the credits maximum value
It should be supported to define a reference type filter - SG-525
When defining a filter based on a reference type, the filter was not saved (correctly). The issue was caused by an invalid mapping of the values. The mapping is adjusted and the issue is resolved.
The structure view should only show the configured offerings - SG-524
When using the structure view in table view the modules are shown including the relevant offerings in the context of the study. However, in case the list view was used, the module showed all defined offerings. This has been fixed, so both views will only show the defined offerings in context of the study.
Adding pictures should be supported when using Markdown - SG-521
A picture defined in a Curriculum description when using markdown as the formatting language was not shown in the study guide. When using HTML as formatting language the picture was shown.
A fix is applied that will support the definition and visualisation of pictures in both HTML and Markdown.
A condition on a button should be respected - SG-516
When using the budget widget and adding a widget having a filter the button will always be shown. E.g. only show the button in case the study is a minor or a module has over 15 credits. This has been fixed and now you can not only define the filter on the button, but it will also be respected and only shown if the filter is matched.
Link widgets should support 'configuration'' of the shown information - SG-513
When using a link widget, e.g. to show the studies that are using a specific modules (used by: ...), the visualisation option was defaulted to show the name.
A new option is added to manage the display of the information using the default ${field} convention:
- ${name} - default, will show the name
- (${code) ${name} - will show the code between brackets and the name. E.g., (ABC123) Bachelor of Arts
- ${name} (${type}) - will show the name and the type between brackets. E.g. Bachelor of Arts (BA)
And any other combination using these fields.
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.