All release notes
share
4 min read

New release Study Guide 2.68

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.


Accessibility analysis and improvements - SG-673, SG-674

An in-depth accessible analysis has been performed focusing on the WCAG-2.2. A short list of non-compliant issues has been defined to be picked up during the next 2 sprints. During this release the next two issues have been addressed:

  • After selecting a search result (e.g. module, program), the focus should stay on the selected result.
  • The keyboard TAB is not on all views navigating correctly to the next item


Navigating back to the overview page should show the search results - SG-679

In case a user has selected for instance the detailed page of bachelor program from the search result, and navigates back to the overview using the 'back to overview' button, no search results were displayed. This has been fixed and navigating back will show the initial search results.

Enhanced AI result using the Broker and a more intelligent LLM pattern - SG-689

The AI search has been adjusted to provide better results. A rather technical story, where the underlying implementation is changed from a relevance search that is attached to the context to using the broker that already standard supports direct lookups, filters and relevance search out of the box. The AI Large Language Model (LLM) has been adjusted and improved to use the new, extended options of the Broker. The LLM is now no longer depending on the context being built up in the search conversation, but can dynamically use the relevance searching of the broker, use the found similar objects to perform automatically a next search on the new 'learned' relevance and then find the best matching result(s). 


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 security vulnerabilities were reported, requiring mitigation.

For more guidance on configuration and setup of Study Guide, use the relevant Study Guide manual.