Product Updates

Hello everyone,In this release, we further simplified the product configuration by adding a button for selecting the correct IAM database. To improve working with the Deployment Center GUI, we have added two new default settings. We also fixed some issues with the dependency checks.Download the Thinkwise Deployment Center 2.3.0 here. New and fixed in this releaseNew (GUI) IAM selection dialog in the Indicium and Windows GUI flows Setting: hide the script variables step Setting: default database name as default value Fixed (GUI) Fixed some issues with dependency checks  New (GUI) IAM selection dialog in the Indicium and Windows GUI flowsIn the Deployment Center's GUI, we have added a Select IAM button to the configuration steps in the Indicium flows (Simple mode) and Windows GUI flows. The button opens a dialog where you can connect to a server and host and select an IAM database. This change further simplifies the product configuration.This is an example of the Select IAM button and dialog in the Indicium configuration (Simple mode):A 'Select IAM' button in the Indicium configuration flow (Simple mode)Note that in a Windows GUI configuration flow, you need to re-select the IAM when (re)loading any of the configuration templates:A 'Select IAM' button in the Windows GUI's configuration flow Setting: hide the script variables stepWhen going through the model synchronization flow for an application, you will be prompted for a database name to be used in the post-synchronization section of the script.This value is optional, and since it might not be used in the post-synchronization section, we have added an option to skip this screen in the Deployment Center GUI. You can set this option using the Flow:ModelSync:Application:HideScriptVariablesStep key in the twdeployerGUI.appsettings.json file.{ "Flow": { "ModelSync": { "Application": { "HideScriptVariablesStep": true } } }} Setting: default database name as default valueWe have added a new setting for using the default database name as default value for the model synchronization script variable. The settting is called Flow:ModelSync:UseDefaultDatabaseName and you can add it to the twdeployerGUI.appsettings.json.{ "Flow": { "ModelSync": { "UseDefaultDatabaseName": true } }}When set to true, the Deployment Center GUI will attempt to use the value of the product's defaultDatabaseName property in the manifest. For example, with the following manifest, the GUI will use MY_APP as the default value for <@db_name,,> in the script variables step. This also works in combination with the HideScriptVariablesStep setting as described above.{ //... "products": [ { "type": "Application", //... "packages": [ { "type": "Install", "path": ".../MY_APP/Install", "defaultDatabaseName": "MY_APP" } ] } ]} Fixed (GUI) Fixed some issues with dependency checksPreviously, the Deployment Center GUI only checked dependencies, such as the compatibility level of the targeted database or server, once per flow execution. So if, for example, the specified compatibility level had not been met, you needed to restart the flow after fixing the issue.We have improved this process in two ways:We have added a Refresh button to the screen for each specified database dependency in the manifest. The dependencies will now be re-checked when switching server or targeted database in one of the previous flow steps.A 'Refresh' button in the Dependency Check 

Hello everyone!We’ve released the following platform improvements this week: IAM 2022.120220627 - Prevent duplicate preview entries when multiple gui applications When multiple GUI applications exist for the same project/project version, this could lead to double rows in the 'Scheduled runs' (preview) tab in the IAM 'Scheduled system flows' screen. This would cause problems in identifying the unique rows in our GUI's. This has now been fixed.

 June 24, 2022:Changed beta release to the full version: 2022.1.17.0 Improvements for issues found in the previous beta release: In right-aligned grid column headers, the asterisk indicating a mandatory field was not visible. This has been fixed. In a grid, group headers were cut off, even if there was enough space. This has been fixed. In a grid, centered column headers jumped to the left when entering edit mode. This has been fixed. When opening a detail tab or switching between parent rows, badges on detail tabs did not refresh instantly but only after the interval period. This has been fixed. When sending an OData request to Indicium, including a primary key value with a date and time, a bad request error occurred. This especially happened when (re)activating a record or saving a newly inserted record that was not in the current set of (pre)filters. This has been fixed. Known issues in this release: During testing, we found that the default editable grid can still behave incorrectly in a detail subject when the entire document is refreshed after changing a record. After changing some values and clicking the next record (which saves the changes), the clicked record may not be activated. We will plan for improvements in this case later.  Hello everyone,In this sprint, we reduced the row height in grids, made grids less flickering while editing, show the numeric keypad on tablets when editing a numeric field, and when adding or editing a row, a document is now marked as 'unsaved'.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.17.0 Do not forget the documentation  and be sure to keep the following in mind:A modern browser is required to access the Universal GUI, e.g., a recent version of Chrome, Firefox, Edge, or Safari mobile. Using the Universal GUI with IE is not supported. The Universal GUI must be deployed on the same server as Indicium or an allowed origin in appsettings.json. This has been fixed. 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.17.0 here  Contents of this releaseUniversal GUI version 2022.1.17.0  Changed Add row and Edit row process actions marked as unsaved Display the numeric keypad on tablets Row height in grids and pivot grids reduced Supported conditional layout conditions Third-party library needed for grids upgraded Minor fixes and tasks What we will be working on next sprintChangedAdd row and Edit row process actions marked as unsavedAs of this version, when performing the actions Add row or Edit row from a process flow, the document is now marked as 'unsaved'. If the user closes this document, they will be prompted to save or cancel the changes.Display the numeric keypad on tabletsOn tablets, the numeric keypad was not visible when editing a numeric field. Now it is.Row height in grids and pivot grids reducedIn compact mode, the row height in grids is reduced from 44px to 36px.The same applies to pivot grids in compact mode and comfortable mode.Supported conditional layout conditionsIn the Universal GUI, the following conditional layout conditions can now also be used:Starts with Does not start with Ends with Does not end with.Third-party library needed for grids upgradedWe upgraded the third-party library needed for grid functionality. This has improved grid performance, made the default editable grid more stable, and made grids less flickering while editing,Also, with this upgrade, the following warning no longer appears in the DevTools Console:"agGrid: getSortModel() is deprecated." Minor fixes and tasks We have fixed many grid alignment issues: The alignment in edit mode versus non-edit mode was different in many cases. This caused the position of fields to change between edit mode and non-edit mode, especially for Combo control values. Right-aligned column headers were left-aligned. Individual cells were not aligned identically with the summary cell. For read-only date, time, and datetime fields in edit mode, the buttons to open a date/time picker were visible while they should be hidden. This has been corrected. When a user was executing a task while a process flow was running, they could get stuck in the running process flow, or spend time filling in task parameters for a task that was not allowed for the selected record. This has been fixed. The task execution now waits for running logic (for example, a stored procedure) to know whether the task execution is allowed or not. When a context procedure was applied when double-clicking a row in a grid, the grid double-click task should wait for the context application logic. However, this was not the case and has been fixed. This is especially important when double-clicking a record that is not selected to decide whether to allow task execution. When opening a subject, the action bar did not always immediately contain the correct buttons, only after switching rows. This has been fixed. In a document that contains unrelated details (for example, two tables with no explicit reference or link to each other), executing a task would refresh the document based on the configurations defined in the Software Factory, except for the unrelated details. Each unrelated detail had to be refreshed manually to reflect the changes. This has been fixed. The whole document is now refreshed when necessary and will show the updated version of each detail. Start objects with a badge did not initially display this badge, only when opened a second time. This has been fixed. When opening a lookup popup a second time, the grid detail tab was opened instead of the form. This has been fixed. When opening a document in one project version from the tiles menu and switching to another project version, the currently open document was reactivated. This has been fixed. Now a new document opens in the correct project version. On tablets, when editing multiple records, the (numeric) values entered for a previous record could temporarily reappear in a later edited record if the same numeric field was empty. This has been fixed. What we will be working on next sprintIn the next sprint, we will be working on: DateTime controls with time zone - This allows DateTime values to always be stored in UTC+0 and displayed to the user in the time zone configured for that user. This will only work in Software Factory platform 2022.2. Vertical tabs - Align your tabs vertically. Variant API - Variants are now more specific in the Indicium API and the Universal GUI will implement this. This will only work in Software Factory platform 2022.2. Make process flow execution more stable - Prevent a process flow from staying active if the user cannot continue the desired steps. Such process flows blocked the execution of subsequent process flows. In progress: Technical research add row in grid.

Hello everyone,In this sprint, we solved some issues.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.19 here. Download Web GUI 2022.1.19 here. Minor fixes and tasks [Windows GUI] When a Claim timeout setting for Indicium (Basic) was set in the Software Factory, and the claim expired, the Windows GUI no longer retrieved the data. This problem has been fixed. As of this version, the Windows GUI attempts to renew the claim for the application when a claim expires. [Windows GUI] When connected via Indicium (basic), the Windows GUI did not terminate the user log sessions correctly, leaving claims active. This has been fixed.

Hello everyone,In this sprint, we changed the message on the logout page to show the user's first and last name, and you can now remove the 'Stay signed in' option on the Indicium login page. 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.20 here. Download Indicium Basic release 2022.1.20 here.Contents of this releaseIndicium Universal Show the user's first and last name when logging out Remove 'Stay signed in' option on login page Indicium UniversalShow the user's first and last name when logging outWhen a user was logged in, the Indicium landing and logout page showed a message like:"You are logged in as: <usr_id>".Since a user ID can be a non-descript GUID or another type of unintelligible identifier, this message has now been changed to:"You are logged in as: <first_name> <last_name>".This message is only visible to a user after logging in. For development and testing purposes, the tooltip still shows the user ID. This allows developers to distinguish between different test users, which could all be named "Test Test".Example of a logout page (fragment)Remove 'Stay signed in' option on login pageYou can remove the 'Stay signed in' option from the Indicium login page by adding the following JSON property to the appsettings.json file."LoginOptions": { "AllowStaySignedIn": false}When the AllowStaySignedIn property (default: true) is set to false, the 'Stay signed in' option is removed. It will also cause the ‘Remember my choice’ option to be removed when there are multiple login options available, for example when OpenID providers are configured.

Hello everyone!We’ve released the following platform improvements this week: SF 2021.1 and up 20220601 - Fixed sorting of icon columns in i_ui menu views Due to the listing of icon columns in the menu item views that the Universal GUI uses to show the menu, it was possible that menu items were showing a different icon than intended. This has been fixed.  SF 2022.120220603 - Fill reachable object tables upon syncing Due to an oversight, reachable objects were not calculated before syncing projects to IAM. This has been fixed.

June 3, 2022:Changed beta release to the full version: 2022.1.16.0 Improvements for issues found in the previous beta release: When a record was edited by a process flow and the subject was closed at the same time, an error message appeared unnecessarily: "Request error: The object was not found. You may have insufficient rights or the object no longer exists" This has been fixed. In the beta release, we improved the style of the task buttons in the toolbar. As a result, the toolbar was not always the correct size, and the task buttons could continuously change size while editing the subject or executing a task. This has been fixed.  Hello everyone,In this sprint, we fixed several issues, and we added two configuration settings to config.json. When searching on a tablet or touchscreen, these settings prevent that after each keystroke, search results are updated immediately. Furthermore, toolbar buttons have been slightly enlarged.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.16.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.16.0 here Contents of this releaseUniversal GUI version 2022.1.16.0 Changed Configurable debounce time Enlarged toolbar buttons Minor fixes and tasks What we will be working on next sprintChangedConfigurable debounce timeWhen you type into the search field, the search starts a moment after each keystroke if no new keystroke occurs. This is called the debounce time. The default value of this debounce time is considered too short when typing on a tablet or touchscreen, resulting in search results being updated after each keystroke.Therefore, this debounce time can now be configured in the config.json file. Also, the default debounce time has been doubled for mobile devices, as typing on a touch keyboard is much slower.New settings for config.json are:searchDebounceTime - in ms, with a default value of 300 ms and a minimum value of 300 ms. searchDebounceTimeMobile - in ms, with a default value of 600 ms and a minimum value of 300 ms.Enlarged toolbar buttonsToolbar buttons with both an icon and text appeared too close together. They are now slightly enlarged, and there is more space between them. Also, the color has been changed for clarity when hovering.Resized toolbar buttonsMinor fixes and tasksIf a task start object or report start object was not included in the menu, it would not open at startup. This has been fixed. When leaving a field with a default setting to fill another field, the default value was filled in correctly, but the default value was not selected. Instead, the mouse cursor was placed right after the default value. This has been fixed. When tabbing through an editable grid, the dropdown lists of combo boxes could not be opened with a keyboard shortcut. This has been fixed. When zooming in on a screen until the menu on the left-hand side was hidden and then zooming out again, the menu remained hidden. This has been fixed. When adding a new parent record, incorrect child records were shown in the detail tab in some cases. This has been fixed. Now, when adding a parent record, only unrelated details will be displayed.  In some cases, when opening a subject with a default editable grid, the application could stop responding with a message: "Cannot read "allowUpdate" of undefined". This could especially occur when two or more grids were loaded and displayed at the same time. 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:DateTime controls with time zone - This allows DateTime values to always be stored in UTC+0 and displayed to the user in the time zone configured for that user. This will only work in Software Factory platform 2022.2. Grid edit mode flashing - To reduce this, we need to upgrade a third-party library. Technical design for asynchronous editing in a grid - To improve the performance of the grid edit mode, we plan to have multiple records in edit mode behind the scenes. This allows the user to continue while the records are saved in the background. In this sprint, we will start with a design. In progress: Variant API - This will only work in Software Factory platform 2022.2. UI/UX Drag and drop. UI/UX Design Vertical tabs.

Hello everyone,In this sprint, we worked hard on features for the upcoming 2022.2 Thinkwise platform release and features that take multiple sprints to build.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.18.0 here. Download Web GUI 2022.1.18.0 here. 

Hello everyone,In this sprint, we 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 2021.1.19 here. Download Indicium Basic release 2021.1.19 here.Contents of this releaseMinor fixes and tasksMinor fixes and tasksThe (legacy) DB2 iSeries driver can throw errors on SQL statements that are valid but where comment text is incorrectly treated as SQL, for example when a comment contains a question mark. However, the application connector did not handle this as an error, resulting in DB2 iSeries driver error messages that were not passed through. The application connector now correctly handles the DB2 iSeries error as an error. Note: The IBM DB2 .NET CORE driver does not have this issue and does not consider comments in SQL statements.

Hi everyone,The 2022.2 release of the Thinkwise platform is just around the corner, and it is packed with great new features and improvements such as handler procedures, notifications, time zone support, OpenID user provisioning, performance optimizations, and many new and improved process flow actions, for example for zipping, encryption and file storage handling.This release was originally planned for the end of June, but unfortunately we need one more sprint to dot the i's and cross the t's. As a result, the release will now be generally available in mid-July.If this impedes with any of your plans, please contact us to see how we can be of assistance.

Hello everyone!We’ve released the following platform improvements this week: SF 2021.3 and up20220509 - DB2 updated sf_product_info insert When installing or upgrading a DB2 end product, the insert into sf_product_info used a timestamp without a format. This led to problems, which now have been corrected.  

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.

Hello everyone,In this sprint, we added the possibility to disable the automatic password filling on the Login page. Also, cubes can now show the cube title in the active graph.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.17 here. Download Web GUI 2022.1.17 here.NewDisable automatic password filling on Login page[Web GUI] Login passwords used to be automatically filled in for users who had their passwords saved in their browsers. As of this version, the application manager can disable this behavior by setting the new parameter AutoFillPassword with the default value true to false in the settings.ini configuration file.Add cube title to active graphIt is now possible to show the cube title in the active graph by adding the extended property ShowTitleActiveChart and setting it to true.Minor fixes and tasks[Web GUI] A look-up control displaying suggestions did not get the focus until it was clicked twice. Only then you could start typing. This has been fixed.

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.

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.

Hello everyone,In this sprint, we solved some issues.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.16 here. Download Web GUI 2022.1.16 here.Minor fixes and tasks(Web GUI) In a screen with a default editable autosaved detail tab, when making changes and then immediately selecting another row in the parent grid, the changes were saved but the row was not selected. This has been fixed. (Web GUI) When editing in a grid with multiple drop-down columns, only the first column showed the correct data. Any subsequent drop-down list was empty. This has been fixed. All drop-down lists are now correctly updated. (Web GUI and Windows GUI) After an upgrade to Thinkwise Platform release 2022.1, detail tile icons were not displayed correctly. This has been fixed. (Windows GUI) When executing a task for multiple rows with the Popup for each row setting enabled, task parameter values in drop-down lists were not updated after each task run. This mainly happened when executing the task using the Ctrl + Enter keyboard shortcut. This has been fixed. (Windows GUI) If HTTP URLs were redirected to HTTPS URLs in IIS, the OAuth connector would fail. This has been fixed.

Hello everyone!We’ve released the following platform improvements this week: SF 2021.3 & 2022.120220407 - Set upgrade checkbox correctly when connecting to DB2 database Previously when connecting to a DB2 database from the Software Factory's Creation window, the value of the Upgrade checkbox would not be set correctly, which resulted in developers having to execute the upgrade manually. This has been fixed and the Upgrade checkbox will now be set correctly.

Hello everyone,In this sprint, we fixed an issue. Furthermore, we are working hard on features for the upcoming 2022.2 Thinkwise platform release and features that take multiple sprints to build, 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.17 here. Download Indicium Basic release 2022.1.17 here.Contents of this releaseBreaking Install Indicium 2022.1.17 together with Universal 2022.1.14 (BETA) Indicium Universal Minor fixes and tasks BreakingInstall Indicium 2022.1.17 together with Universal 2022.1.14 (BETA)In this release, we slightly changed the logout interaction between the Universal GUI and Indicium Universal to fix some redirecting issues.If you install this Indicium 2022.1.17 release, you must also install the Universal 2022.1.14 (BETA) releaseIndicium UniversalMinor fixes and tasksIn the Universal GUI, 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.

Hello everyone!We’ve released the following platform improvements this week: SF 2021.3 and up20220331 - Delete generated objects Generated domains used by process variable will no longer be deleted. IAM 2020.2 and up and SF 2021.3 and up20220406 - i_ui views performance optimizations We applied some extra optimizations to improve the performance for 3 i_ui views: i_ui_col_form, i_ui_task_parmtr and i_ui_report_parmtr. When dealing with a table/task/report that has many variants, the performance will increase significantly. When starting an end product created with the Thinkwise Platform, the model must be loaded. For the Universal GUI, this is done by using so-called i_ui views. These views load the data in the most efficient way, which is a challenge because the model and amount of data can differ enormously per customer. We always strive to offer a solution that works as well as possible for everyone. SF and IAM 2022.120220408 - Thinkstore download access token fix A problem was identified where solutions from the Thinkstore would fail to download due to incorrect handling of an access token in the authorization header. This has been resolved.  

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. 

Hello everyone!We’ve released the following platform improvements this week: SF 2020.2 and up20220329 - Grid group label fixed in i_ui_col_grid Previously, a group label would only be presented over one column, instead of over all columns that the group applies to. A fix for i_ui_col_grid was implemented that ensures that groups in grids will receive the correct group label at all times.

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 (Basic), 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.

Hello everyone!We’ve released the following platform improvements this week: SF 2020.2 and up 20220321 - Delete default cube view task correction When the default cube view is deleted, the other cube views are now no longer deleted also.

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 Basic release 2022.1.15 here.Contents of this releaseBreaking Install Indicium 2022.1.15 together with Universal 2022.1.13 (BETA) Indicium Basicand 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 Basic 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.

Hello everyone!We’ve released the following platform improvements this week: SF & IAM 2020.2 and up20220318 - Variant grid translation fix next group label When grouping columns in the grid for variants, the translation for the next group label would be retrieved for the main subject column instead of the variant column. This has now been fixed.