Hello everyone,

In this release, we added support for keyboard shortcuts regarding import/export, updated the tab navigation within the grid in edit-mode, and changed how we manage users leaving an editable subject with unsaved changes. We have also addressed several issues and tasks.

Demo

As always, we have made a demo for you: try it here. Before trying it out, press 'Clear Cache' on the login screen.

Read the Universal GUI user interface guide to get familiar with the GUI.

Universal GUI version 2024.2.13

For more information about setting up the Universal GUI, see the Universal GUI setup guide.

Note:

• Use a modern browser to access the Universal GUI, e.g., a recent version of Chrome, Firefox, Edge, or Safari mobile.
• Deploy the Universal GUI on the same server as Indicium or an allowed origin in appsettings.json.
• The Universal GUI only works with version 2022.1 and up of the Thinkwise Platform.
• Run all hotfixes on IAM and the Software Factory that you plan to use for the Universal GUI.
• Use the latest version of Indicium.

Download the Universal GUI version 2024.2.13 here

Contents

New and changed

Keyboard shortcuts for import and export

new

We have added support for keyboard shortcuts when importing or exporting data:

• Import: Ctrl + Shift + I
• Export: Ctrl + Shift + E

Grid tab navigation in grid using modern key binding

change

We have updated the tab navigation within the grid in edit-mode. The keyboard navigation is as follows:

• Classic key bindings: Tab navigates through all fields, Enter navigates through editable fields only.
• Modern key bindings: Tab navigates through editable fields only, Enter is not used in this key binding.

Confirmation dialog for leaving an editable subject

change

The Universal GUI previously only blocked a user from leaving an editable subject with unsaved changes. Now, we have added a confirmation dialog. It gives a user the option to either continue closing (losing the open changes) or to go back to the changes.

Fixes and tasks

Fixes for issues on startup:

• We have fixed an issue where the Universal GUI would not load after logging in, if the active menu was not set or not available due to rights. This has been solved. Now, an alternative menu is selected or a message is displayed to the user.
• Logging into the same model on different versions of Universal previously caused an infinite loader, especially when downgrading from a newer to an older version. Now, you will be automatically logged out and an error message will be displayed.
• We resolved an issue where deep links sometimes failed to work correctly for non-cached applications, especially after you cleared the cache. This could mean that you would not end up at the intended part of the application or that the correct filters were not applied.

Fixes for filtering:

• Some time ago, while implementing group header filtering for lookup-type columns, we decided to hide process flow filters in filter forms due to technical reasons. However, you informed us that you wanted to see the filtered values again so users would know they exist. We have now restored this functionality. Filtered values are again shown in filter forms, and the filter indicator is displayed in the grid column headers.

  In some cases, it may still not show up:

  • When the filtered value does not exist in the dataset.
  • When the filter key has multiple representations and multiple are available to the user for filtering, such as an item per selected language.

• When using the filter in grids to modify an existing filter with the 'In' or 'Not in' operator, you might not have been able to select any values. This has now been fixed.

• A few releases ago, we introduced column filtering from grid headers. In the case of a lookup without a display column, the list with items to filter on was not filled successfully. Now, the list is filled with all available items in the subject's data set.

Fixes for lookups:

• When you add a row in a lookup pop-up, you would get an erroneous error message "No context or record", despite the row being successfully saved. We fixed this, as this was misleading and gave the impression of an error where there was none.
• When adding a new row and opening a lookup pop-up on that row, any linked details in the lookup pop-up would not be loaded. This has been resolved.
• When editing a lookup with two options having the same translation, the options would be further duplicated under some circumstances. This has been fixed.

Fixes in form, grid and cardlist:

• In a default editable grid, checkboxes were still editable even when updating the row was disabled by the application logic. The value was not saved, but the user interface made it look like it was. This issue has been improved. Now, on the active row, the checkbox is disabled. For inactive rows, the user is still allowed to select it. After the row is activated, the value is corrected when needed. The reason for this solution is to maintain high performance in case the checkboxes on other rows are not cleared.
• If you get a validation error in a detail screen, such as one caused by an empty mandatory field, a snackbar message showing this error would appear on each refresh. This would only occur if both auto-save and auto-refresh are enabled on the main subject. We solved this by pausing the refresh on the main subject whenever there are unsaved changes in any of its details at any level. Refreshing resumes once there are no longer unsaved changes.
• We resolved a situation where the Universal GUI could enter an infinite loop. This could occur if Indicium returned a 422 error on an auto-save for reasons unrelated to mandatory fields, or if it involved a mandatory hidden field.
• We fixed an issue where changing a checkbox value in a card list would not be applied, even after refreshing the subject. The value is now updated automatically.
• If you encounter a validation error while editing in a form, the application logic values from the server would not be applied until you resolved the error. In certain cases, new values from the server may help to resolve such a validation error. For example, when the logic fills an empty mandatory field for an address after you provide the postal code and house number. Now, we apply the new values again, so you cannot get stuck on saving/executing the changes. This not only applies to regular forms but also to task forms.
• When consecutively switching rows in a default editable grid, either by clicking or using the up/down arrow keys, the grid would occasionally exit the edit mode. This has been resolved.
• After changing a value in a lookup-type column of a default editable grid and leaving the row to save it, the previous value would flash briefly. Now, the newly selected value is shown consistently.
• Values coming from the default procedure would not be processed when modifying a date field. Furthermore, when navigating through a default editable grid without making changes, rows would erroneously be saved if a date field was focused. Both these issues have been fixed.

Fixes for charts:

• When you selected the chart type Funnel, the chart type would not change. This has been fixed.
• When you configured 2d bar (stacked) as chart type in the Software Factory, a value would not be displayed for Chart type in the popup Chart settings. Furthermore, when trying to save the values as configured in the popup Chart Settings in this situation, the Universal GUI would crash. Both these issues has been resolved.

Other fixes:

• When a task is set up with a default procedure, a parameter may be filled with an invalid value. If this is handled by sending a message using tsf_send_message with the abort parameter set to 1, the old value of the task parameter would not be restored. This has now been fixed.
• When clicking a detail tile, the process action Zoom detail did not work as a process flow starting point. It does now.
• When you selected the chart type Funnel, the chart type would not change. This has been fixed.
• Actions on a scheduler may have triggered unexpected error messages when the scheduler was bound to a subject variant (SF concept). This occurred due to differences in the available columns between the original subject and the variant. This has now been fixed.

• When "2d bar (stacked)" was configured as chart type in the Software Factory, Universal would not display a value for "Chart type" in the "Chart settings" popup.
  Furthermore, when trying to save the Chart Settings popup in this situation, Universal would crash.
  Both these issues has been resolved.

• Executing a task by using the Tab key in a barcode field that is the last visible task parameter did not work anymore. Furthermore, when you configured in the Software Factory to disable layouts for the task, the same functionality would sometimes not work. Both of these issues have been resolved.

What we will be working on next sprint

The next sprint we will be working on:

• Grid default edit-mode improvements
• Universal performance improvements
• High priority tickets

Questions or suggestions?