Hello everyone,

In this sprint, we have added configurable import for Excel and CSV files. We have also added support for the Language user preference, the Change sort order process action, and fallback display types for table tasks and reports.

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 2023.3.10

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 2023.3.10 here

Contents

New and changed

Support for fallback display types

new​

We have added support for fallback display types for table tasks and reports. This is available as of Thinkwise Platform version 2023.3.

To customize how a table task or table report is shown in the Universal GUI, you could already change its Display type. If there was enough space, the presentation would be according to the selected type. With insufficient space, the Universal GUI decided what the fallback display type would be.

You can now customize the fallback behavior to suit your needs. We have added additional combinations of fallback display types as options to cover most cases. 

For more information, see the Thinkwise Platform 2023.3 release notes.

Configurable import

new

You can now configure how to import an Excel or CSV file into your subject. You can find the Import option in a subject's overflow menu. The import consists of various steps that guide you to the configuration:

The first step is Select file. Here, you can select the file that you want to import. .XLS, .XLSX, or .CSV are the only allowed extensions.

In the second step, Import mode, you can configure how the data should be imported. Based on the selected mode, the description at the bottom differs because it depends on the location where the export is started. When working in a detail subject, it explains why the related columns to the parent subject could not be changed. The options for the import mode are:

• Insert all data
• Add new records, update existing records
• Only update existing records

The third step is Prepare data. This page differs according to the type of file that is selected. With the fields at the top, you can select which part of the selected file you want to import. It also shows sample data of the selected file.

• For an Excel file, you can select the worksheet and where the data starts.
• For a CSV file, only the headers field is available. Indicium guesses the delimiter separating the column values. This cannot be changed yet.

The fourth step is Map data. Here, you can map the column of a CSV or Excel file to a column in your database. You can select which columns should be imported. If columns are not available in Excel but do require a value, you can set a constant value that should be used for each row. Next to each column, a preview is shown of the data that will be imported.

The final step is Import. This screen shows an overview of the configured settings and a preview of what the import will look like. Select the button Import to start the import. A progress bar is shown.

When the import has finished, an overview shows how many records have been imported, updated, or failed. You can download an Excel file with the rows that failed to import.

Tab icons hidden by default

change

Previously, icons on tabs were, by default, always visible. Based on user feedback, we have changed this. Now, tab icons are hidden by default.

You can use the new extended property ShowTabIcons to show them.

Language as a user preference

new change

Users can now change their language in an application with the Universal GUI. This is available as of Thinkwise Platform version 2023.3.

They can select User preferences in the profile menu and switch to any available language. If no translations are available for the selected language, the Universal GUI will show the default language. Note that it can take up to one minute for all translations to load.

In addition, the option Change password has moved from the User preferences to its own item in the profile menu.

Support for 'Change sort order' process action

new

Universal GUI now supports the Change sort order process action. It was already available for the Windows and Web GUIs.

We have also solved a problem with the sort arrow. It would not be removed when resetting the sort order.

Improved hierarchy and attribute trees

change

We have improved the hierarchy and attribute trees. They now support multi-selection and conditional layouts.

This change also results in some small behavioral changes:

• Previously, you had to use the left and right arrows to expand and collapse. Now, this is done with the Enter key instead.
• The trees have some minor visual changes.

In addition, we have solved a crash in the attribute tree and the problem of a broken hierarchy tree when multiple parent columns were configured.

 Skeleton screen when loading

change

The Universal GUI now shows a skeleton instead of a spinner screen when loading. If you want to go back to the spinner, set enableSkeletonScreens to false in the config.json file.

Saving when switching tabs changed

change

If you switched to a different tab with Auto-save enabled and the subject in edit mode, it would be saved in the background.

Now, if you switch to another tab, the subject will be saved first. Only if the save succeeds will it switch to the new tab. This prevents errors in the newly opened tab about the previous subject, for example, when a mandatory field is empty.

Fixed multi-select for touch screens

fix

We have solved some problems with multi-select for touch screens:

• It is now possible to deselect the active record (as shown in a form and breadcrumb). When deselected, the first selected record will become the new active record. Deselecting is not possible if the active record is the only selected record; this is intentional.
• If you deselect the active record when it is the last record in a selection, the GUI now shows the right number of selected records in the top bar (instead of 0).
• When you start selecting multiple records by long-pressing a record, this record now becomes the new active record, as expected. Previously, it would be added to a selection with the prior active record.
• Now, checkboxes are shown on each row in a grouped grid.
• It is no longer possible to exit multi-select with long-pressing, you must now press the X in the top bar.

Minor fixes and tasks

• Adding a new row that included a read-only checkbox field on a grid would ignore the default value of that field and show a NULL/indeterminate checkbox.
  This has been fixed, the proper value will be shown now.
• The HTML control did not save the contents correctly when closing the keyboard with the Done button on iOS.
  This has been fixed.
• The control for the file input field scaled outside the normal field boundary during uploading. This has been fixed.
• The tooltip for grid headers did not look as intended. This has been fixed.
• A detail subject kept showing summary/aggregation value underneath the grid when a parent record was selected without detail records.
  This resulted in a possible expensive data request without filtering on the parent keys. This has been fixed; without a parent record, there will be no summary.
• The Copy to clipboard control for forms would not expand to match the field height in the positions setting.
  This has been fixed. The control now also allows multiple lines of text if the field height in positions is higher than 1.
• Clicking on hyperlinks in form input fields (Email, Telephone No, URLs, etc.) would not work. This has been fixed.

What we will be working on next sprint

The next sprint we will be working on:

• Advanced filter form
• Pivot series totals
• Editable cube view

Questions or suggestions?