Release notes Universal GUI (2022.1.15.0)

May 13, 2022:Changed beta release to the full version: 2022.1.15.0 Improvements for issues found in the previous beta release: In a specific case, when a subject was opened from a process flow step and this process flow activated a filter simultaneously while loading, parts of the subject appeared empty, or showed unrelated data. This has been fixed. In some components, for example, the Resource Scheduler and the Maps component, user interface styling was not applied correctly. This has been fixed. When opening (for example) the User Preferences menu while an auto-refresh screen was open, the application stopped responding. This has been fixed.  Hello everyone,In this sprint, we made a number of changes and improvements and fixed some issues. One important change is that process flows are now disabled by default in a lookup popup or context. To enable process flows, you can use an extended property. You can read more about the other changes, improvements, and fixes in the topics below.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.Universal GUI version 2022.1.15.0Do 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 an allowed origin in 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 2022.1.15.0 hereContents of this releaseUniversal GUI version 2022.1.15.0 Changed Process flows by default disabled in lookup popup or context Pivot grid improvements and changes Improved performance: layout calculated based on model settings Improved (grid) performance Tooltips more legible Minor fixes and tasks What we will be working on next sprintChangedProcess flows by default disabled in lookup popup or contextDue to some issues with process flow execution from within a popup of a lookup field, the process flows are no longer executed by default within a lookup popup or context. Similar to our other interfaces, they now listen to the extended property AllowProcessFlowsInLookupDialogs. We will solve the known issues later on.Pivot grid improvements and changesIn this sprint, we have improved the pivot grid in several ways:The look and feel have been improved. When expanding a category (row), the total will be shown in the parent row. We have added nested series (columns) for all aggregation types. Previously, when a cube view had multiple series (columns) and the values were not of type 'SUM', the pivot would not start. We have added nested groups for all aggregation types. Previously, when a cube view had multiple categories (rows) and the values were not of type 'SUM', the pivot would not start.Another change is that nested series (columns) are always expanded in this release, though collapse and expand will be available again in a future release. Previously, if conditions were met, these were expandable and collapsible. The main reason for this is a necessary technical overhaul that will pave the way for future improvements:series (columns) subtotals series (columns) grand totals expand and collapse series (columns) category (row) grand totals default expanded series/categories. Improved look and feel in the pivot gridImproved performance: layout calculated based on model settingsPreviously, the Universal GUI would request Indicium to get the model's layout settings. Now, it can calculate the model layout settings itself, so the request to Indicium is no longer necessary.So, if you deselect the logic concept Layout in a subject's settings, the Universal GUI will now use the model settings instead of executing the layout's stored procedure. This setting is available in the menu User interface > Subjects > tab Default/Variants > tab Settings > tab Performance > group Use concept > checkbox Layout.This can slightly speed up the performance when switching a row, editing, and opening a screen.Improved (grid) performanceWe made several (grid) performance improvements. In the coming sprints we will continue to focus on more performance improvements.Tooltips more legiblePreviously, a tooltip appeared below an element when a user hovered over it. Sometimes this would cause the cursor to cover part of the text, making it partially unreadable. This has been fixed by changing the placement of the tooltip. Now it appears above an element when the user hovers over it.Minor fixes and tasksOn mobile devices, when selecting multiple rows in a grid, the checkbox to select all rows was horizontally not aligned with the checkboxes for the individual rows. This has been fixed. When typing a value in a filter field on a tablet, the extended touch keyboard pushed the filter component away from the screen and reverted the typed value. This has been fixed. Now the filter component in a document claims at least the height of a single control, so the filter fields always remain visible. Opening a lookup while no record was selected resulted in a Bad Request error. This has been fixed. If the preview component cannot generate a preview for a file, it now displays the message No preview is available. Fixes for file upload: Uploading a file in edit mode was only possible by clicking the icon, not the bar itself. This has been fixed. When you select a file in a form in edit mode, you can now click the upload control or press Enter to open the file selector and easily overwrite the previously selected file. The cursor now changes to a 'pointer' icon when you hover over the field, in both edit and read mode, since the text cannot be edited. When a user switched tabs in a resource scheduler component and returned to the first tab, the years and weeks were no longer displayed. This has been fixed, they remain visible now. A right-aligned control in an editable grid got too much padding at the left, so it got cut off at the right. This has been fixed. When saving an edited record in the grid with validation errors, the grid row height reserved some room for a validation error that did not come. As a result, some types of controls did not align properly. The height now remains the same. Auto-refresh would stop working after a record in its subject was edited. This has been fixed. After filtering the data set, the Change detection logic is now prevented from firing more often than required. We have fixed that a date value sometimes was not processed when directly executing a task after filling in a date. If the tiles menu is the default menu for an application, and the last open document was closed by a process flow, the Universal GUI showed an empty screen. It only contained the backplate and no tiles menu. This has been fixed, the tiles menu now is displayed as it is supposed to be. When switching fast between records and clicking edit, the wrong record would be edited. This has been fixed.What we will be working on next sprintIn the next sprint, we will mainly focus on fixing known issues. Furthermore, we will be working on:Pivot column subtotals - Subtotals on the columns and series of the pivot. Suggested GUI Action: Download file. (grid) performance research. In progress: UI/UX design for add row. UI/UX design for vertical tab pages.

Related products:Universal GUI

Release notes Universal GUI (2022.1.15 BETA)

Hello everyone,In this sprint, we made a number of changes and improvements and fixed some issues. One important change is that process flows are now disabled by default in a lookup popup or context. To enable process flows, you can use an extended property. You can read more about the other changes, improvements, and fixes in the topics below.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.Universal GUI version 2022.1.15 BETADo 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 an allowed origin in 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 2022.1.15 BETA here This is a beta release, which can be used to test the new features. This release is not suitable for use in a production environment. The full release will be available this Friday.Contents of this releaseUniversal GUI version 2022.1.15 BETA Changed Process flows by default disabled in lookup popup or context Pivot grid improvements and changes Improved performance: layout calculated based on model settings Improved (grid) performance Tooltips more legible Minor fixes and tasks What we will be working on next sprintChangedProcess flows by default disabled in lookup popup or contextDue to some issues with process flow execution from within a popup of a lookup field, the process flows are no longer executed by default within a lookup popup or context. Similar to our other interfaces, they now listen to the extended property AllowProcessFlowsInLookupDialogs. We will solve the known issues later on.Pivot grid improvements and changesIn this sprint, we have improved the pivot grid in several ways:The look and feel have been improved. When expanding a category (row), the total will be shown in the parent row. We have added nested series (columns) for all aggregation types. Previously, when a cube view had multiple series (columns) and the values were not of type 'SUM', the pivot would not start. We have added nested groups for all aggregation types. Previously, when a cube view had multiple categories (rows) and the values were not of type 'SUM', the pivot would not start.Another change is that nested series (columns) are always expanded in this release, though collapse and expand will be available again in a future release. Previously, if conditions were met, these were expandable and collapsible. The main reason for this is a necessary technical overhaul that will pave the way for future improvements:series (columns) subtotals series (columns) grand totals expand and collapse series (columns) category (row) grand totals default expanded series/categories. Improved look and feel in the pivot gridImproved performance: layout calculated based on model settingsPreviously, the Universal GUI would request Indicium to get the model's layout settings. Now, it can calculate the model layout settings itself, so the request to Indicium is no longer necessary.So, if you deselect the logic concept Layout in a subject's settings, the Universal GUI will now use the model settings instead of executing the layout's stored procedure. This setting is available in the menu User interface > Subjects > tab Default/Variants > tab Settings > tab Performance > group Use concept > checkbox Layout.This can slightly speed up the performance when switching a row, editing, and opening a screen.Improved (grid) performanceWe made several (grid) performance improvements. In the coming sprints we will continue to focus on more performance improvements.Tooltips more legiblePreviously, a tooltip appeared below an element when a user hovered over it. Sometimes this would cause the cursor to cover part of the text, making it partially unreadable. This has been fixed by changing the placement of the tooltip. Now it appears above an element when the user hovers over it.Minor fixes and tasksOn mobile devices, when selecting multiple rows in a grid, the checkbox to select all rows was horizontally not aligned with the checkboxes for the individual rows. This has been fixed. When typing a value in a filter field on a tablet, the extended touch keyboard pushed the filter component away from the screen and reverted the typed value. This has been fixed. Now the filter component in a document claims at least the height of a single control, so the filter fields always remain visible. Opening a lookup while no record was selected resulted in a Bad Request error. This has been fixed. If the preview component cannot generate a preview for a file, it now displays the message No preview is available. Fixes for file upload: Uploading a file in edit mode was only possible by clicking the icon, not the bar itself. This has been fixed. When you select a file in a form in edit mode, you can now click the upload control or press Enter to open the file selector and easily overwrite the previously selected file. The cursor now changes to a 'pointer' icon when you hover over the field, in both edit and read mode, since the text cannot be edited. When a user switched tabs in a resource scheduler component and returned to the first tab, the years and weeks were no longer displayed. This has been fixed, they remain visible now. A right-aligned control in an editable grid got too much padding at the left, so it got cut off at the right. This has been fixed. When saving an edited record in the grid with validation errors, the grid row height reserved some room for a validation error that did not come. As a result, some types of controls did not align properly. The height now remains the same. Auto-refresh would stop working after a record in its subject was edited. This has been fixed. After filtering the data set, the Change detection logic is now prevented from firing more often than required. We have fixed that a date value sometimes was not processed when directly executing a task after filling in a date. If the tiles menu is the default menu for an application, and the last open document was closed by a process flow, the Universal GUI showed an empty screen. It only contained the backplate and no tiles menu. This has been fixed, the tiles menu now is displayed as it is supposed to be. When switching fast between records and clicking edit, the wrong record would be edited. This has been fixed.What we will be working on next sprintIn the next sprint, we will mainly focus on fixing known issues. Furthermore, we will be working on:Pivot column subtotals - Subtotals on the columns and series of the pivot. Suggested GUI Action: Download file. (grid) performance research. In progress: UI/UX design for add row. UI/UX design for vertical tab pages.

Related products:Universal GUI

Release notes Indicium (2022.1.18)

Hello everyone,In this sprint, we have added new settings for OpenID Identity Providers and solved some issues. Furthermore, we are working hard on features for the upcoming 2022.2 Thinkwise platform release and features that take multiple sprints to build.You can read more about Indicium's features in the Indicium user manual.We will keep you updated regularly about Indicium's progress.Download Indicium Universal release 2022.1.18 here. ContentsIndicium Universal New settings for OpenID Identity Providers Minor fixes and tasks  Indicium Universal New settings for OpenID Identity Providers IncludeProfileScope - Indicium default requests the openid and profile scopes for external Identity Providers. However, not all Identity Providers support the profile scope. We have, therefore, introduced a new setting: IncludeProfileScope. You can add it to the appsettings.json file with the value false to prevent Indicium from requesting the profile scope. PromptLogin - Indicium already supported the AlwaysPromptLogin setting, but this only allowed you to specify true in order for Indicium to use the "login" prompt. The new PromptLogin setting allows you to specify a string, for example, select_account, to use any prompt setting supported by the Identity Provider.NoteAs of platform version 2022.2, the settings for external Identity Providers will be available in IAM. Minor fixes and tasksIndicium did not supply a file name hint to the browser for previewed files. As a result, when saving a file from the PDF previewer in the Universal GUI, it would use a part of the URL as the file name. This has been fixed. We have fixed a performance issue that occurred on process flows that required interaction with the Universal GUI when using an SF meta source (i.e., /sf/appl instead of /iam/appl). The issue could cause a delay of several seconds on every action that required communication with the Universal GUI. System flow actions were not affected.

Related products:Indicium Service Tier

Release notes Universal GUI (2022.1.14)

April 22, 2022:Changed beta release to the full version: 2022.1.14 Improvements for issues found in the previous beta release: When opening one of some specific screens after opening another screen, the specific screen was correctly listed in the OPEN DOCUMENTS section, but it did not show any content. This has been fixed. Hello everyone,In this sprint, we made it possible to open multiple instances of the same subject by Ctrl-clicking the corresponding menu item. Double-clicking a detail tab opens a new document zooming in on the detail. Furthermore, we added two configuration settings to improve grid performance. And splitter positions are now retained after refreshing the Universal GUI.More new functionality and improvements are listed below.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.Universal GUI version 2022.1.14Do 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 an allowed origin in 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 2022.1.14 here Contents of this releaseUniversal GUI version 2022.1.14 New Open a subject twice through Ctrl-clicking Double-click a detail tab to open a new document and zoom in on the detail Splitter positions retained after refreshing the Universal GUI Changed New configuration settings for grid performance Overflow menu changes Minor fixes and tasks What we will be working on next sprintNewOpen a subject twice through Ctrl-clickingYou can now open multiple instances of the same subject by holding CTRL and clicking the corresponding menu item.Double-click a detail tab to open a new document and zoom in on the detailYou can now double-click a detail tab to open a new document and zoom in on the detail. This does not apply to mobile devices as there is no double click functionality.Splitter positions retained after refreshing the Universal GUISplitter positions were retained after closing and reopening a subject but disappeared when refreshing the Universal GUI. As of this version, the splitter positions are also retained after a refresh.ChangedNew configuration settings for grid performanceWe have added two configuration settings to improve grid performance. These settings can be useful for applications running on mobile devices with low hardware specifications. Record changes and scrolling appear to be slow on such mobile devices. We added two config.json options: gridDisableRowSwitchDebounce and gridRowBuffer.gridDisableRowSwitchDebounce: true | false | mobile. Default = falseWhen set to true or mobile while working on a mobile device, the first record change will be processed immediately instead of waiting for the 300ms debounce timeout. Any subsequent record changes will still be debounced.gridRowBuffer: any number. Default = 10The gridRowBuffer property sets the number of rows the grid displays outside the visible area. The default is 10. For example, if a grid shows 30 rows (the number of rows that fits on your screen without scrolling), the grid will render 50 rows in total (10 extra rows before and 10 extra rows after). When scrolling, 10 rows can immediately be displayed, so the user will not see any redraw.Setting a low row buffer makes the initial loading of the grid faster (for example, when data is first loaded, or after filtering or grouping). Setting a high row buffer will reduce the visible vertical scrolling of the redraw.Overflow menu changesIn the overflow menu of the search and filter bar, when users are not allowed to filter, the Quick filter and Clear all filters options were read-only. This has changed. As of this version, these buttons are hidden. In addition, if a subject does not contain any prefilters, filters, or sorting, the overflow menu in the search and filter bar will be hidden.Minor fixes and tasksIn some cases, when a user opened a document containing a map component, no base layer was selected. Now a default base layer is selected. Cubes did not filter on values entered in a filter form field. This has been fixed. For look-ups with Def. control set to 'Combo (sorted)', the look-up control was still sorted alphabetically instead of according to the default sorting of the look-up subject. This happened in some cases if there were multiple sorting columns. When a user created a lookup value with an ID of '0', the lookup would only be visible in edit mode. The '0' would become invisible again when the user exits edit mode. This has been fixed. Deleting a record in a detail tab would sometimes change the parent's active record. This has been fixed. Recently we implemented task bars as a screen component. The task bar component is removed from the screen if it is directly below the default action bar. Otherwise, you would see two bars directly below each other. However, the task bar was not removed if it was on a tab. This has been fixed. If the task bar is elsewhere on the tab, its buttons will be correctly removed from the default action bar. In a specific case, some action bar buttons were displayed over the nearby task or report buttons, especially the Refresh and Delete buttons. This has been fixed. After dragging the cursor outside the browser window while moving a splitter, the application temporarily stopped responding. This has been fixed. In fields with the Image Combo domain, the images were not correctly colored when viewed (read) in dark mode. This has been fixed. If a chart showed a total number of objects and there were none, the tooltip would show Undefined instead of 0. This has been fixed. When opening a page with the Hide main action bar setting enabled and then reopening a page with this setting disabled, the action bar was still hidden. This has been fixed. When editing in a grid, numeric columns could not be left-aligned. This has been fixed. When adding a record in a detail subject, all data was intentionally refreshed, but a Bad Request error could also occur. This has been fixed. Look-ups based on an unauthorized look-up column did not refresh automatically. This has been fixed. Indicium now correctly instructs the Universal GUI to refresh the look-up column. In the previous version, the preview component did not support the file formats .txt, .xml, and .json. Now, these file formats are supported again. If a document was open and a process flow action Open document with input parameter open_doc_existing_yes would switch to this document, the process flow would not continue. This has been fixed. When a document was first opened, detail tiles were not visible in some cases. This has been fixed. For this fix, you must also install the Indicium 2022.1.17 release: When signing out from the Universal GUI while connected via an OpenID connection (by a third party authentication provider), the user was not redirected to the correct logout page (see below) that provides the option to sign out, either from Indicium only or sign out from the third party authentication provider. Instead, the user stayed logged in. This has been fixed. Now the correct sign-out dialog is displayed. Signing out from the third-party authentication provider also signs out from other applications connected via OpenID in the same browser session. Signing out from the Universal GUI with an OpenID connectionWhat we will be working on next sprintThe next sprint we will be working on:Improving grid performance In progress: UI/UX designs for cube panel and add row in grid.

Related products:Universal GUI

Release notes Universal GUI (2022.1.14 BETA)

Hello everyone,In this sprint, we made it possible to open multiple instances of the same subject by Ctrl-clicking the corresponding menu item. Double-clicking a detail tab opens a new document zooming in on the detail. Furthermore, we added two configuration settings to improve grid performance. And splitter positions are now retained after refreshing the Universal GUI.More new functionality and improvements are listed below.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.Universal GUI version 2022.1.14 BETADo 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 an allowed origin in 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 2022.1.14 BETA here  This is a beta release, which can be used to test the new features. This release is not suitable for use in a production environment. The full release will be available this Friday.Contents of this releaseUniversal GUI version 2022.1.14 BETA New Open a subject twice through Ctrl-clicking Double-click a detail tab to open a new document and zoom in on the detail Splitter positions retained after refreshing the Universal GUI Changed New configuration settings for grid performance Overflow menu changes Minor fixes and tasks What we will be working on next sprintNewOpen a subject twice through Ctrl-clickingYou can now open multiple instances of the same subject by holding CTRL and clicking the corresponding menu item.Double-click a detail tab to open a new document and zoom in on the detailYou can now double-click a detail tab to open a new document and zoom in on the detail. This does not apply to mobile devices as there is no double click functionality.Splitter positions retained after refreshing the Universal GUISplitter positions were retained after closing and reopening a subject but disappeared when refreshing the Universal GUI. As of this version, the splitter positions are also retained after a refresh.ChangedNew configuration settings for grid performanceWe have added two configuration settings to improve grid performance. These settings can be useful for applications running on mobile devices with low hardware specifications. Record changes and scrolling appear to be slow on such mobile devices. We added two config.json options: gridDisableRowSwitchDebounce and gridRowBuffer.gridDisableRowSwitchDebounce: true | false | mobile. Default = falseWhen set to true or mobile while working on a mobile device, the first record change will be processed immediately instead of waiting for the 300ms debounce timeout. Any subsequent record changes will still be debounced.gridRowBuffer: any number. Default = 10The gridRowBuffer property sets the number of rows the grid displays outside the visible area. The default is 10. For example, if a grid shows 30 rows (the number of rows that fits on your screen without scrolling), the grid will render 50 rows in total (10 extra rows before and 10 extra rows after). When scrolling, 10 rows can immediately be displayed, so the user will not see any redraw.Setting a low row buffer makes the initial loading of the grid faster (for example, when data is first loaded, or after filtering or grouping). Setting a high row buffer will reduce the visible vertical scrolling of the redraw.Overflow menu changesIn the overflow menu of the search and filter bar, when users are not allowed to filter, the Quick filter and Clear all filters options were read-only. This has changed. As of this version, these buttons are hidden. In addition, if a subject does not contain any prefilters, filters, or sorting, the overflow menu in the search and filter bar will be hidden.Minor fixes and tasksIn some cases, when a user opened a document containing a map component, no base layer was selected. Now a default base layer is selected. Cubes did not filter on values entered in a filter form field. This has been fixed. For look-ups with Def. control set to 'Combo (sorted)', the look-up control was still sorted alphabetically instead of according to the default sorting of the look-up subject. This happened in some cases if there were multiple sorting columns. When a user created a lookup value with an ID of '0', the lookup would only be visible in edit mode. The '0' would become invisible again when the user exits edit mode. This has been fixed. Deleting a record in a detail tab would sometimes change the parent's active record. This has been fixed. Recently we implemented task bars as a screen component. The task bar component is removed from the screen if it is directly below the default action bar. Otherwise, you would see two bars directly below each other. However, the task bar was not removed if it was on a tab. This has been fixed. If the task bar is elsewhere on the tab, its buttons will be correctly removed from the default action bar. In a specific case, some action bar buttons were displayed over the nearby task or report buttons, especially the Refresh and Delete buttons. This has been fixed. After dragging the cursor outside the browser window while moving a splitter, the application temporarily stopped responding. This has been fixed. In fields with the Image Combo domain, the images were not correctly colored when viewed (read) in dark mode. This has been fixed. If a chart showed a total number of objects and there were none, the tooltip would show Undefined instead of 0. This has been fixed. When opening a page with the Hide main action bar setting enabled and then reopening a page with this setting disabled, the action bar was still hidden. This has been fixed. When editing in a grid, numeric columns could not be left-aligned. This has been fixed. When adding a record in a detail subject, all data was intentionally refreshed, but a Bad Request error could also occur. This has been fixed. Look-ups based on an unauthorized look-up column did not refresh automatically. This has been fixed. Indicium now correctly instructs the Universal GUI to refresh the look-up column. In the previous version, the preview component did not support the file formats .txt, .xml, and .json. Now, these file formats are supported again. If a document was open and a process flow action Open document with input parameter open_doc_existing_yes would switch to this document, the process flow would not continue. This has been fixed. When a document was first opened, detail tiles were not visible in some cases. This has been fixed. For this fix, you must also install the Indicium 2022.1.17 release: When signing out from the Universal GUI while connected via an OpenID connection (by a third party authentication provider), the user was not redirected to the correct logout page (see below) that provides the option to sign out, either from Indicium only or sign out from the third party authentication provider. Instead, the user stayed logged in. This has been fixed. Now the correct sign-out dialog is displayed. Signing out from the third-party authentication provider also signs out from other applications connected via OpenID in the same browser session. Signing out from the Universal GUI with an OpenID connectionWhat we will be working on next sprintThe next sprint we will be working on:Improving grid performance In progress: UI/UX designs for cube panel and add row in grid.

Related products:Universal GUI

Release notes Universal GUI (2022.1.13)

April 1, 2022:Changed beta release to the full version: 2022.1.13 Improvements for issues found in the previous beta release: HTML field labels were not aligned correctly like the other form controls. Now they are. When saving a record containing a FILE_UPLOAD control, the application stopped responding in some cases. This has been fixed. In a grid column group, the group separator line did not appear at the top right of the right column in some cases. This has been fixed.  Hello everyone,In this sprint, we support displaying overlay layers on top of the base layer of a map, and the grid column width can now automatically be determined based on the header and the data. Furthermore, you can now group columns in a grid, and you can specify the size of task bar icons. More new functionality and improvements are listed below.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.  Universal GUI version 2022.1.13Do 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 an allowed origin in 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 2022.1.13 here  Contents of this releaseUniversal GUI version 2022.1.13 Breaking Install Universal 2022.1.13 together with Indicium 2022.1.15 Fields layout in forms now use Software Factory settings New Map Overlays Group columns in a grid Grid column width can be based on headers and data Changed Size of task bar icons can be set Minor fixes and tasks What we will be working on next sprint BreakingInstall Universal 2022.1.13 together with Indicium 2022.1.15The Universal GUI now communicates differently with Indicium when executing a task on multiple rows with the Popup for each row setting enabled. This makes this release dependent on the 2022.1.15 release of Indicium:If you install this Universal 2022.1.13 release, you must also install the Indicium 2022.1.15 release.This also fixes a known issue:Subjects did not refresh properly after all tasks were executed when executing a task on multiple rows with the Popup for each row setting enabled.Fields layout in forms now use Software Factory settingsForms in the Universal GUI are responsive to the device on which they are displayed. The layout of controls in a form is determined by the available space on the respective device.The form width determines how many columns of fields with their labels are displayed. Within a group, fields are displayed together. A group is created when Field in next group or Field in next tab is set for a column in the Software Factory, via navigation path:menu User interface > Subjects > tab Default > tab Components > tab FormThe number of columns in a form is determined differently as of this version. Previously, a form was split into columns when the width of the field and its label together was more than 300 pixels. As of this version, the subject's settings in the Software Factory are used for this, adding the label width to the field width. These two settings can be set for the entire application at once, or for a specific subject, via navigation path:menu User interface > Subjects > tab Default/Variants > tab Settings > tab GeneralIf this new calculation results in a lower value, more controls can be displayed side by side in different columns. This utilizes the screen space more efficiently.Due to this change, the width at which a new column is displayed by default has been changed from 300 to 335. However, this can make forms appear differently.Especially notice subjects where the value is customized. The Universal GUI will react to the settings from now on. To check, execute this query on your Software Factory/IAM database:SELECT tf.[gui_appl_id] ,a.[transl] ,[tab_id] ,[tab_variant_id] ,[no_of_cols_in_form] ,[form_col_width] FROM [i_ui_tab_form] tf JOIN i_ui_gui_appl a on a.gui_appl_id = tf.gui_appl_idNewMap OverlaysIn the Universal GUI, you can now display overlay layers on top of the base layer of a map to add additional information such as weather or traffic information. You can also toggle an overlay layer on and off. Example of a map with Route info and seaways overlay layerGroup columns in a gridYou can now group columns that are part of the subjects sorting in a grid. This grouping is fixed on one or more columns and must be pre-configured in the Software Factory via navigation path:User Interface > Subjects > Data > SortThe Group until option specifies the last column by which to group. All columns up to and including the column with Group until selected become part of the grouping. In the example below, persons are grouped by country, then by province, and then by city. Group persons by country, province, and cityIn the Universal GUI, the result looks like this: Grouping resultNote: Letting the user dynamically group on columns is a different feature that will be added in the future.Grid column width can be based on headers and dataFor grids, the Universal GUI now supports the Auto column width setting 'Headers and data'. This setting indicates that the column width is automatically determined based on the header and the data. The Auto column width setting does not apply to fixed-size columns. Auto column width setting Headers and dataSee also: auto column width.ChangedSize of task bar icons can be setIn the previous sprint, we introduced the positioning of task bars across the entire subject by dragging a Task bar component onto a screen type. Now, you can specify the size of the task bar icons in the Software Factory. Screen type with task bar and Icon size propertyIn the Software Factory, you can choose from 7 possible icon sizes (in pixels). In the Universal GUI, these sizes are translated into 3 possible values, according to the following table:Icon size in Software Factory Icon size in Universal GUI Button size Compact mode Button size Comfortable mode 16*16, 20*20 20*20 32*32 40*40 24*24 28*28 40*40 48*48 32*32, 40*40, 48*48, 64*64 36*36 44*44 56*56 The icon size is also affected by the Compact or Comfortable mode setting. In compact mode, less padding is applied. More padding is applied in the comfortable mode.The icon size set for task bar icons also applies to icons in the action bar at the top. This has made these icons a little more compact.Example: A task bar with small icons and a task bar with large iconsMinor fixes and tasksWhen a user tried to perform some activity after a user session expired, a popup message notified the user to sign in again. For example, when opening the documents tab. However, if the user tried to switch to a different application after their session expired, the application would stop responding. Now, a popup message appears. Conditional layouts with the condition Contains or Does not contain were not visible. Now, they are. A toolbar containing items, such as prefilters, can be displayed in the form of a uniquely colored icon representing the first letter of the item's name. However, in an overflow or dropdown menu, the color of these icons would be identical and non-unique. This has been fixed. When using the Preview component, unknown file types were unnecessarily downloaded. This has been fixed. Now, a message is displayed: The file cannot be previewed. The Start report process action did not receive any output parameters from the process flow. This has been fixed. Warning messages without message options contained an OK button. This button label text now reads CLOSE. When a default procedure was started, file type fields were not emptied. This has been fixed. When entering a search condition and exiting the search field before the search was completed, the value in the search field was temporarily reset to its previous value (or empty). This has been fixed. The data mapping column of a Maps component only accepted the VARCHAR data type. For an INT data type, no markers were visible. This has been fixed. Also, when the id and the data value of the domain elements differ, the marker is now displayed. Background: In the Maps component, a column with domain elements specifies the type of the object displayed on the map (for example, a marker or polygon). These elements map to the entity_type column of the record of the underlying subject. In a cube field, group intervals such as Year, Quarter, Month, or Week could only be used with charts, not pivot tables. Now, you can use group intervals also in pivot tables. After navigating to the next record, in some cases, multiple records were selected. This has been fixed. When searching a multi-page grid on a detail subject, no result was returned if it was not visible on the current page. This has been fixed.What we will be working on next sprintThe next sprint we will be working on:Pivot grid enhancements - Calculations on grouped data, for example, the average value. Splitter position user preference - This will save all the splitter positions to the user device. Compact mode grid density - This will make the grid height more dense in compact mode. Allow users to open a subject twice through Ctrl-clicking - When Ctrl-clicking a subject in the menu, this subject will be opened a second time as an open document. When double-clicking a detail tab page, this tab page will be opened as a new document. Switching between menus - This enables the user to switch between menus from the application when there are multiple menus. 

Related products:Universal GUI

Release notes Windows GUI and Web GUI (2022.1.15)

Hello everyone,In this sprint, we solved some issues. Also, Thinkwise Platform support for release 2020.1 ends, and unknown messages from Indicium are now displayed directly to the end-user.You can read more about the Windows and Web GUI's features, in the GUI user manual. We will keep you updated regularly about the Windows and Web GUI's progress.Download Windows GUI 2022.1.15 here. Download Web GUI 2022.1.15 here.BreakingThinkwise Platform support release 2020.1 endsSupport for Thinkwise Platform release 2020.1 is ending. Please upgrade to at least release 2020.2. Attempts to launch a GUI with an unsupported Software Factory or IAM version will result in an error. See also: lifecycle policy ChangedReport unknown errors from Indicium(Windows GUI) When an error occurs in Indicium, this error is always passed to the Windows GUI. The Windows GUI then translates this error into a user message. Until this version, if the Windows GUI did not recognize the message ID, this error was not passed to the user.As of this version, this behavior has changed. If the Windows GUI does not recognize the message ID, the error message from Indicium is now passed and displayed directly (without translation). This informs the user that a specific error has occurred.Minor fixes and tasks(Windows GUI) When exporting to Excel while connected to Indicium legacy, in some cases the id was displayed instead of the corresponding lookup value. This has been fixed. (Windows GUI) In a grid, when adding or editing a row and selecting a value from a lookup dialog, defaults were executed twice. This has been fixed. (Windows GUI) In the OAuth Connector process action, the input parameter UsePrompt was not always passed correctly, which resulted in the prompt= part not being removed. This has been fixed. (Web GUI) In a grid with the add_row action enabled (to enter data immediately), selecting all rows with the keyboard shortcut Ctrl+A also selected the empty row, and an error occurred. This has been fixed. (Web GUI) When sorting a grid in default edit mode by clicking a header, the grid was not editable anymore. This has been fixed. (Web GUI) In a grid with multiple pages, the wrong values were filtered: Quick filters were applied to a row on the first page and not to the current row on the current page. As a result, the filtering was on the wrong value. This has been fixed. (Web GUI) When adding a row in a grid and immediately selecting a dropdown list, lookup values were not loaded and displayed. This has been fixed.

Related products:Web and Windows GUI

Release notes Indicium (2022.1.15)

Hello everyone,In this sprint, we enhanced the error logging, and the Application connector process action has three new status codes related to the database server connection. Finally, you can now patch a property to its current value when hidden or read-only, making the Indicium API more usable for third-party applications.In addition to these changed features, we are working hard on upcoming features in the 2022.2 Thinkwise platform release, and on features that are lifted over multiple sprints, for example, horizontal scaling.You can read more about Indicium's features in the Indicium user manual.We will keep you updated regularly about Indicium's progress.Download Indicium Universal release 2022.1.15 here. Download Indicium Legacy release 2022.1.15 here.Contents of this releaseBreaking Install Indicium 2022.1.15 together with Universal 2022.1.13 (BETA) Indicium Legacy and Indicium Universal Log SQL statements with database errors Indicium Universal New status codes for Application Connector Allow patching a property to its current value when hidden or read-only BreakingInstall Indicium 2022.1.15 together with Universal 2022.1.13 (BETA)The Universal GUI now communicates differently with Indicium when executing a task on multiple rows with the Popup for each row setting enabled. This makes this release dependent on the 2022.1.13 release of Universal:If you install this Indicium 2022.1.15 release, you must also install the Universal 2022.1.13 (BETA) release Indicium Legacy and Indicium UniversalLog SQL statements with database errorsWhen an error occurs at the database level, Indicium now logs the associated error messages, including the SQL statements in the error log. These SQL statements can make it easier to determine which query caused the error.Indicium UniversalNew status codes for Application ConnectorIn a process flow, the Application connector process action has three new status codes for the executed action:-7 - Unsuccessful (could not open database)-8 - Unsuccessful (could not connect to database server)-9 - Unsuccessful (invalid credentials for database connection)Allow patching a property to its current value when hidden or read-onlyPatching a value to a resource equal to the current value, for example, for hidden or read-only columns, resulted in an HTTP Forbidden error. Now, this value is accepted (HTTP OK), making the Indicium API more usable for third-party applications.

Related products:Indicium Service Tier

Release notes Universal GUI (2022.1.13 BETA)

Hello everyone,In this sprint, we support displaying overlay layers on top of the base layer of a map, and the grid column width can now automatically be determined based on the header and the data. Furthermore, you can now group columns in a grid, and you can specify the size of task bar icons. More new functionality and improvements are listed below.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. Universal GUI version 2022.1.13 BETADo 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 an allowed origin in 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 2022.1.13 BETA here  This is a beta release, which can be used to test the new features. This release is not suitable for use in a production environment. The full release will be available this Friday. Contents of this releaseUniversal GUI version 2022.1.13 BETA Breaking Install Universal 2022.1.13 (BETA) together with Indicium 2022.1.15 Fields layout in forms now use Software Factory settings New Map Overlays Group columns in a grid Grid column width can be based on headers and data Changed Size of task bar icons can be set Minor fixes and tasks What we will be working on next sprintBreakingInstall Universal 2022.1.13 (BETA) together with Indicium 2022.1.15The Universal GUI now communicates differently with Indicium when executing a task on multiple rows with the Popup for each row setting enabled. This makes this release dependent on the 2022.1.15 release of Indicium:If you install this Universal 2022.1.13 BETA release, you must also install the Indicium 2022.1.15 release.This also fixes a known issue:Subjects did not refresh properly after all tasks were executed when executing a task on multiple rows with the Popup for each row setting enabled.Fields layout in forms now use Software Factory settingsForms in the Universal GUI are responsive to the device on which they are displayed. The layout of controls in a form is determined by the available space on the respective device.The form width determines how many columns of fields with their labels are displayed. Within a group, fields are displayed together. A group is created when Field in next group or Field in next tab is set for a column in the Software Factory, via navigation path:menu User interface > Subjects > tab Default > tab Components > tab FormThe number of columns in a form is determined differently as of this version. Previously, a form was split into columns when the width of the field and its label together was more than 300 pixels. As of this version, the subject's settings in the Software Factory are used for this, adding the label width to the field width. These two settings can be set for the entire application at once, or for a specific subject, via navigation path:menu User interface > Subjects > tab Default/Variants > tab Settings > tab GeneralIf this new calculation results in a lower value, more controls can be displayed side by side in different columns. This utilizes the screen space more efficiently.Due to this change, the width at which a new column is displayed by default has been changed from 300 to 335. However, this can make forms appear differently.Especially notice subjects where the value is customized. The Universal GUI will react to the settings from now on. To check, execute this query on your Software Factory/IAM database:SELECT tf.[gui_appl_id] ,a.[transl] ,[tab_id] ,[tab_variant_id] ,[no_of_cols_in_form] ,[form_col_width] FROM [i_ui_tab_form] tf JOIN i_ui_gui_appl a on a.gui_appl_id = tf.gui_appl_idNewMap OverlaysIn the Universal GUI, you can now display overlay layers on top of the base layer of a map to add additional information such as weather or traffic information. You can also toggle an overlay layer on and off. Example of a map with Route info and seaways overlay layerGroup columns in a gridYou can now group columns that are part of the subjects sorting in a grid. This grouping is fixed on one or more columns and must be pre-configured in the Software Factory via navigation path:User Interface > Subjects > Data > SortThe Group until option specifies the last column by which to group. All columns up to and including the column with Group until selected become part of the grouping. In the example below, persons are grouped by country, then by province, and then by city. Group persons by country, province, and cityIn the Universal GUI, the result looks like this: Grouping resultNote: Letting the user dynamically group on columns is a different feature that will be added in the future.Grid column width can be based on headers and dataFor grids, the Universal GUI now supports the Auto column width setting 'Headers and data'. This setting indicates that the column width is automatically determined based on the header and the data. The Auto column width setting does not apply to fixed-size columns. Auto column width setting Headers and dataSee also: auto column width.ChangedSize of task bar icons can be setIn the previous sprint, we introduced the positioning of task bars across the entire subject by dragging a Task bar component onto a screen type. Now, you can specify the size of the task bar icons in the Software Factory. Screen type with task bar and Icon size propertyIn the Software Factory, you can choose from 7 possible icon sizes (in pixels). In the Universal GUI, these sizes are translated into 3 possible values, according to the following table:Icon size in Software Factory Icon size in Universal GUI Button size Compact mode Button size Comfortable mode 16*16, 20*20 20*20 32*32 40*40 24*24 28*28 40*40 48*48 32*32, 40*40, 48*48, 64*64 36*36 44*44 56*56 The icon size is also affected by the Compact or Comfortable mode setting. In compact mode, less padding is applied. More padding is applied in the comfortable mode.The icon size set for task bar icons also applies to icons in the action bar at the top. This has made these icons a little more compact.Example: A task bar with small icons and a task bar with large iconsMinor fixes and tasksWhen a user tried to perform some activity after a user session expired, a popup message notified the user to sign in again. For example, when opening the documents tab. However, if the user tried to switch to a different application after their session expired, the application would stop responding. Now, a popup message appears. Conditional layouts with the condition Contains or Does not contain were not visible. Now, they are. A toolbar containing items, such as prefilters, can be displayed in the form of a uniquely colored icon representing the first letter of the item's name. However, in an overflow or dropdown menu, the color of these icons would be identical and non-unique. This has been fixed. When using the Preview component, unknown file types were unnecessarily downloaded. This has been fixed. Now, a message is displayed: The file cannot be previewed. The Start report process action did not receive any output parameters from the process flow. This has been fixed. Warning messages without message options contained an OK button. This button label text now reads CLOSE. When a default procedure was started, file type fields were not emptied. This has been fixed. When entering a search condition and exiting the search field before the search was completed, the value in the search field was temporarily reset to its previous value (or empty). This has been fixed. The data mapping column of a Maps component only accepted the VARCHAR data type. For an INT data type, no markers were visible. This has been fixed. Also, when the id and the data value of the domain elements differ, the marker is now displayed. Background: In the Maps component, a column with domain elements specifies the type of the object displayed on the map (for example, a marker or polygon). These elements map to the entity_type column of the record of the underlying subject. In a cube field, group intervals such as Year, Quarter, Month, or Week could only be used with charts, not pivot tables. Now, you can use group intervals also in pivot tables. After navigating to the next record, in some cases, multiple records were selected. This has been fixed. When searching a multi-page grid on a detail subject, no result was returned if it was not visible on the current page. This has been fixed.What we will be working on next sprintThe next sprint we will be working on:Pivot grid enhancements - Calculations on grouped data, for example, the average value. Splitter position user preference - This will save all the splitter positions to the user device. Compact mode grid density - This will make the grid height more dense in compact mode. Allow users to open a subject twice through Ctrl-clicking - When Ctrl-clicking a subject in the menu, this subject will be opened a second time as an open document. When double-clicking a detail tab page, this tab page will be opened as a new document. Switching between menus - This enables the user to switch between menus from the application when there are multiple menus. 

Related products:Universal GUI

Release notes Thinkwise Deployment Center (2.2.0)

Hello everyone,In this release, we have added:Support for deploying the Thinkwise Upcycler. A separate deployment option for synchronizing the meta model of an application into IAM without installing or upgrading the database. A settings file for the Deployment Center's GUI in which you can store some default values for various screens during startup.We have also improved working with the Manifest.Download the Thinkwise Deployment Center 2.2.0 here. ContentsNew Support for deploying the Thinkwise Upcycler (GUI and CLI) Application model synchronization as a separate deployment option (GUI and CLI) Skip synchronizing the application model into IAM (GUI and CLI) Settings file for the Deployment Center's GUI Manifest - Specifying a directory path in a supportedVersion Manifest - Override the fallback encoding of script files Changed IP validation for bindings when creating a new site (GUI) Next New Support for deploying the Thinkwise Upcycler (GUI and CLI)It is now possible to deploy the Thinkwise Upcycler with the Deployment Center.Deploying the Thinkwise Upcycler through the GUI or CLI is similar to the Thinkwise Software Factory.Deploy the Upcycler through the GUITo deploy the Upcycler through the CLI:twdeployer.exe upcycler auto -m ".../Manifest.json" -s ".\sqlserver" -n "THINKWISE_UPCYCLER" --iam-name "THINKWISE_IAM"twdeployer.exe upcycler install -m ".../Manifest.json" -s ".\sqlserver" -n "THINKWISE_UPCYCLER" --iam-name "THINKWISE_IAM"twdeployer.exe upcycler upgrade -m ".../Manifest.json" -s ".\sqlserver" -n "THINKWISE_UPCYCLER" --iam-name "THINKWISE_IAM"twdeployer.exe upcycler hotfix -m ".../Manifest.json" -s ".\sqlserver" -n "THINKWISE_UPCYCLER" Application model synchronization as a separate deployment option (GUI and CLI)We have added a separate deployment option for synchronizing the meta model of an application into IAM without installing or upgrading the database.Currently, this is available for deployment packages generated by the Software Factory if the Deployment Center detects a 'MetaModel' folder on the same directory level as an 'Install' or 'Upgrade' package.The synchronization deployment for the Software Factory and Upcycler requires the name of a matching database due to their post-synchronization scripts. These products use the database name, for example, to create an application record inside the target IAM. For applications other than the Software Factory and Upcycler, providing a database name is optional since the Deployment Center cannot detect if the post-synchronization scripts use it.We are still looking into extending the manifest specification to make the model synchronization a separate package type with options to specify parameters included in the post-synchronization scripts.Synchronizing the meta model through the GUITo synchronize the meta model in the CLI:twdeployer.exe iam sync-model -m ".../Manifest.json" -s ".\sqlserver" -n "THINKWISE_IAM"twdeployer.exe sf/upcycler/app sync-model -m ".../Manifest.json" -s ".\sqlserver" --iam-name "THINKWISE_IAM" --db-name "THINKWISE_SF/UPCYCLER" Skip synchronizing the application model into IAM (GUI and CLI)You can now skip the synchronization of the application model during the installation or upgrade of a Software Factory, Upcycler, or customer app. This can be useful when a single IAM has been configured with multiple instances of the same application on different servers.In the GUI, you can skip the synchronization step by clearing the Import application model checkbox on the new Synchronization options screen:Clear the Import application model checkbox to skip synchronizationIn the CLI, the auto, install, and upgrade commands for the Software Factory (sf), Upcycler (upcycler), and app (app) have been updated with a --skip-model-sync switch:twdeployer sf/upcycler/app auto/install/upgrade ... --skip-model-syncNote that the --iam-name option is no longer required if --skip-model-sync is used. Settings file for the Deployment Center's GUIWe have added a settings file for the Deployment Center's GUI that you can use to store some default values for various screens during startup.The default template is:{ "DbConnection": { "Host": "", "Username": "" }, "IISApi": { "ServerUrl": "https://localhost:55539", "ApiKey": "", "Username": "", "TrustInvalidSSLCert": false }, "Manifest": { "SelectionDirectory": "", "LoadOnStartup": [ ], "HideLoadAfterLoadOnStartup": true }}DbConnection - use this section to specify a default Host and Username when making a connection to a database server, for example, when starting an install or upgrade flow. If Username is empty or otherwise unspecified, the GUI assumes you want to use Integrated Security instead. After a successful connection to a database server, the GUI will continue to load the information of the last successful connection for subsequent screens, like in previous releases.  { "DbConnection": { "Host": ".\\sql2019", "Username": "sa" }}Result of DbConnection settings in the GUIIISApi - Use this section to specify default connection settings to a Microsoft IIS Administration API instance.{ "IISApi": { "ServerUrl": "https://localhost:55539", "ApiKey": "not a real key just an example", "Username": "tsf\\thisisausername", "TrustInvalidSSLCert": true }} Result of IISApi settings in the GUIManifest - Use this section to indicate how manifests are loaded by the GUI at startup. LoadOnStartup - Use this section to specify multiple manifest files to load during startup. When you leave this unspecified or empty, the GUI will default look for a Manifest.json/yaml/yml file in the executable's directory. Paths are relative to the location of the executable. So, if you also want to load the default manifest locations, you must add them as well. For example: { "Manifest": { "LoadOnStartup": [ "Manifest.json", "C:\\Manifests\\Manifest_2021_2.json", "C:\\Manifests\\Manifest_2021_3.json", "C:\\Manifests\\Manifest_2022_1.json" ] }}Result of Manifest settings in the GUIHideLoadAfterLoadOnStartup - By default, the GUI hides the separate manifest loading and selection screens if a manifest is loaded during startup. You can now change this behavior by setting it to false.{ "Manifest": { "LoadOnStartup": [ "C:\\Manifests\\Manifest_2022_1.json" ], "HideLoadAfterLoadOnStartup": false }}The separate manifest loading and selection screens are no longer hiddenSelectionDirectory - Use this setting to change the file picker on the Load Manifest screen, to always try and open in the specified directory. If the directory does not exist or cannot be found, the file picker control will fall back on the default Windows behavior. In that case, it tries to open the last directory from which a user has selected a file. The directory path must be specified using Windows style path separators (backslash). Since the settings file uses JSON, this means you always need to escape it. So, use: C:\\Manifests instead of C:/Manifests or C:\Manifests \\\\unc_share\\directory instead of \\unc_share\directory { "Manifest": { "SelectionDirectory": "C:\\Manifests" }}File picker opens in specified directory Manifest - Specifying a directory path in a supportedVersionWhen the Deployment Center was first made, the the Software Factory and IAM upgrade scripts were released with all generated scripts concatenated into one. This was more convenient because the install and upgrade scripts had to be run manually through, for example, SQL Server Management Studio. And sometimes, a separate pre-upgrade script had to be run before an upgrade.There was no real pattern for naming these scripts. Therefore, we made a decision in the design of the deployment manifest to specify the path to each script for each supportedVersion in an upgrade package, using the files property.Then, since the 2018.3 Thinkwise Platform release, we decided to skip the concatenating step and release the generated scripts as-is. That did not really change anything for the manifest since files could still be specified as always:schema: 2products: - type: "IAM" version: "2022.1" projectFolder: "T:\\Product Innovation\\Applications" dependencies: - "CompatibilityLevel140" packages: - type: "Upgrade" path: "IAM/Upgrade" supportedVersions: - version: "2021.3" upgradesTo: "2022.1" files: - "2022.1\\020_Upgrade.sql" - "2022.1\\030_Checks.sql" - "2022.1\\040_Constraints.sql" - "2022.1\\050_Indexes.sql" - "2022.1\\060_Functions.sql" - "2022.1\\065_Table_valued_functions.sql" - "2022.1\\070_Views.sql" - "2022.1\\080_Procedures.sql" - "2022.1\\090_Instead_of_triggers.sql" - "2022.1\\100_Triggers.sql" - "2022.1\\110_Tasks.sql" - "2022.1\\120_Defaults.sql" - "2022.1\\130_Layouts.sql" - "2022.1\\140_Contexts.sql" - "2022.1\\145_Badges.sql" - "2022.1\\150_Processes.sql" - "2022.1\\999_Apply_roles_on_database.sql" - "2022.1\\999_Manual.sql"It did, however, cause the manifest to grow larger and larger with each consecutive platform release since each supported upgrade version added about 12-17 script files.To reduce that amount, you can now use a path property to specify the directory containing the upgrade scripts:schema: 2products: - type: "IAM" version: "2022.1" projectFolder: "T:\\Product Innovation\\Applications" dependencies: - "CompatibilityLevel140" packages: - type: "Upgrade" path: "IAM/Upgrade" supportedVersions: - version: "2021.3" upgradesTo: "2022.1" path: "2022.1"Some rules apply when you use the path property for a supportedVersion:Only the immediate directory is scanned for .sql files. Subdirectories will be skipped. All .sql files inside the specified directory must adhere to the <order/sequence number>_<code file name>.sql format the Software Factory uses to generate the code files. The path of a supportedVersion is relative to the path of the upgrade package, which in turn is relative to the location of the manifest file. Using the manifest above as an example: If the manifest file is located at "C:\Manifests", the path of the upgrade package resolves to "C:\Manifests\IAM\Upgrade", and the path of the 2021.3 -> 2022.1 supportedVersion resolves to "C:\Manifests\IAM\Upgrade\2022.1".  Manifest - Override the fallback encoding of script filesDue to technical reasons, the Deployment Center has always assumed that the default encoding of script files generated by the Software Factory is windows-1252.However, the script generation process has been changed in platform release 2021.3. Since it is now run by Indicium, these reasons no longer apply.Therefore, the V2 specification of the manifest file has been extended to allow overriding the encoding for script files. This is a backward-compatible way to change the encoding of the generated scripts in a future platform release.The encoding property can be set at the following levels inside an IAM, Software Factory, Upcycler, or application type product:Product level. Package level. supportedVersion level inside an upgrade package.To maintain backward compatibility with previously generated manifests using the V2 specification, the default value of the encoding property is still windows-1252.Meaning that the following manifest: schema: 2products: - type: "IAM" version: "2022.1" projectFolder: "T:\\Product Innovation\\Applications" dependencies: - "CompatibilityLevel140" packages: - type: "Install" path: "IAM/Install" - type: "Upgrade" path: "IAM/Upgrade" supportedVersions: - version: "2021.2" upgradesTo: "2021.3" path: "2021.3" - version: "2021.3" upgradesTo: "2022.1" path: "2022.1" - type: "Hotfix" path: "IAM/Hotfixes"is interpreted by the Deployment Center as:schema: 2products: - type: "IAM" version: "2022.1" projectFolder: "T:\\Product Innovation\\Applications" dependencies: - "CompatibilityLevel140" encoding: "windows-1252" packages: - type: "Install" path: "IAM/Install" encoding: "windows-1252" - type: "Upgrade" path: "IAM/Upgrade" encoding: "windows-1252" supportedVersions: - version: "2021.2" upgradesTo: "2021.3" path: "2021.3" encoding: "windows-1252" - version: "2021.3" upgradesTo: "2022.1" path: "2022.1" encoding: "windows-1252" - type: "Hotfix" path: "IAM/Hotfixes" encoding: "windows-1252"When the encoding is changed at higher levels, the Deployment Center will also use that encoding at lower levels or until it encounters another override value.Notes:Because the meta model import is not a separate package type inside manifests using schema V2, it currently assumes the same encoding as the install or upgrade package, depending on which was used to detect the presence of the import scripts (usually the install package). encoding specifies the fallback encoding it should use if it does not detect a BOM. This means that technically you could mix file encodings in a package as long as encoding with a defined BOM is used. But if possible, it is still best to use a single encoding.Examples:Change the default script encoding for the entire product to UTF-8:schema: 2products: - type: "IAM" version: "2022.1" projectFolder: "T:\\Product Innovation\\Applications" dependencies: - "CompatibilityLevel140" encoding: "utf-8" packages: - type: "Install" path: "IAM/Install" - type: "Upgrade" path: "IAM/Upgrade" supportedVersions: - version: "2021.2" upgradesTo: "2021.3" path: "2021.3" - version: "2021.3" upgradesTo: "2022.1" path: "2022.1" - type: "Hotfix" path: "IAM/Hotfixes"Manifest as interpreted by the Deployment Center:schema: 2products: - type: "IAM" version: "2022.1" projectFolder: "T:\\Product Innovation\\Applications" dependencies: - "CompatibilityLevel140" encoding: "utf-8" packages: - type: "Install" path: "IAM/Install" encoding: "utf-8" - type: "Upgrade" path: "IAM/Upgrade" encoding: "utf-8" supportedVersions: - version: "2021.2" upgradesTo: "2021.3" path: "2021.3" encoding: "utf-8" - version: "2021.3" upgradesTo: "2022.1" path: "2022.1" encoding: "utf-8" - type: "Hotfix" path: "IAM/Hotfixes" encoding: "utf-8"Change the default encoding of the product to UTF-8 but leave the upgrade package at Windows-1252:schema: 2products: - type: "IAM" version: "2022.1" projectFolder: "T:\\Product Innovation\\Applications" dependencies: - "CompatibilityLevel140" encoding: "utf-8" packages: - type: "Install" path: "IAM/Install" - type: "Upgrade" path: "IAM/Upgrade" encoding: "windows-1252" supportedVersions: - version: "2021.2" upgradesTo: "2021.3" path: "2021.3" - version: "2021.3" upgradesTo: "2022.1" path: "2022.1" - type: "Hotfix" path: "IAM/Hotfixes"Manifest as interpreted by the Deployment Center:schema: 2products: - type: "IAM" version: "2022.1" projectFolder: "T:\\Product Innovation\\Applications" dependencies: - "CompatibilityLevel140" encoding: "utf-8" packages: - type: "Install" path: "IAM/Install" encoding: "utf-8" - type: "Upgrade" path: "IAM/Upgrade" encoding: "windows-1252" supportedVersions: - version: "2021.2" upgradesTo: "2021.3" path: "2021.3" encoding: "windows-1252" - version: "2021.3" upgradesTo: "2022.1" path: "2022.1" encoding: "windows-1252" - type: "Hotfix" path: "IAM/Hotfixes" encoding: "utf-8"Change the default encoding of the product to UTF-8 but leave the supportedVersion upgrade for 2021.2 to 2021.3 at Windows-1252:schema: 2products: - type: "IAM" version: "2022.1" projectFolder: "T:\\Product Innovation\\Applications" dependencies: - "CompatibilityLevel140" encoding: "utf-8" packages: - type: "Install" path: "IAM/Install" - type: "Upgrade" path: "IAM/Upgrade" supportedVersions: - version: "2021.2" upgradesTo: "2021.3" path: "2021.3" encoding: "windows-1252" - version: "2021.3" upgradesTo: "2022.1" path: "2022.1" - type: "Hotfix" path: "IAM/Hotfixes" Manifest as interpreted by the Deployment Center:schema: 2products: - type: "IAM" version: "2022.1" projectFolder: "T:\\Product Innovation\\Applications" dependencies: - "CompatibilityLevel140" encoding: "utf-8" packages: - type: "Install" path: "IAM/Install" encoding: "utf-8" - type: "Upgrade" path: "IAM/Upgrade" encoding: "utf-8" supportedVersions: - version: "2021.2" upgradesTo: "2021.3" path: "2021.3" encoding: "windows-1252" - version: "2021.3" upgradesTo: "2022.1" path: "2022.1" encoding: "utf-8" - type: "Hotfix" path: "IAM/Hotfixes" encoding: "utf-8"Change the default encoding of the product to UTF-8, leave the upgrade package at Windows-1252 but use UTF-8 again for the 2021.3 to 2022.1 supportedVersion upgrade: schema: 2products: - type: "IAM" version: "2022.1" projectFolder: "T:\\Product Innovation\\Applications" dependencies: - "CompatibilityLevel140" encoding: "utf-8" packages: - type: "Install" path: "IAM/Install" - type: "Upgrade" path: "IAM/Upgrade" encoding: "windows-1252" supportedVersions: - version: "2021.2" upgradesTo: "2021.3" path: "2021.3" - version: "2021.3" upgradesTo: "2022.1" path: "2022.1" encoding: "utf-8" - type: "Hotfix" path: "IAM/Hotfixes"Manifest as interpreted by the Deployment Center:schema: 2products: - type: "IAM" version: "2022.1" projectFolder: "T:\\Product Innovation\\Applications" dependencies: - "CompatibilityLevel140" encoding: "utf-8" packages: - type: "Install" path: "IAM/Install" encoding: "utf-8" - type: "Upgrade" path: "IAM/Upgrade" encoding: "windows-1252" supportedVersions: - version: "2021.2" upgradesTo: "2021.3" path: "2021.3" encoding: "windows-1252" - version: "2021.3" upgradesTo: "2022.1" path: "2022.1" encoding: "utf-8" - type: "Hotfix" path: "IAM/Hotfixes" encoding: "utf-8" Changed IP validation for bindings when creating a new site (GUI)In the GUI, the Next button will no longer be enabled when you enter an invalid IP address.No IP address (bind to all IP addresses), Next is enabled: Valid IP input, Next is enabled:IP not parsable, Next is disabled: NextFor future releases, we are still working on:Move Deployer CLI to .NET 6. Check access rights on the target directory when installing Indicium to a local IIS. A UI-assisted meta source selection for simple configuration modes during Indicium and Windows GUI flowsWould like to have:A simple configuration mode for Windows GUI flows to make it easier to get a basic installation up and running.

Related products:Deployment Center

Release notes Universal GUI (2022.1.12)

March 11, 2022:Changed¬†beta release¬†to the full version: 2022.1.12 Hotfixes for issues¬†found¬†in the previous beta release: When editing in a grid, the checkboxes in the selected record were not aligned identically as in the other rows.¬†This has been fixed. For checkboxes, the asterisk that indicates a mandatory field was displayed too high.¬†This has been fixed. In a grid, conditional layouts did not work until clicking a row.¬†This has been fixed. When clicking a splitter, user interface elements stopped responding until dragging the splitter. This has been fixed. Grid headers were misaligned, and the sort icons were not displayed correctly.¬†This has been fixed. When hovering over a grid, the color used for fixed columns was slightly different than for non-fixed columns.¬†This has been fixed. The task bar component could disappear from the corresponding subject, especially when displayed directly below the default action bar of the subject. The task buttons in the default action bar could also disappear when the taskbar was placed elsewhere in the subject. This has been fixed. Note that within tabs that are located at the top of the subject, tasks may still pop up in these cases. We will improve this later on. ¬†Hello everyone,In this sprint, we made it possible to (re)position task buttons across the entire subject screen type by dragging a¬†Task bar¬†component to a screen type. Also, the filter form now uses the (default)¬†Filter condition¬†settings from the Software Factory. More new functionality and improvements are listed below.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.¬†Universal GUI version 2022.1.12Do 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 an allowed origin in¬†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 2022.1.12¬†here¬†¬†Contents of this releaseUniversal GUI version 2022.1.12 New Task bar as screen component Grouping fields in a grid and show a group label‚Äč Looking ahead in the resource scheduler Changed Filter form conditions Minor fixes and tasks What we will be working on next sprintNewTask bar as screen componentYou can now (re)position task buttons across the entire subject screen type by dragging a¬†Task bar¬†component to a screen type. The task buttons then disappear from the standard action bar at the top.menu User interface > Screen types > tab DesignThere are some considerations to keep in mind:A task bar must be placed horizontally. Vertical task bars are not displayed yet. Buttons are not sizable yet.Grouping fields in a grid and show a group label‚ÄčIn a grid, you can group fields that logically belong together by checking the¬†Next group¬†option for the first field in the group. You can now also provide a¬†Group label. This label appears as a group header in the grid.menu User interface > Subjects > tab Default > tab Components > tab GridFor example, see the group labels¬†IAM root administration¬†and¬†Tenant self-administration¬†group labels on the¬†Tenants¬†page:¬†Example: Tenants page with group labelsLooking ahead in the resource schedulerIn the resource scheduler, you can now look ahead for a specified period. This allows users to view year-end appointments. The scheduler appears on the current date.This period can be configured by setting the new (global) extended property¬†SchedulerPeriodInYears to the number of years to look ahead. ¬†Note that displaying many appointments in the future may decrease the performance.ChangedFilter form conditionsThe filter form now uses the (default)¬†Filter condition¬†settings from the Software Factory. These settings can be specified for several control types at the application and project version levels and also for a specific column in a subject:Application level: menu User interface > Subjects > tab Default settings > Filter area¬†Default filter condition settingsSpecific column:¬†menu User interface > Subjects > tab Subjects > tab Default > tab Data > tab Filter¬†Column-specific filter condition settingsMore specific column filters override the default condition. For example, when the default condition is set to¬†Contains¬†and the user performs a quick filter on a column value (Equal to), the filter control temporarily changes to¬†Equal to¬†as long as the quick filter is active.Previously, you could only use the¬†Equal to¬†condition. As of this version, you can use the following filter conditions:(not) Equal to Contains Starts with Ends with Greater than (or equal to) Smaller than (or equal to)The following filter conditions are not supported (yet):(not) Between Does not contain Is (not) null Does not start with Does not end¬†with¬†Examples of filter form conditionsMinor fixes and tasksWhen a screen contained more than one snackbar, the timer did not start counting down until the previous snackbar was closed. This has been fixed. Now, the timer starts counting down immediately and closes at the end of the set period. When making a new appointment in the resource scheduler, other appointments were not visible. This has been fixed. When opening a screen containing a map, the default activated base layer differed from the layer shown in the Windows and Web GUI. This has been changed. The default behavior is now the same in all GUIs. The selected base layer is also preserved when switching open documents or tabs. If a column contained a lookup value 0 (zero), it was not visible in edit mode even though it would be saved and presented correctly in preview mode. This has been fixed. When exporting data spread over several pages in a grid or list to Excel, an incorrect number of records (the number of rows on a single page) was displayed on the toolbar button. This has been fixed. When a column was changed to mandatory using a layout, combo boxes in a grid contained an empty option. This has been fixed. When tabbing from one field to another, for example, from¬†field1¬†to¬†field2¬†in the default procedure below, the Universal GUI would wrongly focus¬†field2¬†after closing the message popup, even though¬†cursor_to_col_id¬†specifies that the focus should go back to¬†field1. This has been fixed.exec tsf_send_message 'wrong_value_in_field1', null, 0set @cursor_to_col_id = 'field1'In the Preview component, images could contain a horizontal scrollbar. This has been fixed (images have a maximum of 100% width). When changing the value of a Datetime column and immediately focusing on another Datetime column, defaults, layouts, and contexts were not executed. In a map component, the settings to change the border width and border opacity of a polygon were ignored, and the default Universal GUI values were displayed instead. Now, these border settings are used. When using the process action¬†Go to row¬†to navigate to another record not shown on the current page, this record was not always selected and not scrolled to. This has been fixed.What we will be working on next sprintThe next sprint we will be working on:Grid attribute grouping¬†- Apply the group until settings from the model to the entire dataset of the subject and show the grouping columns on the grid. Taskbar screen component icon sizes¬†- Allows for modeling of three different icons with sizes small, medium, and large for the task bar screen component. Maps overlays¬†- Overlay maps with specialist tile layers, like weather, wind, environmental zones. In progress: Technical design for storing local user preferences.

Related products:Universal GUI

Release notes Windows GUI and Web GUI (2022.1.13)

Hello everyone,In this sprint, we replaced the integrated browser component used for previewing web content, Indicium (Legacy) now supports the Concurrent access (Claims) feature, and we solved an issue.You can read more about the Windows and Web GUI's features, in the GUI user manual. We will keep you updated regularly about the Windows and Web GUI's progress.Download Windows GUI 2022.1.13 here. Download Web GUI 2022.1.13 here. BreakingNew web browser component for previewing(Windows GUI) The integrated browser component used for previewing web content has been replaced. Instead of the full CefSharp browser (270 MB in size), the Windows GUI now ships with the Microsoft Edge Webview2 installer that installs the browser component if not already available. The installation does not require administrator privileges.In addition to the smaller size of the Windows GUI, this also ensures the security of the browser component, as Windows takes care of keeping the browser component up-to-date.Installing Microsoft Edge Webview2 RuntimeNewIndicium (Legacy) supports the Concurrent access (Claims) feature(Windows GUI) To use the Concurrent access (Claims) feature via Indicium (Legacy), you need to install the latest Software Factory and IAM hotfixes (Platform improvements).Concurrent access delimits the number of concurrent users that can log into an application simultaneously.For more information on the Concurrent access settings, please refer to the corresponding IAM documentation.Support for additional OAuth2 prompt optionsThe Windows GUI now supports the new OAuth2 prompt options. These options were originally added in IAM hotfix 20220216.The available OAuth2 prompt options have been made editable and have been expanded with the prompt options login, select account, and none.Minor fixes and tasks(Windows GUI and Web GUI) When a primary key column had data type VARBINARY, an incorrect row was selected after data refresh. This has been fixed.

Related products:Web and Windows GUI

Release notes Indicium (2022.1.13)

Hello everyone,In this sprint, we added various performance metrics for requests using Server-Timing response headers. We also added the Agent ID to the Indicium landing page, and Indicium now automatically retries when encountering a database connection failure on startup.You can read more about Indicium's features in the Indicium user manual.We will keep you updated regularly about Indicium's progress.Download Indicium Universal release 2022.1.13 here.Contents of this releaseBreaking Changes Thinkwise Platform support release 2020.1 ends Indicium Universal Measuring Server-Timing responses Retry start-up on connection failure Agent ID on the Indicium landing page Language of translated messages by application connector Messages filtered out in log files Minor fixes and tasks Breaking ChangesThinkwise Platform support release 2020.1 endsIndicium support for Thinkwise Platform release 2020.1 is ending. Please upgrade to at least release 2020.2 to use this release of Indicium. Indicium UniversalMeasuring Server-Timing responsesIn this release of Indicium Universal, we have added various performance metrics for requests using Server-Timing response headers. Browser developer tools can interpret these headers and visualize these performance metrics. The goal of these features is to give more detailed insight into performance and help solve potential performance issues, which are almost always caused by specific queries, layout procedures, file storage operations, etc. that can be optimized fairly easily. We have already added dozens of these performance metrics, which are listed below, and we are looking into adding more of them in the future.CRUD operationsAll SELECT queries for requested subjects of an application (tables and views). When the $count operation requests the total number of records, this will be measured and returned separately. When the $expand operation joins a lookup or a detail subject, these will each be measured and returned separately. Insert statements. Update statements. Delete statements. Expression queries while adding or editing a record. Default value queries when entering edit mode to add a new record or start a task or report. Lookup validations when changing a lookup value or a lookup filter value.Application logicTasks Subroutines Default procedures. Layout procedures. Context procedures. Badge procedures. Change detection procedures (the new logic concept).File storageFetching the database record for a file to be downloaded. Calculating the hash of a file. File access (this can be considered as obtaining a file connection, but does not include the entire download process). Writing files (this does include the entire upload process).MiscellaneousFetching records by primary key. This is, for instance, done when starting a task in the context of a record. This record will first need to be fetched. Loading the application model. After restarting Indicium or changing the application model, the model needs to be loaded, which may take multiple seconds on top of the request performed.Once you have installed this version of Indicium Universal, you can see these metrics under Server timings in your browser's developer tools.Some examples (partially in Dutch) are shown below.The first request to an applicationAfter changing a column value - 1After changing a column value - 2Downloading a file Examples of Servertiming metricsRetry start-up on connection failureWhen Indicium encountered a database connection failure during start-up, it would not automatically retry. As of this version of Indicium, a retry occurs every two minutes for up to 10 minutes. The cause of the connection failure could be a temporary issue with the database server or network that resolves itself.Agent ID on the Indicium landing pageIndicium's landing page will now show the Agent ID of the Indicium instance. This Agent ID corresponds to the IDs that you will find on the 'Agent check in' screen in IAM's advanced menu. It can help you troubleshoot issues regarding system flows. You can also use the Agent ID to test if your load balancer's sticky sessions configuration is working by refreshing the landing page a few times and checking whether the Agent ID stays the same.Indicium Landing page with Agent ID Language of translated messages by application connectorIf a tsf_send_message procedure sends a message to the application connector, the message is now translated into the language of the user who initiated the process flow.If the application connector is called from a system flow, then the message is translated into the application fallback language.Messages filtered out in log filesThe following messages are now filtered out in the log files because they often occur and can quickly fill the log files, making them difficult to search for errors:schedule_not_found system_flow_already_running system_flow_still_runningMinor fixes and tasks In the database event log, SQL queries and messages did not contain newline characters, which made the statements poorly readable and could cause problems with single-line comments. This has been fixed.  Example of a SQL query with newlines 

Related products:Indicium Service Tier

Release notes Universal GUI (2022.1.12 BETA)

Hello everyone,In this sprint, we made it possible to (re)position task buttons across the entire subject screen type by dragging a¬†Task bar¬†component to a screen type. Also, the filter form now uses the (default)¬†Filter condition¬†settings from the Software Factory. More new functionality and improvements are listed below.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.¬†Universal GUI version 2022.1.12 BETADo 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 an allowed origin in¬†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 2022.1.12 BETA here¬†This is a beta release, which can be used to test the new features. This release is not suitable for use in a production environment. The full release will be available this Friday.¬†Contents of this releaseUniversal GUI version 2022.1.12 BETA New Task bar as screen component Grouping fields in a grid and show a group label‚Äč Looking ahead in the resource scheduler Changed Filter form conditions Minor fixes and tasks What we will be working on next sprintNewTask bar as screen componentYou can now (re)position task buttons across the entire subject screen type by dragging a¬†Task bar¬†component to a screen type. The task buttons then disappear from the standard action bar at the top.menu User interface > Screen types > tab DesignThere are some considerations to keep in mind:A task bar must be placed horizontally. Vertical task bars are not displayed yet. Buttons are not sizable yet.Grouping fields in a grid and show a group label‚ÄčIn a grid, you can group fields that logically belong together by checking the¬†Next group¬†option for the first field in the group. You can now also provide a¬†Group label. This label appears as a group header in the grid.menu User interface > Subjects > tab Default > tab Components > tab GridFor example, see the group labels¬†IAM root administration¬†and¬†Tenant self-administration¬†group labels on the¬†Tenants¬†page:¬†Example: Tenants page with group labelsLooking ahead in the resource schedulerIn the resource scheduler, you can now look ahead for a specified period. This allows users to view year-end appointments. The scheduler appears on the current date.This period can be configured by setting the new (global) extended property¬†SchedulerPeriodInYears to the number of years to look ahead. ¬†Note that displaying many appointments in the future may decrease the performance.ChangedFilter form conditionsThe filter form now uses the (default)¬†Filter condition¬†settings from the Software Factory. These settings can be specified for several control types at the application and project version levels and also for a specific column in a subject:Application level: menu User interface > Subjects > tab Default settings > Filter area¬†Default filter condition settingsSpecific column:¬†menu User interface > Subjects > tab Subjects > tab Default > tab Data > tab Filter¬†Column-specific filter condition settingsMore specific column filters override the default condition. For example, when the default condition is set to¬†Contains¬†and the user performs a quick filter on a column value (Equal to), the filter control temporarily changes to¬†Equal to¬†as long as the quick filter is active.Previously, you could only use the¬†Equal to¬†condition. As of this version, you can use the following filter conditions:(not) Equal to Contains Starts with Ends with Greater than (or equal to) Smaller than (or equal to)The following filter conditions are not supported (yet):(not) Between Does not contain Is (not) null Does not start with Does not end¬†with¬†Examples of filter form conditionsMinor fixes and tasksWhen a screen contained more than one snackbar, the timer did not start counting down until the previous snackbar was closed. This has been fixed. Now, the timer starts counting down immediately and closes at the end of the set period. When making a new appointment in the resource scheduler, other appointments were not visible. This has been fixed. When opening a screen containing a map, the default activated base layer differed from the layer shown in the Windows and Web GUI. This has been changed. The default behavior is now the same in all GUIs. The selected base layer is also preserved when switching open documents or tabs. If a column contained a lookup value 0 (zero), it was not visible in edit mode even though it would be saved and presented correctly in preview mode. This has been fixed. When exporting data spread over several pages in a grid or list to Excel, an incorrect number of records (the number of rows on a single page) was displayed on the toolbar button. This has been fixed. When a column was changed to mandatory using a layout, combo boxes in a grid contained an empty option. This has been fixed. When tabbing from one field to another, for example, from¬†field1¬†to¬†field2¬†in the default procedure below, the Universal GUI would wrongly focus¬†field2¬†after closing the message popup, even though¬†cursor_to_col_id¬†specifies that the focus should go back to¬†field1. This has been fixed.exec tsf_send_message 'wrong_value_in_field1', null, 0set @cursor_to_col_id = 'field1'In the Preview component, images could contain a horizontal scrollbar. This has been fixed (images have a maximum of 100% width). When changing the value of a Datetime column and immediately focusing on another Datetime column, defaults, layouts, and contexts were not executed. In a map component, the settings to change the border width and border opacity of a polygon were ignored, and the default Universal GUI values were displayed instead. Now, these border settings are used. When using the process action¬†Go to row¬†to navigate to another record not shown on the current page, this record was not always selected and not scrolled to. This has been fixed.What we will be working on next sprintThe next sprint we will be working on:Grid attribute grouping¬†- Apply the group until settings from the model to the entire dataset of the subject and show the grouping columns on the grid. Taskbar screen component icon sizes¬†- Allows for modeling of three different icons with sizes small, medium, and large for the task bar screen component. Maps overlays¬†- Overlay maps with specialist tile layers, like weather, wind, environmental zones. In progress: Technical design for storing local user preferences.

Related products:Universal GUI