release notes

Release notes Universal GUI (2021.3.13)

Related products: Universal GUI
Release notes Universal GUI (2021.3.13)

November 26, 2021:

  • Full release from version 2021.3.13 BETA.
  • Hotfixes:
    • We fixed two bugs that caused the Universal GUI to crash when the session had expired or the user had logged out.
    • We fixed errors that occurred when a task deleted the current record.

 

Hello everyone,

In this sprint, we added support for showing messages thrown from the Badge logic and we now support the lookup control type 'Combo (sorted)'. We also improved some features, like the form's HTML editor, and fixed some issues.

As always, we have made a demo for you: try it here. Before trying it out, press 'Clear Cache' on the login screen. You can read the GUI user manual to get familiar with the Universal GUI.

We will keep you updated regularly about Universal's progress.

 

Contents of this release

 

Universal GUI version 2021.3.13

Like with every blog, we have released a version to test the Universal GUI out for yourself. Do not forget the documentation and be sure to keep the following in mind:

  • A modern browser is required to access the Universal GUI, e.g., a recent version of Chrome, Firefox, Edge, or Safari mobile. Using the Universal GUI with IE is not supported.
  • The Universal GUI must be deployed on the same server as Indicium or it should be an allowed origin in the appsettings.json.
  • The Universal GUI only works with version 2019.2 and up of the Thinkwise Platform.
  • Make sure you run all hotfixes on the IAM and SF that you plan to use for the Universal GUI.
  • Make sure you are using the latest version of Indicium Universal.

Download the Universal GUI version 2021.3.13 here

 

Changed

 

Tasks marked as "double click" hidden in the toolbar

Tasks marked as ‘double click’ are hidden in the toolbar now. This setting is available in the menu Processes > Tasks > tab Table tasks > tab Form.

 

Process flow continues in the last document when the follow-up action says so

We made process flows a little smarter when running outside the context of a document, e.g., when running a task from the menu. When the follow-up action points to a subject, it tries to find it in the last involved open document of the flow.

This is helpful when running a task that should not be accessible from the document's toolbar. The task can be executed globally filled by process variables, and afterward, the flow can continue in the active document.

We strongly advise you to thoroughly test your process flows if they contain one of the following actions:

  • add / copy / edit / delete
  • task / report execution
  • open / activate / close document
  • zoom detail.

 

New

 

Messages from the Badge logic

Like the other GUIs, the Universal GUI now shows messages thrown from the Badge logic.

Notice that the badge may be displayed multiple times and run again after a certain interval. As a Software Factory developer, you are responsible for preventing messages from popping up multiple times.

 

Support for 'Combo (sorted)'

Universal GUI now supports the lookup control type 'Combo (sorted)', so you can configure a combo in another way than just alphabetically.

This setting is available in menu User interface > Subjects > tab Default/Variants > tab Settings > tab General > field Def. control.

Note that:

  • Some more complicated combinations of sort fields, like a domain element with values followed by another sort on a lookup field, are not yet available.
  • This lookup control type is not yet available for lookup controls in the filter form.

 

HTML edit / non-edit popup

We have improved the form's HTML editor. It is now possible to show and edit the formatted document in a larger popup.

You can click on the new icon to open the popup for editing HTML in edit mode. The formatting toolbar (to make text, for example, bold) has also been moved to the popup. In the form editor, you can still edit the text in the currently applied format. In both the popup and form editor, you can use the shortkeys for formatting.

In non-edit mode, you can use the popup to inspect the contents in a larger display.

This was the previous HTML editor, with the formatting toolbar:

Previous HTML editor with formatting toolbar

Now, the formatting toolbar has been removed, and a popup icon has been added:

New editor without the formatting toolbar, but with a popup icon

The new popup in edit mode now contains the formatting toolbar:

The new popup editor in edit mode, with formatting toolbar

This is the new popup in non-edit mode (read-only):

The new popup editor in non-edit mode (read-only, no formatting toolbar)

This is only the first release of this feature. For future releases, we have planned:

  • To replace the Close button with Save/Cancel buttons. Now, after opening the popup while editing, changes made to the HTML text are always synchronized. Later on, the Cancel button should provide the option to ignore them.
  • To improve the styling of the formatting toolbar. We wish to apply equal padding at the top and bottom and add a border between the buttons and content.
  • To solve a known issue, which has been in the Universal GUI for a couple of releases. At the moment, scrolling in the HTML control of the form in edit mode is not possible with the scroll wheel. Manually grabbing the scrollbar still works. We will plan this as a separate issue.

 

Minor fixes and tasks

  • Messages from a process flow now show parameter values.
  • In some cases, a type error 'Cannot read properties of undefined (reading 'applications')' occurred when the login token had expired. This has been fixed.
  • When adding a record in a task was followed by a Go to row process action, the new record was not selected. This has been fixed.
  • The controls for the Cortex and regular barcode scanners used to lose focus when the scan button was still loading. This has been fixed. The input now retains the focus.
  • We fixed two bugs that caused the Universal GUI to crash when the session had expired or the user had logged out. These bugs made the GUI unusable with a `reading properties of undefined` error that kept recurring. We are working on a final fix to prevent these types of errors when logging out. That final fix will be available next release. For now, the Universal GUI will no longer become unusable when such an error occurs.
  • We fixed errors that occurred when a task deleted the current record.

 

What we will be working on next sprint

The next sprint we will be working on:

  • Record not found on lookup open - When a look-up popup is opened and the selected record is not in the current filtered set, it should try to fetch the record by removing all the pre-filters.
  • Lookup from grid Ctrl+Alt+P shortcut - Open the look-up for the currently selected field in the grid with the Ctrl+Alt+P shortcut.
  • Form list design
  • Automated testing
  • General maintenance.

I try to download this new version but

“GUI Downloaden → Universal” the downloaded ZIP is empty
“Installation package downloaden” (only Universal option on) the zip contains Indicium but no Universal GUI

 


@Jaap van Beusekom Can you try again? It should work now


Yes, thanks


With the new Universal GUI release we have an unexpected surprice, HTML fields got resized and a Lookup icon appeared next to them. This should have been disabled by default as it never existed before (to be backwards compatible). I will add a TCP ticket regarding this.

 


The domain of the column in the SF offers a setting for this. The Universal GUI doesn't listen to this setting yet. We planned to start using it in the upcoming sprint.


The domain of the column in the SF offers a setting for this. The Universal GUI doesn't listen to this setting yet. We planned to start using it in the upcoming sprint.

@Erik Brink So can we expect this in the 2021.3.15 release? We use the HTML field for custom screen stuff (specifically showing a LinkedIn icon for a LinkedIn URL and a Teams icon to initiate a chat with a user), so we need this functionality to not break our existing HTML-based solutions. 


The domain of the column in the SF offers a setting for this. The Universal GUI doesn't listen to this setting yet. We planned to start using it in the upcoming sprint.

@Erik Brink So can we expect this in the 2021.3.15 release? We use the HTML field for custom screen stuff (specifically showing a LinkedIn icon for a LinkedIn URL and a Teams icon to initiate a chat with a user), so we need this functionality to not break our existing HTML-based solutions. 

Yes, we planned it for current sprint.


Tasks marked as "double click" hidden in the toolbar

Tasks marked as ‘double click’ are hidden in the toolbar now. This setting is available in the menu Processes > Tasks > tab Table tasks > tab Form.

@Erik Brink I suppose you guys changed this based on our TCP 2056S. Could you explain why the solution chosen here is different than requested?

We would have liked it to work as follows:

  1. IF both Show and Grid double click checkboxes are true: show Task in Action bar ánd have it work with Grid double click
  2. IF Show is false and Grid double click is true: don't show Task in Action bar, but have it work with Grid double click

Currently implemented logic is less flexible: both Show and Grid double click must be true for Grid double click to work, but the Task is never shown in the Action bar.

 

Messages from the Badge logic

Like the other GUIs, the Universal GUI now shows messages thrown from the Badge logic.

Notice that the badge may be displayed multiple times and run again after a certain interval. As a Software Factory developer, you are responsible for preventing messages from popping up multiple times.

We appreciate having this functionality available in the Universal GUI now! When testing our use case for this logic, we noticed that the Universal GUI behaves differently than the Windows GUI on the following: all Badge logic in the Windows GUI is triggered based on the set frequency, while in the Universal GUI the Badge logic is only triggered if either the Document on which the Badge is active is open, or if the list bar group is expanded for which a Badge is active on a list bar item.

The Universal GUI logic hampers our use case, since we intend to trigger a message whenever someone gets assigned a new Task, regardless of whether or not the user has the Tasks document opened.

Could you explain why this difference in behavior exists?


@Arie V 

1. The show task checkbox is currently used to decrease the number of tasks loaded by the GUI, so the Universal GUI doesn't know about the existence of the tasks now. @Anne Buit should we update our `i_ui`-views with this?

2. In my opinion we shouldn't use the badge stored procedure to push messages to the user, but there is no other way now. The Universal GUI indeed executes the badge SP much "smarter” and I think we shouldn't change this. Maybe for now think of a start object, which the users will keep open to stay informed?

P.s. maybe we should get the discussion about this out of the release notes topic?


@Arie V

1. The show task checkbox is currently used to decrease the number of tasks loaded by the GUI, so the Universal GUI doesn't know about the existence of the tasks now. @Anne Buit should we update our `i_ui`-views with this?

2. In my opinion we shouldn't use the badge stored procedure to push messages to the user, but there is no other way now. The Universal GUI indeed executes the badge SP much "smarter” and I think we shouldn't change this. Maybe for now think of a start object, which the users will keep open to stay informed?

P.s. maybe we should get the discussion about this out of the release notes topic?

@Erik Brink Alright, I have raised TCPs for both issues.

Regarding the use of Badge logic for messages: As long as there is no other supported way to proactively send in-app Notifications or Push Notifications we want to use the Badge logic for sending messages to users for certain changes (as per earlier suggestion from @Anne Buit :rolling_eyes: ). We thought of the Start Object solution ourselves too: it helps but it is not airtight since users can close that document after login.