Release notes Windows GUI and Web GUI (2021.1.13)

Hello everyone,

In this sprint we've added some extended properties, a small change has been made in the scheduler, and we've fixed some issues for you.

You can read the GUI user manual to read about the WinWeb GUI's features.

We'll keep you updated regularly about the WinWeb GUI's progress.

New extended properties

• Windows & Web: Now it is possible to hide the popup when an async task is started, by setting the global extended property HideAsnycTaskPopup in IAM to 'true' or 'yes'.
• Web: The global extended property NoClaimableApplicationMessageENG allows IAM users to set a customized message to let their users know that all of their applications are already in use. If not set, the default error message will be "All applications for this user are currently in use.".

See Extended properties.

Changes and fixes in the scheduler (Windows)

• In the scheduler, the background of the time cells used to be white by default, they now change according to the settings in the extender. If they were white before and have rainbow colors now, please set the time cell background color in the extender to 'White'.
• An error has been fixed that would occur when you had a scheduler component in a splitter tab, with a detail tab in the other splitter tab.
• The date picker in the scheduler will now update accordingly when scrolling through time.
• When performing the double-click task on a time cell in the scheduler, now only the date and resource_id parameters in the task popup will be filled.

Minor fixes and tasks

• Windows & Web: Grid group headers will now not be drawn when there is no visible column with a group header. Also, invisible columns now no longer prematurely stop a group header.
• Windows: Radio buttons were incorrectly shown as read-only controls when opened in a form with default edit-mode. This has been fixed. Now the radio buttons are editable, as they should be.
• Web: Reactivating an already active document using the process flow caused the interface to be built incorrectly. This problem has been fixed.
• Web: We've fixed a null reference in the method setComponentSizeUP. This error was only shown in the logs, not to a user. It occurred when a user moved a splitter.