Skip to main content
Release Notes

Release notes Windows GUI and Web GUI (2022.1.13)

Related products:Windows GUI
Release notes Windows GUI and Web GUI (2022.1.13)
Sjors Niesten
Apprentice
Forum|alt.badge.img+1

Hello everyone,

In this sprint, we replaced the integrated browser component used for previewing web content, Indicium (Basic) now supports the Concurrent access (Claims) feature, and we solved an issue.

You can read more about the Windows and Web GUI's features, in the GUI user manual. We will keep you updated regularly about the Windows and Web GUI's progress.

 

Breaking

New web browser component for previewing

(Windows GUI) The integrated browser component used for previewing web content has been replaced. Instead of the full CefSharp browser (270 MB in size), the Windows GUI now ships with the Microsoft Edge Webview2 installer that installs the browser component if not already available. The installation does not require administrator privileges.

In addition to the smaller size of the Windows GUI, this also ensures the security of the browser component, as Windows takes care of keeping the browser component up-to-date.

Installing Microsoft Edge Webview2 Runtime

New

Indicium (Basic) supports the Concurrent access (Claims) feature

(Windows GUI) To use the Concurrent access (Claims) feature via Indicium (Basic), you need to install the latest Software Factory and IAM hotfixes (Platform improvements).

Concurrent access delimits the number of concurrent users that can log into an application simultaneously.

For more information on the Concurrent access settings, please refer to the corresponding IAM documentation.

Support for additional OAuth2 prompt options

The Windows GUI now supports the new OAuth2 prompt options. These options were originally added in IAM hotfix 20220216.

The available OAuth2 prompt options have been made editable and have been expanded with the prompt options loginselect account, and none.

Minor fixes and tasks

  • (Windows GUI and Web GUI) When a primary key column had data type VARBINARY, an incorrect row was selected after data refresh. This has been fixed.
Did this topic help you find an answer to your question?
This topic has been closed for comments

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings