Hello everyone,
In this sprint, we solved some issues. Also, Thinkwise Platform support for release 2020.1 ends, and unknown messages from Indicium are now displayed directly to the end-user.
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
Thinkwise Platform support release 2020.1 ends
Support for Thinkwise Platform release 2020.1 is ending. Please upgrade to at least release 2020.2. Attempts to launch a GUI with an unsupported Software Factory or IAM version will result in an error. See also: lifecycle policy
Changed
Report unknown errors from Indicium
(Windows GUI) When an error occurs in Indicium, this error is always passed to the Windows GUI. The Windows GUI then translates this error into a user message. Until this version, if the Windows GUI did not recognize the message ID, this error was not passed to the user.
As of this version, this behavior has changed. If the Windows GUI does not recognize the message ID, the error message from Indicium is now passed and displayed directly (without translation). This informs the user that a specific error has occurred.
Minor fixes and tasks
- (Windows GUI) When exporting to Excel while connected to Indicium (Basic), in some cases the id was displayed instead of the corresponding lookup value. This has been fixed.
- (Windows GUI) In a grid, when adding or editing a row and selecting a value from a lookup dialog, defaults were executed twice. This has been fixed.
- (Windows GUI) In the OAuth Connector process action, the input parameter UsePrompt was not always passed correctly, which resulted in the
prompt=part not being removed. This has been fixed. - (Web GUI) In a grid with the add_row action enabled (to enter data immediately), selecting all rows with the keyboard shortcut Ctrl+A also selected the empty row, and an error occurred. This has been fixed.
- (Web GUI) When sorting a grid in default edit mode by clicking a header, the grid was not editable anymore. This has been fixed.
- (Web GUI) In a grid with multiple pages, the wrong values were filtered: Quick filters were applied to a row on the first page and not to the current row on the current page. As a result, the filtering was on the wrong value. This has been fixed.
- (Web GUI) When adding a row in a grid and immediately selecting a dropdown list, lookup values were not loaded and displayed. This has been fixed.
