Hello everyone,

In this release, we have improved the way cell data is copied from the grid, optimized performance in edit mode, and added support for report parameter properties action and Export path. We have also solved some minor 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.12

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.12 here

Contents

New and changed

Improved the way cell data is copied from the grid

change

It was already possible to copy data from the grid to the clipboard by selecting the cell and using Ctrl + C. This feature has been improved in this release.

Previously, when a user copied a cell from a grid with Ctrl + C, the inner grid data for the current row was copied instead of the displayed data, which in some cases can be different.

Now, when a cell is copied with Ctrl + C, the data that will be copied is the displayed data. There are some exceptions, though. Some controls format the value before copying:

• Color: copies the color value without image.
• Checkbox: if selected, true will be copied; if cleared, then false will be copied; if indeterminate, then a blank space will be copied.
• Progress bar (read only): copies the percentage displayed within the progress bar.

Some controls copy a blank space to the clipboard:

• File link
• File upload
• HTML
• HTML card
• Image combo
• Image link
• Image upload
• Signature

All the other supported control types will be copied exactly as they are presented to the user in the grid.

Improved performance in edit mode

change

We have improved the performance of the Universal GUI in default edit mode by reducing the number of requests made when entering edit mode and after changing a value.

We will continue to optimize performance in future releases.

Support for report parameter properties action and Export path

new

For a report parameter with the property action, the Universal GUI now creates a dropdown editor that displays the available options. Users can choose the download type for the report from this dropdown: Excel, image, Word, HTML, etc. The default is a preview in PDF format.

In addition to the action property, we have also added the Export path property. You can use this property to influence the name of the downloaded report file.

You can set these properties in the Software Factory in the menu Processes > Reports > tab Report parameters.

Warning about HTTP

new

For security and performance reasons, it is recommended to run the Universal GUI on HTTPS. Now, when running on HTTP, a warning message is shown to the user.

Opt-out of Sentry crash reporting

new

It is now possible to opt-out of Sentry crash reporting by adding this to config.json:

"disableErrorReporting": true

Minor fixes and tasks

Fixes for layout and styling:

• For subjects with auto-save enabled, if a user updated a record and then navigated to their profile menu and selected User preferences, a pop-up with untranslated warning messages was displayed. This has been fixed.
• Very rarely, the CRUD buttons would not show up on screen type breakpoints. This has been fixed.

Fixes for issues on startup:

• Users would sometimes get the following snack bar error when starting the Universal GUI: "Request error: The object was not found. You may have insufficient rights or the object no longer exists." After this error, start objects would not be opened. This has been fixed.

Fixes for slow connections:

• On a slow connection, if users clicked too fast for the network to process the requests, they were sometimes confronted with "Objects could not be found" errors. These errors looked bad to users but could be ignored most of the time. Now, the user no longer gets this message. You can still see the 404 status of the corresponding network request in your browser's DevTools.

Fixes in form and grid:

• Drag-drop tasks would not work if used in tables without variants. This has been fixed now.
• Previously, if you tried to select multiple records at one time using the Shift key, it would not work as expected if this was the first action taken in the grid component. This has now been fixed.
• A read-only column was editable in the grid though it was set to read-only in the model. This has been fixed. This could happen for regular columns where the Type was set to Read-only for component types:
  - Any editor in the grid
  - Lookup editors in the form where the Select button in the pop-up was not disabled.
• The lookup editor can contain a past value that is no longer available in the dropdown. Previously, when a user started editing, the field became empty. This was not correct. The field should show the value until something else is selected. This has been fixed.
• Every time a row in an editable grid was switched, the data in the lookup columns would be reloaded, causing it to disappear and reappear. This has been fixed. Data in lookup columns are no longer reloaded if there are no changes.

What we will be working on next sprint

The next sprint we will be working on:

• Grid default edit-mode improvements
• High priority tickets

Questions or suggestions?