Product Updates

Hello everyone,In this release, we have made some usability improvements to the TOTP authentication setup, updated the DevExpress library, and improved the login provider selection process.You can read more about Indicium's features in the Indicium user manual. About IndiciumTwo types of the Thinkwise Indicium Application Tier are available:Indicium Basic (EoL): for use with the Windows GUI and Mobile GUI. This basic version does not support features such as system flows and OpenID. Download Indicium Basic release 2025.1.14 here. Indicium: for use with the Universal GUI and via APIs. This version uses the full range of Indicium functionality.Download Indicium release 2025.1.14 here.ContentsAbout Indicium Contents New and changed TOTP token displayed when setting up TOTP License trade distribution Updated DevExpress library Minor fixes and tasks Questions or suggestions? New and changedTOTP token displayed when setting up TOTPnewTo improve the usability of TOTP authentication, the TOTP token is now visible to the user in the setup screen, below the QR code. This allows for easier manual entry or verification.TOTP token that is now visible in the setup screenLicense trade distributionchangeWhen multiple Incidium instances on a shared database were scheduled to update their license, they could attempt to do so simultaneously. Due to the relatively resource-heavy query, this could lead to performance issues. We have now distributed license updates more evenly to reduce the load, minimizing the performance impact.Updated DevExpress librarychangeThe library version for DevExpress, which is used for generating reports, has been updated from 24.1.16 to 24.2.7. Verify your reportsWhile the update is unlikely to cause issues, we recommend you to verify your reports to ensure they work as expected.Minor fixes and tasksYou can add a certificate to a web connection in the Software Factory as an additional authentication measure. This did not work as expected on Windows Server machines and has been fixed.If you are working with IIS, make sure the application pool has Load user profile set to true.When an OpenID provider was configured in IAM with a hyphen ('-') in its name, the sign-in and sign-out buttons would not display images. This has been fixed. For Indicium Basic, we have fixed an issue where update and delete handlers did not work correctly when the primary key included a datetime or timestamp data type.Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community! 

Hi everyone!We’ve released the following platform improvements this week: SF 2025.1, 2024.320250530 - Clean up history data for all non-existent branches The task responsible for cleaning up history data for non-existent branches would skip the clean-up if there were no archived branches to be removed. However, this resulted in historical data of non-existent branches remaining in the history tables. This has been fixed.

Hi everyone!We’ve released the following platform improvements this week: SF 2025.120250523 - Re-apply new objects rights approval and disapproval logic The tasks to Approve and Disapprove new objects had the potential to hit more objects than it should. This usually does not lead to any issues but did have the potential to mark other new objects too during its approval or disapproval. This has been fixed.  

Hi everyone!We’ve released the following platform improvements this week: SF 2025.1, 2024.3, 2024.220250516 - Update merge conflict type of data column merge conflicts When modifying a model object with a data column, for example, a Report file, only changing the data of the Report would result in two merge conflicts, of which only one is shown. The one shown is of the Report file itself, and due to it being the same on both sides, it is automatically resolved. This had the unintended side effect that the data of the Target branch was always the chosen data. This has been fixed for Reports and Icons. The original conflict is no longer automatically resolved, and the developer can choose the preferred resolution.   20250514 - Scope rename of web connection endpoint parameter When renaming an input parameter of a Web connection endpoint, the usage was renamed for all endpoints rather than that specific endpoint. This has been fixed.

This is an additional release for the Universal GUI version 2025.1.13.1.We have fixed prefilter icons not being displayed properly in the action bar overflow.The 2025.1.13.2 release is now available for download in TCP.

This is an additional release for the Universal GUI version 2025.1.13.We have fixed lookup popups that didn't have a size configured not properly opening.The 2025.1.13.1 release is now available for download in TCP.

May 12, 2025Full release (from release candidate 2025.1.13) Additional fixes in this release: In some cases, focus was lost when <kbdTab</kbd> was used to navigate through the grid when adding or editing a record. This has been fixed. When the formlist is in a detail and the user switches records in the parent subject, the formlist would be empty in some cases. This has been fixed. In the release candidate, for details with a 1:1 parent relation, the Universal GUI would also remove the grid, tree, and card list if there was no form. This has been corrected; these components will only be removed if there is a form, just like the Windows GUI does. In the release candidate, *Quick filter* would wrongly stay disabled after clicking a grid cell. This has been fixed. When in an editable grid, clicking an editable column and pressing edit would not always keep the focus in the column. This has been fixed.  Hello everyone,In this release, we worked on adding support for the new Open as parameter in the process action Zoom detail. You can now choose how a zoomed document is opened in the Universal GUI. We also made some adjustments to the detail screen options when it has a 1:1 relation to its parent.For cubes, the pivot table field list is now available on mobile devices, allowing users to filter and sort data in their mobile applications. In addition, months will now be displayed using their full names in pivot tables and charts.For screen types, you can now configure pop-up sizes (Max height and Max width), and a fallback icon is now used for component tab pages without an icon.Lastly, we made some minor fixes and tasks to improve forms and grids, cubes, tasks, as well as other fixes to enhance the overall user experience. DemoAs always, we have made a demo for you: try it here. Before trying it out, press 'Clear Cache' on the login screen.Read the Universal GUI user interface guide to get familiar with the GUI. Universal GUI version 2025.1.13For more information about setting up the Universal GUI, see the Universal GUI setup guide.Note:Use a modern browser to access the Universal GUI, for example, a recent version of Chrome, Firefox, Edge, or Safari mobile. Deploy the Universal GUI on the same server as Indicium or an allowed origin in appsettings.json. Run all hotfixes on IAM and the Software Factory that you plan to use for the Universal GUI. Use the latest version of Indicium.Download the Universal GUI version 2025.1.13 here ContentsDemo Universal GUI version 2025.1.13 New and changed Support added for input parameter 'Open as' Adjustments in detail screen options Pivot table field list available for mobile devices Full month names in pivot tables and charts 'Max height' and 'Max width' available for screen types Fallback icon for component tab pages Lookups reflect lookup table order Minor fixes and tasks For forms and grids For cubes For tasks Other fixes What we will be working on next sprint Questions or suggestions? New and changedSupport added for input parameter 'Open as'newIn the latest Thinkwise Platform 2025.1 release we added the new input parameter Open as to the process flow action Zoom detail. This parameter determines how a zoomed document is opened. The Universal GUI now supports this feature. You can set this up in menu Processes > Process flows > tab Process actions > tab Input.You can select from the following options:Modal document - The document opens in a new window; interaction with the underlying application is not possible until the user closes the document. Detail tabs and detail tiles can now also be opened as a modal pop-up using Shift + (double) click. Support for opening as a floating window was already available. Document - The document opens in a docked window. Floating window - The document opens a new window ('floating') that can be repositioned.Currently, the process flow will not continue in a new tab if you select Floating window. Once the user closes the window, the process flow will continue in the main window. Adjustments in detail screen optionsnewWhen a detail has a 1:1 relation to its parent, the Universal GUI will now do the following on the detail screen:If there is a form component: remove cardlist, tree, and grid components. Remove the combined filter and filter form components. Remove the search and filter buttons from the action bar and toolbar. Make the add button read-only if there is already a record. Hide the copy button. Change the top bar translation to singular instead of plural.These changes are implemented because only one record can exist in a detail, rendering filtering options and components designed for multiple records unnecessary. Pivot table field list available for mobile devicesnewYou can create cubes in the Software Factory and use them in your application. To visualize data in a cube, you can use pivot tables to display data in a table format with aggregated information such as sums, averages, and counts.The pivot table field list is now available for mobile devices with the Universal GUI. With this field list, users can filter and sort data in their mobile applications. It allows them to select and arrange fields in a cube to create custom views of the data.Pivot table field list on the left side of the screen Full month names in pivot tables and chartsnewPreviously, the months in pivot tables and charts were represented by their corresponding number in the calendar (for example, '7' for July) in the Universal GUI. Months are now displayed using their full names, for example, the number '7' will now be displayed as 'July'. If you set the Interval of a dimension in menu User Interface > Dimensions > Form to Month, the Universal GUI will automatically display the translated month name based on the user's language settings. 'Max height' and 'Max width' available for screen typesnewYou can now configure the Max height and Max width for subjects in a pop-up (menu User interface > Screen types > tab Form). When a user opens a subject as a Floating document (Alt + click on a menu item), Modal document (Shift + click on a menu item) or a lookup pop-up, it will now open as the configured maximum size. Fallback icon for component tab pagesnewWhen no icon is assigned to a component tab page, the Universal GUI now displays the subject icon by default.The Universal GUI only shows tab page icons when the extended property ShowTabIcons is enabled. Lookups reflect lookup table orderchangeLookups in the filter form, mass-update pop-ups and import pop-ups now reflect the sort order of the lookup table.The sorting behavior in the filter form is only applied when the lookup control is of the type Combo (sorted) (menu User interface > Subjects > tab Default > tab Settings > tab General > group Look-up).For example, if the display column full_date is sorted in descending order, the dropdown will also show the values in descending order. Minor fixes and tasksFor forms and gridsOn data grids users can drag records and headers for ordering. When both were enabled on a subject, and the reordering was saved as user preferences to IAM, the header reordering caused unexpected behavior because of an internal error. This has been fixed. When Allow Sort (menu User interface > Subjects > tab Settings > tab Permissions > group Data) was disabled on the subject and a lookup column was sorted by default, applying filters using the pop-up filter was not possible. This issue has been resolved. Users can now filter lookup fields in the grid, regardless of the column's sorting behavior. Previously, when editing a form the conditional layout text color would disappear for a lookup. This has been fixed. When a lookup control was hidden inside a form, the clear button would remain visible. This has been fixed. Resolved an issue where the detail form appeared empty after adding or copying a parent record from the main subject. Fixed a bug where the detail form was not cleared when adding a parent record via the detail tab. When a new form is opened to add a record, the cursor is now automatically placed in the first editable and empty field. Fixed an issue where the grid could become unresponsive when a field constraint was violated. When Model insight was active, column information was not consistently displayed when selecting a grid cell or a form editor. This has been fixed. In some cases, reordering columns in the grid was ignored, and switching records would cause the columns to revert to their previous positions. This has been fixed. When the fixed column area of the grid reached the left border, the first non-fixed column would briefly flash over the beginning of the fixed column area after a user action. This flashing behavior has been fixed. When selecting a new value in a Time domain control, calculated fields were not updated in the UI. This has been fixed. If no empty field exists in the form, the cursor defaults to the first editable field.For cubesWhen a domain, with elements, of the datatype int was used as a category in an editable pivot grid, changing an editable value resulted in a bad request error. This has been fixed. At times, the editable pivot grid would give the error: 'It is not possible to change an axis value that is based on multiple rows', despite there only being one row behind the cell. This has been corrected. When the cube field ID did not match the subject column ID, the drilldown would display unfiltered data for that axis. This has been fixed. When categories or series were changed via the cube field editor or by the user, the drilldown filters did not update accordingly. This has been resolved.For tasksPreviously, when a task pop-up had a Signature domain control, the pop-up would slowly become wider with increments of 2 px. This resulted in the signature control being cleared every time it was resized. This has been fixed. Double-click tasks for the tree did not work. This has been fixed. When editing a task parameter configured with an HTML domain control, you have two pop-ups: one for the task and one for the HTML domain control. Previously, pressing the escape key in the HTML pop-up would close both pop-ups. Now, it only closes the HTML pop-up.Other fixesFixed a bug where the layout would not reset after pressing cancel. When importing data with the Import wizard, the table permissions are now enforced more accurately. When adding or updating data is disabled, the relevant import options, such as Insert all data or Add new rows, update existing rows are automatically hidden. If both actions are restricted, the import is not shown. If the Add permission is disabled, only Update existing rows will be available; if the Update permission is disabled, only Insert all data will be shown. In some cases, the action bar overflow menu button would have no content when clicked. We have disabled the overflow button for these cases. In the Scheduler, when using Sliding pagination, the view would incorrectly start one month earlier if the top timescale was not set to Year. In addition, when switching between timescales, the current date would not always remain in view. These issues have been fixed. The breakpoint screen type was not being shown in certain cases. This has been fixed. The badge for About in the profile menu had the incorrect color. This has been fixed. What we will be working on next sprintThe next sprint we will be working on:Scheduler component improvements Maps component improvements File upload support for offline tasks Maintenance Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community! 

Hi everyone!We’ve released the following platform improvements this week: SF 2025.1, 2024.320250508 - Reapply conflict resolution in merge conflict overview when refreshing merge session The refresh merge session mechanism could reapply chosen merge conflict resolutions when they were no longer applicable or possible. In the off-chance that the underlying models were modified so that these conflict resolutions would cause delta actions to stay available when they should be unavailable, an error would occur during the execution of the merge session. This has been fixed. ⚠️ It is recommended to install this as soon as possible. Please download the latest hotfixes from TCP. SF 2025.120250507 - Only write program objects with file specification Writing program objects to a storage location would fail, as the Smoke test related program objects do not have a file specification. This has been fixed.

Hello everyone,In this release, the import process has been enhanced to handle non-unique header names, and domain translations have been updated to include cases with only one min/max constraint.You can read more about Indicium's features in the Indicium user manual. About IndiciumTwo types of the Thinkwise Indicium Application Tier are available:Indicium Basic (EoL): for use with the Windows GUI and Mobile GUI. This basic version does not support features such as system flows and OpenID. Indicium: for use with the Universal GUI and via APIs. This version uses the full range of Indicium functionality. Download Indicium release 2025.1.13 here.ContentsAbout Indicium New and changed Unique header names while importing Translation for a domain with only one min/max constraint Minor fixes and tasks Questions or suggestions? New and changedUnique header names while importingchangeIndicium can now successfully import files containing non-unique header names. Previously, this would cause the import to fail.An import file with two duplicate header namesNow, duplicate header names are made unique by adding a suffix during the import process (for example, name__1 and name__2). This update affects the prepare data and map data stages of your import, and will also be returned in the headers of the failed rows Excel file.The duplicate header names with a suffix to make them unique Translation for a domain with only one min/max constraintchangePreviously, there was only a translation for min/max constraint values in a domain when both values were specified (menu Data > Domains > tab Form). Now, there is also a translation when only one of the values is specified. This is visible in the message when a constraint is violated. Minor fixes and tasksWe have fixed an issue that caused various file storage connector (e.g. Copy File, List Folder) for Azure File storage providers to not work when a SAS token was used for authentication. This fixes the problem that was reported here. Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

This is an additional release for the Universal GUI version 2025.1.12.1.In this release, we have fixed selecting records in the grid on touch devices not working.The 2025.1.12.2 release is now available for download in TCP.

Hi everyone!We’ve released the following platform improvements this week: IAM 2025.120250414 - Return default global configuration extended properties when none specified The procedure responsible for returning global configuration extended properties would not return the data of the default global configuration when no global configuration ID was specified. This has been fixed. 20250417 - Improve performance of get_gui_drag_drop_link We made a change to the underlying view that ensures procedure get_gui_drag_drop_link returns unique records. However, this had the potential to decrease the performance and even lead to timeouts. This has been fixed. SF 2025.120250417 - List included index columns for non-clustered history table indexes Non-clustered (history) index columns that were set to be 'Included' were not included in the generated code due to an oversight. This has been fixed. 20250418 - Improve sync data processing for role_tab_variant_look_up The step to synchronize model data for role_tab_variant_look_up had the potential to stall the synchronization process. This has been fixed for this procedure. In 2025.2 for all synchronization procedures.

Hello everyone,Earlier today we did an early release of Indicium with version 2025.1.12.1 to support the “Report file (non-file storage)” report parameter property in Generate Report process actions as well. Due to a mistake, this version of Indicium would not start up. We have just released version 2025.1.12.2 which fixes this problem.Our apologies for any inconvenience caused by this.

This is an additional release for the Universal GUI version 2025.1.12.We found out that the 2025.1.12.0 did not contain the changes of last sprint as we wanted it to have. So if you already deployed the 2025.1.12.0 version, please replace it with this.The 2025.1.12.1 release is now available for download in TCP.

Hi everyone!We’ve released the following platform improvements this week: IAM 2025.120250410 - Correct UP setting for storing collapsible section states Existing IAM environments that upgraded to 2025.1 had the User preference configuration setting for storing the Collapsible section state false by default, whilst two default configurations should have this setting set to True. This has been fixed. The default User preference configurations Move, On_Off and Complete now allow the user to store the collapsible state of Sections. Universal GUI version 2025.1.12 or up is recommended.

April 13, 2025Full release (from release candidate 2025.1.12) Additional fixes in this release: Collapsing or expanding collapsible form sections would sometimes trigger the message "This action is not allowed." This issue has been resolved. Hello everyone,in this release, we have added support to some refresh options to also refresh the subject's parent row, and for the form Column width factor setting in the Software Factory. Aggregations in the grid have been improved to use selected records instead of the entire dataset.We have also restyled the grid header and the pivot tables. For editable pivot tables, we have added some functional changes as well, such as cell navigation, and editing cells on focus. DemoAs always, we have made a demo for you: try it here. Before trying it out, press 'Clear Cache' on the login screen.Read the Universal GUI user interface guide to get familiar with the GUI. Universal GUI version 2025.1.12For more information about setting up the Universal GUI, see the Universal GUI setup guide.Note:Use a modern browser to access the Universal GUI, for example, a recent version of Chrome, Firefox, Edge, or Safari mobile. Deploy the Universal GUI on the same server as Indicium or an allowed origin in appsettings.json. Run all hotfixes on IAM and the Software Factory that you plan to use for the Universal GUI. Use the latest version of Indicium.Download the Universal GUI version 2025.1.12 here ContentsDemo Universal GUI version 2025.1.12 New and changed Refresh parent subject row Grid header restyling Improvements for aggregations Pivot table UI/UX update Support for 'Column width factor' in the Software Factory Minor fixes and tasks What we will be working on next sprint Questions or suggestions? New and changedRefresh parent subject rownewWe have extended the following Refresh options: Row and Subject (menu User interface > Subjects > tab Settings > group Refresh > fields After insert/copy/update/delete). They now also refresh the subject's parent row. The parent row is also refreshed when a table task is executed with Refresh after execute set to Row or Subject (menu Process flows > Tasks > column Refresh after execute).This change solves several issues where the parent row was missing after executing a task, and subsequent actions, such as a process flow, would crash. Furthermore, the refresh option Document, which is performance-heavy, is now less essential. Instead, you can now update a calculated field in the parent with the child subject's update trigger or handler, by setting the child's refresh option to Row or Subject.Note: the Universal GUI refreshes the parent row only one level up. Grid header restylingchangeThe grid column headers have been redesigned:The border and text styles have been updated. The header height is now fixed and no longer responds to the data record height. Previously, when the header text did not fit the column width, it was cut off. Now, the text wraps over multiple lines.Note: with the new styling, the header height, in general, has decreased. If you are using longer column names with multiple words, they take up more space now. Using column header groups may be a better alternative for very long names. Configuring the column (auto) size also helps to properly show the header text.Grid column header restyling Improvements for aggregationsnew Previously, the Universal GUI always calculated aggregations in a grid based on the entire dataset. When selecting multiple records, the Universal GUI will now use selected records to calculate the aggregate. When a single record is selected, the Universal GUI will use the entire dataset.The Universal GUI supports aggregation types average, sum, count, min, and max. Before, when an unsupported aggregation type was selected in the Software Factory, the Universal GUI would default to using the aggregation type sum. Now, if an unsupported aggregation type is selected in the Software Factory, no aggregation will be shown. Pivot table UI/UX updatechangeWe have updated the styling and some UX aspects of the pivot tables. Additional functional changes in pivot tables are:The pivot row height now follows the grid row height (menu User interface > Subjects > Settings > Grid > Row height). The pivot header height no longer follows the grid row height. The category columns are now pinned. The category and value columns now auto-wrap their header titles. Note that this can cause the header to use more rows in existing cubes. An Enter on a cell now behaves like a double click and opens the drilldown.Additional functional changes in editable pivot tables:Cells are now editable on focus. Cell navigation is possible with Tab, Shift + Tab, and arrow up and down. Arrow left and arrow right navigate the cursor in the value of the cell. Drill-down in editable cells is suppressed.Known issue: when the editable field is a domain with elements, cell navigation does not yet work like it should. Support for 'Column width factor' in the Software FactorynewWe have added support for the form setting Column width factor in the Software Factory. It allows you to control the column width of task and report pop-ups. For more information, see Form column width factor. Minor fixes and tasksFor lookup fields and editors:Selecting the Clear button for a lookup field did not apply the defaults correctly. This issue has been fixed. We have fixed an issue where the default value was not properly applied when typing an exact value in a lookup editor and leaving the field. In editable grids and forms, a modified lookup editor briefly showed different values before the actual value appeared after leaving the field or record. This issue has been fixed. As usual, the latest version of Indicium (2025.1.12) is required for this fix. When switching rows repeatedly by clicking a lookup editor in a default editable grid, clicks would sometimes get ignored. As a result, the desired row did not become active and editable. This has been fixed. After switching to a different row, lookup editor cells could appear as if they were still active. This issue has also been improved. When selecting checkboxes on the same row in a default editable grid, a different checkbox than the one selected would change its state as well. This issue has been fixed. When rapidly selecting checkboxes on different rows in a default editable grid, some checkboxes would revert to their original state. This issue has been fixed. In a default editable grid, the layout logic was not applied to the active record when the record was updated by triggers, update handlers, or other users. This has been fixed.Other:If a FormList was set to refresh the subject after an update, it scrolled back to the top, and the focus was no longer on the correct editor. This issue has been fixed. When navigating to a different tab that uses a subject variant and returning to the initial tab, the conditional layouts would sometimes not apply correctly. This issue has been fixed. When an action bar button with a non-SVG icon was disabled, the icon was not grayed out like it was with the old toolbar. This has been fixed. Importing column mapping failed for mandatory fields with a default value. This issue has been fixed. Now, a mandatory column without a mapping will not be selected by default, respecting the default value. A constant value is not required for this field, as it is handled by the default value from the Software Factory. Only when a user explicitly provides a value will it be sent to Indicium. This change prevents the default value from being overridden unnecessarily and resolves the import block. We have fixed an issue that occurred when a URL or HTML domain control contained a URL with special characters (such as %A7). As of Thinkwise Platform version 2025.1 or when the Action bar was hidden, the Model insights component no longer showed model information. This issue has been fixed. What we will be working on next sprintThe next sprint we will be working on:Conditional layouts for charts Opening a zoomed detail as a new document by a process flow (Thinkwise Platform 2025.1 feature) Scheduler improvements Pop-up size settings from the 2025.1 platform release Maintenance Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

Hello everyone,In this release, we have added a new button to the Process Flow Monitor that allows you to refresh the model without leaving the Process Flow Monitor. To make troubleshooting failed import rows easier, the reason for the failure is now included in the error file. For the process flow action Download file, we have added support for the input parameter Try to preview.You can read more about Indicium's features in the Indicium user manual. About IndiciumTwo types of the Thinkwise Indicium Application Tier are available:Indicium Basic (EoL): for use with the Windows GUI and Mobile GUI. This basic version does not support features such as system flows and OpenID. Indicium: for use with the Universal GUI and via APIs. This version uses the full range of Indicium functionality. Download Indicium release 2025.1.12 here. ContentsRelease notes Indicium (2025.1.12) About Indicium New in Indicium Added a refresh model button to the Process Flow Monitor Added reasons for failed import rows Implemented input parameter for 'Download file' Minor fixes and tasks Questions or suggestions?  New in IndiciumAdded a refresh model button to the Process Flow Monitornew Universal GUIYou can start system flows manually in the Process Flow Monitor for debugging purposes. This feature works by showing all eligible system flows from a Software Factory runtime configuration in a dropdown menu. However, Indicium cannot detect model changes in a Software Factory meta-source.For this reason, logging out and back in or calling the refresh_model method with an external tool was necessary when testing a newly added or changed system flow. To improve this process, we have added a new button: Refresh model. It allows you to refresh the model without leaving the Process Flow Monitor.Refresh model in the Process Flow Monitor Added reasons for failed import rowsnewWhen importing data, the downloadable Excel file with rows that could not be imported only contained which rows and columns failed, but not the reason why they failed.To make troubleshooting failed import rows easier, we have added a new column called '(Errors)' to this Excel file. This new column contains the error message for each failed row. Implemented input parameter for 'Download file'newIn the Thinkwise Platform 2025.1 release, the input parameter Try to preview was added to the process flow action Download file. We have now added support for this input parameter in Indicium, which indicates whether a file should be previewed before downloading. Previewing is not possible for all file extensions. Minor fixes and tasksWe have fixed an issue where a record import was reported as successful when, in reality, it failed. It would occur when the import failed due to certain types of database-level errors. We have fixed a small styling issue in the Process Flow Monitor which could cause text to overflow their cells and overlap with text in other cells. Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

Hi everyone!We’ve released the following platform improvements this week: SF 2025.1Package fix for Cube views We have resolved an issue where a drag-drop link was added twice. This resulted in the Software Factory not being able to start up properly. Important: If you plan upgrade to 2025.1 or later, download a new package from TCP to obtain the latest up-to-date version of the package.   20250404 - Correct code search error for default value queries When performing a code search where the search query found code in both the Data migration column default value query as well as in the Column itself, the code search execution would fail. This has been resolved.

Hello everyone,In this release, we have added support for newer Indicium distributions that only provide an appsettings.sample.json file to use as a reference when creating the actual appsettings.json configuration file. We have also added new Microsoft Entra authentication options to use when connecting to SQL Server databases.Download the Thinkwise Deployment Center 3.3.0 here. ContentsContents New in the Thinkwise Deployment Center Support for Indicium's appsettings.sample.json Microsoft Entra authentication options Questions or suggestions? New in the Thinkwise Deployment CenterSupport for Indicium's appsettings.sample.jsonGUI CLIWe have added support for newer Indicium distributions that only provide an appsettings.sample.json file to use as a reference when creating the actual appsettings.json configuration file.GUI Some deployment combinations can cause the comments from the Indicium sample configuration to become unavailable in the final appsettings.json. To accommodate this when using the Advanced edit mode during an Indicium upgrade flow, the Deployment Center offers a View sample button to view the appsettings.sample.json file from the package in a separate window. This will allow you to reference any newly added settings or view the descriptions of settings should they be missing in the appsettings.json file of the deployed Indicium.Configure Indicium appsettings.jsonMicrosoft Entra authentication optionsWe have added new Microsoft Entra authentication options to use when connecting to SQL Server databases. The following fields have been added to the GUI when selecting a database server host instance:SQL Server Authentication Authenticate using a regular SQL Server account username and password. Using this is the same as previously clearing the checkbox Integrated security. Windows Authentication Authenticate using the current Windows user account. Using this is the same as previously checking the checkbox Integrated security. Microsoft Entra Password Authenticate using your username and password against the Microsoft Entra tenant configured for the SQL Server instance. The username is always your email address. Microsoft Entra Integrated Authenticate using the current Windows user against the Microsoft Entra tenant configured for the SQL Server instance. Requires the computer to be domain joined/federated with the Microsoft Entra tenant. Microsoft Entra MFA Authenticate interactively using a browser window like most Microsoft/Azure service web sites. Due to being handled by the OAuth/OIDC this option also supports Multi-Factor Authentication methods. Microsoft Entra Service Principal Authenticate using an Application Service Principal in a Microsoft Entra tenant. Requires the App ID and a client secret value from the target application registration.In addition, the following advanced options have been added:Encryption - Sets the level required for SSL/TLS when connecting to the server and can be set to: Optional - Uses SSL/TLS if it is available but it is not required. Mandatory - Requires the server to provide SSL/TLS. Strict - Same as Mandatory but requires the connection to support at least TDS 8.0. Trust server certificate - Production servers should always use a valid SSL/TLS certificate. However, development servers might not be properly configured with one. This option can be used to always trust the certificate given by the server even if it, for example, is self signed. Certificate host name - This setting can be used to specify the host name that is expected to be provided in the SSL/TLS certificate in case it does not match with the host being connected to.Configure Microsoft Entra authentication in the GUIFor the command-line interface, new Microsoft Entra authentication options have been added when connecting to SQL Server databases through the iam/sf/upcycler/app commands. These can be set through the --auth-method and --iam-auth-method options depending on the subcommand. The --auth-method option might become required in the future, but currently falls back to previous implicit authentication methods for backwards compatibility.The following commands are available:UserPassword - Authenticate using a regular SQL Server account username and password. Using this is the same as previously providing a --username value. WindowsAuthentication - Authenticate using the current Windows user account. Using this is the same as previously not providing a --username value. MSEntraUserPassword - Authenticate using username/email and password against the Microsoft Entra tenant configured for the SQL Server instance. MSEntraIntegrated - Authenticate using the current Windows user against the Microsoft Entra tenant configured for the SQL Server instance. Requires the computer to be domain joined/federated with the Microsoft Entra tenant. MSEntraMFA - Authenticate interactively using a browser window like most Microsoft/Azure service websites. Due to being handled via OAuth/OIDC this option also supports Multi-Factor Authentication methods. However, due to the interactive nature of this flow, this value is not suitable for use in scripts running inside a CI environment. MSEntraServicePrincipal - Authenticate using an Application Service Principal in a Microsoft Entra tenant. Requires the App ID (--username) and a client secret (--password) value from the target application registration.To remain backwards compatible with previous behaviour, the advanced options currently available in the GUI are interpreted as follows in the command-line interface:Encryption - always set to Optional which will use SSL/TLS if available but it is not required. Trust server certificate - always set to True which allows incorrectly configured/invalid certificates from the server. Certificate host name - always empty, due to Trust server certificate always being true this option does not do anything anyway.Configure Microsoft Entra authentication in the CLIQuestions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

Hello everyone, In this release, we have resolved a problem with drag & drop.You can read more about the Windows GUI's features, in the user interface guide.Download Windows GUI (2-tier) 2025.1.11 here. FixedFreeze when dragging & dropping If a user scrolled in a list for a long time during drag & drop while holding a record, the Windows GUI would freeze. This issue has been fixed. Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!  

March 17, 2025Full release (from release candidate 2025.1.11) Additional fixes in this release: The Search in the action bar stayed hidden while the dataset was still loading and no longer appeared properly. This occurred especially on slow connections. This has been fixed. Hello everyone,In this release, we have updated the row visibility in the card list. We have also fixed several issues. DemoAs always, we have made a demo for you: try it here. Before trying it out, press 'Clear Cache' on the login screen.Read the Universal GUI user interface guide to get familiar with the GUI. Universal GUI version 2025.1.11For more information about setting up the Universal GUI, see the Universal GUI setup guide.Note:Use a modern browser to access the Universal GUI, for example, a recent version of Chrome, Firefox, Edge, or Safari mobile. Deploy the Universal GUI on the same server as Indicium or an allowed origin in appsettings.json. Run all hotfixes on IAM and the Software Factory that you plan to use for the Universal GUI. Use the latest version of Indicium.Download the Universal GUI version 2025.1.11 here ContentsDemo Universal GUI version 2025.1.11 Contents New and changed Row visibility in the card list Minor fixes and tasks What we will be working on next sprint Questions or suggestions? New and changedRow visibility in the card listchangeWe have enhanced the way selected and hovered rows are displayed in the card list by changing the row highlighting. The selected and hovered row colors now use a gradient based on the main color selected for your theme in the Software Factory rather than a grey tone. Minor fixes and tasksWe have fixed an issue where scrolling in the grid on a touch device mistakenly changed the active record due to scrolling gestures being misinterpreted as clicks. Previously, when a record was updated from a related subject or by another user on a default editable subject, the editor did not show the most recent changes. Now, when the record has not been changed by the user, the most recent values are shown. A default editable parent or child subject is now updated when, for example, a task is executed on the subject. The Universal GUI uses timers per subject to manage auto-refresh, which can have the option for change detection. Under certain conditions, more than one timer was created for the same subject which caused several issues. This issue has been fixed. If the user initially opened a tab using a default variant of a subject, conditional layouts were applied correctly. However, if the user switched to another tab that used a variant of the same subject and then returned to the initial tab, the conditional layouts sometimes failed to apply. This issue has been fixed. If, for example, an Action bar task was placed in the overflow menu by setting the Custom display type to Overflow, it was sometimes displayed incorrectly as an icon only element in the overflow menu. This has been fixed. On mobile devices, the background image showed a gap at the top of the screen. This has been fixed. What we will be working on next sprintThe next sprint we will be working on:Grid header re-styling Pivot table re-styling Pivot table pinned categories Maintenance Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

Hi everyone!We’ve released the following platform improvements this week: SF 2025.120250307 - Modify create_breakpoint_screen_types enrichment with ActionBar With the introduction of the Action bar, the old Toolbar has been removed. Any references to the toolbar have been changed to the Action bar for this enrichment.   20250313 - Correct data in variant screen Changes compared to default The 2025.1 feature to compare a variant to its default (see Release notes and Docs) did not display the complete set of data that it should: We did show data when the default table/task/report has no value, and the variant does have a value. We did show data when when the default table/task/report has a value, and the variant has a different value. We did not show data when when the default table/task/report has a value, and the variant has no value. This has now been fixed.   SF 2025.1, 2024.3, 2024.220250312 - Correct difference analysis of arbitrary merge sessions When performing an arbitrary merge from one branch to another, the difference analysis was not always able to determine conflicts properly, resulting in missed conflicts and eventually a failed merge session. This has been fixed. You can use Arbitrary merge sessions to migrate a branch with changes into a freshly made new branch. This essentially rebases your branch, and allows the origin model version to be up-to-date.   IAM 2025.1, 2024.320250313 - Copy classic user-defined prefilter states When copying an application in IAM, you can copy the user preferences of the copied application to the new one. However, the default states of user-defined prefilters were not copied properly resulting in these prefilters being turned off. This has been fixed.

Hello everyone,In this release, we have fixed an issue with the error reporting during import operations.You can read more about Indicium's features in the Indicium user manual.About IndiciumTwo types of the Thinkwise Indicium Application Tier are available: Indicium Basic: for use with the Windows GUI and Mobile GUI. This basic version does not support features such as system flows and OpenID. Indicium: for use with the Universal GUI and via APIs. This version uses the full range of Indicium functionality.Download Indicium release 2025.1.11 here. ContentsAbout Indicium Minor fixes and tasks Questions or suggestions?Minor fixes and tasksWe have fixed an issue that would report the importing of a record as being successful when in fact it failed. This issue would occur when the import failed due to certain types of database-level errors. When this happened, Indicium would incorrectly report the result of the row import as successful, leading to a mismatch between the displayed import result and the actual import result.Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community! 

Hi everyone!We’ve released the following platform improvements: SF & IAM 2025.1Cubes20250303 - Modify create_cube enrichment after Cube refactor After the Cube refactor, the enrichment to create a cube was affected and could raise an error when used. This has been fixed. 20250306 - Cube categories drag-drop correction It was impossible to use drag-drop to change the order of Categories / Rows in the Cube set-up panel. This has been fixed. Action bars20250305 - Prevent syncing custom actions for removed custom action bar It was possible for removed custom action bars to leave behind custom actions that were set up prior to the removal of the bar. These leftover actions were then synchronized to IAM which caused the Windows GUI to raise an error. This has been fixed.   20250307 - Modify create_breakpoint_screen_types enrichment with ActionBar With the introduction of the Action bar, the old Toolbar has been removed. Any references to the toolbar have been changed to the Action bar for this enrichment.

Hello everyone,As of this release, we have introduced several new solutions to the Thinkstore. Furthermore, we have restructured and enhanced a large number of other solutions. ContentsContents About the Thinkstore New and changed in the Thinkstore models Standard http queue with system flow (API) Columnstore index and AI search Add index temporal table Email system flow Maps and Routes Renamed 'Using OAuth to get data from external applications' Default tooltip Make sure your display values are unique Turn off enable tab task when empty Find a certain char in a string Generate a unique randomized token Thinkwise Guideline Validations Check constraint for easy user input validation Difference in data between two databases Friendly error msg for databaseconnector Date prefilters Questions or suggestions? About the ThinkstoreThe Thinkstore is a fully integrated way for downloading and installing ready-made solutions directly into your models right from the Thinkwise IDE. It contains a collection of scripts and samples to help you get the most out of the Thinkwise Platform. You can find the Thinkstore in the Software Factory, in the menu Enrichment > Thinkstore.The Thinkstore only contains solutions specifically for the Software Factory version you are using. Therefore, the Thinkstore will be cleared before every platform upgrade. After the upgrade, if you open the Thinkstore in the new Software Factory version, it will initiate a refresh and retrieve all the available solutions for that version. This process runs in the background. It can take up to ten minutes before the solutions are available.You can read more about the Thinkstore in the Thinkstore guide. New and changed in the Thinkstore modelsStandard http queue with system flow (API)newWe have introduced a new solution in the Thinkstore: Standard http queue with system flow (API). This solution provides a queue table with all the input and output variables of a HTTP connector process action.A system flow executes HTTP calls and stores the response data into the table. This allows both users and the system to process the retrieved information.Columnstore index and AI searchnewThis new solution contains an example of how to use a columnstore index in the Software Factory, combined with AI search.The data model consists of a product table that can compare itself to other products within that table and provide a matching score. A higher score indicates that the product is more similar to the selected product.The columnstore index ensures that this functionality is extremely fast. Columnstore indexes store data by column instead of row, offering significant data compression and reducing storage needs. This leads to faster queries because less data is accessed during query execution.More general information about columnstore indexes: Microsoft More information about columnstore indexes in the Software Factory: IndexesAdd index temporal tablechangeThe model Add index temporal table has been changed because of the introduction of the Non-clustered (history) index in the Software Factory.Add index temporal table now contains a dynamic model. When the tag add_history_index is added to a table, the dynamic model creates an index on the history table based on the primary key of the original table.This index helps when you have included the Thinkstore solution Logging data available in the GUI in your model or when you query your history table with the original primary key.Email system flowchangeThe Email system flow has been completely restructured for improved efficiency and reliability. This update streamlines email handling and ensures a more scalable and robust solution for managing email workflows.Key changes include:New email table: We have introduced an email table with a status field, serving as a queue table for email processing. Background process: A new system flow, email_read_next_queue_id, has been implemented to manage queued emails. It identifies and picks up the next email to be sent automatically. Subflow execution: The system flow triggers a subflow that sends emails using the Email connector.The Example email module has been deprecated as the newly updated Email system flow now provides a more comprehensive and efficient alternative.Maps and Routeschange Universal GUIThe models Maps (mymappi) and Google Maps have been merged into a new model named Maps and Routes. This new model serves the purpose of teaching how to work with the Maps component in the Universal GUI. It also uses two Web connection endpoints for retrieving the GPS coordinates and routes.You need to get your own API key from Google and enter it in the Web connection.The model includes a menu for addresses and routes:Adding an address initiates a process flow that uses the Web connection to retrieve and display the GPS coordinates on the Maps component. Once you have at least two addresses, you can add a route. The Web connection retrieves and displays the fastest route on the Maps component.Renamed 'Using OAuth to get data from external applications'changeThe model Using OAuth to get data from external applications has been renamed to Using OAuth to get data from Exact Online. In addition:The MS Graph connection has been removed. This will be a separate Thinkstore model. Instead of an HTTP connector, a Web connection is now used.Default tooltipchangeThe model Default tooltip has been updated:The generation strategy has been changed to Fully Controlled. The code has been changed so the trace columns are updated. The code has been changed so the tooltip translation is also updated when the translation is updated.Make sure your display values are uniquechangeThe generation strategy has been changed to Staged.Turn off enable tab task when emptychangeThe generation strategy has been changed to Fully Controlled. The code has been changed to a where not exists. The code has been changed to create the tag when it does not exist yet.Find a certain char in a stringchangeWe have added a table valued function so the functionality will be easier to use.Generate a unique randomized tokenchangeWe created a subroutine (procedure) for the functionality. Previously, it was only an example script.Thinkwise Guideline ValidationschangeWe renamed the validation column_name_starts_with_the_table_name to tsf_guideline_column_name_starts_with_the_table_name. This is to be in line with the rest of the naming of the validations. In the validation tsf_guideline_column_name_starts_with_the_table_name, the like missed the '%', this has been corrected. tsf_guideline_domain_which_contains_the_name_of_an_rdbms_datatype now only checks for the RDBMS type of the model. All the validations that use a cursor with a table variable have been changed to a temporary table to improve performance and stability. See this Community post.Check constraint for easy user input validationchangeWe changed the strategy for the meta control procedure "check_constraint_message_add" from delete to staged.For more information about the custom check constraints, see the blog Check constraints using the Software Factory.Difference in data between two databaseschangeWe removed unnecessary parts of the model, reducing the size of the export file model.dat, without any other changes.Friendly error msg for databaseconnectorchangeWe changed the strategy for the meta control procedure database_connector_process_action from delete to fully controlled. We also modified the insert statement for the table process_action_output_parmtr to include the column output_parmtr_type with a value of fixed_option.We changed the strategy for the control procedure error_log_code from delete to staged. We also removed the parameter @error_log_code from the error handling code in the template error_log_code, as it was not declared.Date prefilterschangePreviously, this model included a table named date_of and a prefilter group called date_filters with 4 prefilters. Now, it only contains a meta control procedure tab_date_prefilter that adds the prefilter group and prefilters to all tables linked with the tag tab_date_prefilter. In the tag value, you must specify a column with a domain of data type DATE, DATETIME, or DATETIME2.The 5 prefilters created are:Current week Year to date (new compared to the previous model) Current month Current quarter Current yearThese prefilters can be adjusted within the dynamic code if you desire more or fewer prefilters, or if you wish to modify any details of the prefilters. We set the strategy for the meta control procedure tab_date_prefilter to fully controlled, giving you the freedom to change the details after creation. Note that changes to the dynamic code will not modify the already created prefilters.You have to get your own API key from Google and enter it in the web connection.The model includes a menu for addresses and routes.Adding an address initiates a process flow that uses the web connection to retrieve and display the GPS coordinates on the maps component. Once you have at least 2 addresses, you can add a route. The web connection will then retrieve and display the fastest route on the maps component.Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

Hello everyone,In this release, we have added support for a number of new features that have become available with the Thinkwise Platform release 2025.1. These features include the formalization of action bars, the assignment of actions to screen areas, and the support for default expand grouped grid.We have also implemented the new UI styling for the action bar and grid rows. DemoAs always, we have made a demo for you: try it here. Before trying it out, press 'Clear Cache' on the login screen.Read the Universal GUI user interface guide to get familiar with the GUI. Universal GUI version 2025.1.10For more information about setting up the Universal GUI, see the Universal GUI setup guide.Note:Use a modern browser to access the Universal GUI, for example, a recent version of Chrome, Firefox, Edge, or Safari mobile. Deploy the Universal GUI on the same server as Indicium or an allowed origin in appsettings.json. Run all hotfixes on IAM and the Software Factory that you plan to use for the Universal GUI. Use the latest version of Indicium.Download the Universal GUI version 2025.1.10 here ContentsDemo Universal GUI version 2025.1.10 Contents Breaking Thinkwise Container images New and changed Action bars formalized Screen areas to assign actions to screen components Support for default expand grouped grid Support for disabling multirow selection Support for collapsible form sections Support for calculated cube fields Row visibility in the grid Security update Minor fixes and tasks Questions or suggestions?BreakingThinkwise Container imagesIf you use a container image from the Thinkwise Container Registry, the default port has changed from 80 to 8080.For more information, see the blogpost Thinkwise Container images breaking change. New and changedAction bars formalizednewAs of Thinkwise Platform release 2025.1, the Universal GUI uses Action bars and Custom action bars. The screen component Toolbar is no longer available as of this platform version. When starting this Universal GUI version against an older platform version such as 2024.3, the Toolbar will still be displayed.The new action bars offer you more flexibility in their content and appearance. For more information about configuring the (Custom) action bars, see User interface - More control over action bar placement in the Universal GUI in the Thinkwise Platform 2025.1 release notes.The following features are available in the new action bars:New styling for prefilter, CRUD, and task/report buttons as described in the blog post Styling update of the Universal GUI. In Comfortable mode, the buttons are bigger and have more space around them. This mode is mainly used on mobile devices, and is now more suitable for touch devices. The reintroduction of task and report group dividers, once temporarily introduced in the Universal 2024.3.12 release candidate. Extended display types for table tasks, table reports, prefilters, and cube views, which override the default display type for the action bars. For more information, see Display types in the Thinkwise Platform 2025.1 release notes. A more even distribution of space between buttons. The (Custom) action bars try to keep as many buttons visible as possible. If an action bar is configured with, for example, many Icon + text (> text > icon) buttons, it will first collapse all buttons to Text, then to Icon, and finally to the overflow, from far to near. Contrary to the Toolbar, the (Custom) action bars do not display prefilters both in the bar and in an overflow to the right of the prefilters. This saves screen space. However, it is possible to place prefilters in the overflow menu. Note that the prefilter overflow menu has been removed, there is only one overflow menu at the far end of the action bars.Custom CSS changedThe new action bars come with changes to your custom CSS; the styling has been improved, possibly making your custom CSS obsolete.Note that the HTML structure, CSS classes, and data test IDs have changed, making your CSS selectors mostly unusable for the action bars. This applies to all parts of the selector, for example: div[data-testid=”toolbar”] > div > .icon > svg.We recommend using the default styling.For an overview of the changes:Differences between the test IDs for toolbars and the new action bars: Area Toolbar test ID Action bar test ID Notes General toolbar actionbar     start-toolbar -     - actionbar-near     - actionbar-far     toolbar__overflow-menu -     toolbar__overflow-menu__button actionbar__overflow-menu__button The action bar has only one overflow menu. It is located action bar-far for far buttons, or else in action bar-near. Search search-toolbar__search actionbar__search__input   Prefilters prefilter-toolbar-group-0__<prefilter id> prefilter-actionbar-group-0__<prefilter id> The number (index) differs based on the button visibility   prefilter-toolbar-section -   CRUD crud-toolbar__add actionbar__add     crud-toolbar__copy actionbar__copy     crud-toolbar__edit actionbar__update In action bars, Edit buttons are always hidden in ​​default editable subjects   crud-toolbar__delete actionbar__delete     crud-toolbar__save actionbar__save In action bars, Save buttons are always available in default editable subjects    crud-toolbar__cancel actionbar__cancel In action bars, Cancel buttons are always available in default editable subjects    crud-toolbar__refresh actionbar__refresh   Tasks Reports task-toolbar-section report-toolbar-section -     toolbar__task__<task id> toolbar__report__<report id> actionbar__task__<task id> actionbar__report__<report id>   Cube views cubeview-toolbar-section -     toolbar__cubeview__<cube view id> actionbar__cubeview__<cube view id>   Extra actions in the overflow menu - actionbar__overflow-menu__context     toolbar__overflow-menu__item__quickfilter__icon actionbar__quick-filter     toolbar__overflow-menu__item__filter actionbar__filter     etc. etc.           Note: hidden buttons are no longer rendered. This is not relevant for styling but is relevant when test IDs are used in automated tests. For example, when adding rows is forbidden in the subject, the Add button was available in the Toolbar, but not shown. In the (Custom) action bars, the button is not in the DOM (Document Object Model) at all. *The new Action bar; on the left shows more buttons on the same screen size than the old Toolbar; on the right* Screen areas to assign actions to screen componentsnew changeAs of Thinkwise Platform release 2025.1, Detail groups have been renamed to Screen areas.You can use these Screen areas to assign actions to Action bars and Custom action bars and mark them as fallbacks for all unassigned actions. This allows you to divide actions across multiple bars or make the most important actions stand out in a screen type. You can assign a screen area to the following types of actions in the (Custom) action bars:Tasks Reports Cube views PrefiltersIn the screen type, you can assign the same screen area to task and report tiles, and to task, report, prefilter, and cube view bars. Here, you can also select whether the tiles or bars should be used as fallbacks. You can reuse a screen area multiple times in a screen type, allowing tiles and buttons to be available more than once on a screen. This also applies to the fallback mechanism: a table task, table report, cube view, or prefilter can fall back to multiple bars or tiles.Screen areas remain available for details, the only difference is that a detail tab is placed on a subject only once, whereas actions can be duplicated.For more information, see Screen areas also for tiles and bars in the Thinkwise Platform 2025.1 release notes. Support for default expand grouped gridCommunity idea newIt is now possible to set a grouped grid to be default expanded. When the setting Default expanded has been enabled, you can set the level of groups that will be expanded by default (menu User interface > Subjects > tab Default/Variants > tab Settings > group Grid). For example, if you enter '3', three nested groups deep will be expanded by default.Note that the group and all its parents containing the active row are always expanded, even if the expansion level is set to '0'.For more information, see User interface - Setting for expanding grouped grid in the Thinkwise Platform 2025.1 release notes. Support for disabling multirow selectionnewA new setting is available for enabling or disabling the possibility for users to select multiple rows in the grid. The setting is called Multirow selection enabled and is available in the menu User interface > Subjects > tab Default/Variants > tab Settings > tab General.Disabling multirow selection ensures that the following actions are performed on a single row: Task, Mass update, Delete, Export.For more information, see User interface - Multirow selection in grid in the Thinkwise Platform 2025.1 release notes. Support for collapsible form sectionsnewIn the Universal GUI, form tabs are not implemented because forms can extend indefinitely vertically. Instead, new tabs are interpreted by the Universal GUI as new sections. For example, the Trace info in the Software Factory is displayed as a tab in the Windows GUI, but in the Universal GUI, it is implemented as a section.For all supported Thinkwise Platform versions, the form sections can now be collapsed or expanded by users.As of Thinkwise Platform version 2025.1, you can use the Software Factory setting Default Expanded to specify whether a section should be expanded or collapsed by default. For this setting to work, the first column in a section must have the setting Field on next tab page enabled.Sections without a Tab page label to explain the information available in the section cannot be set to default collapsed, neither in the Software Factory nor via user preferences.For more information, see User interface - Collapsible sections for Universal GUI forms in the Thinkwise Platform 2025.1 release notes.Check the test ID for `<section>`For custom CSS, the data test IDs are unchanged.Note that the <section> element with the editors in it is now wrapped with some additional <div> elements brought up by the collapse panel. You may need to update your selectors for that.The test ID for the <section> element is form-section__<first editor column name>. Support for calculated cube fieldsnewCalculated cube fields are fields that are not directly available in the database but are calculated based on other cube fields. They are evaluated on cells and (sub)totals after intervals have been applied to dimensions and after values have been aggregated.In the Software Factory, you can now create calculated fields by selecting the aggregation type SQL Expression (menu User interface > Cubes > tab Tables > tab Default/Variants > tab Values > tab Form). The Universal GUI will fetch and display these fields in pivot tables and charts like any other aggregation type.For more information, see User interface - Calculated cube fields in the Thinkwise Platform 2025.1 release notes. Row visibility in the gridchangeWe have enhanced the way active, selected, and hovered rows are displayed in the grid:Row highlighting - The active, selected, and hovered row colors now use a gradient based on the main color selected for your theme in the Software Factory instead of a gray shade. Error indicators - Cells with errors are now more clearly highlighted for better visibility. Active row design - The indicator at the beginning of the active row has been removed for a cleaner look.*The new row highlighting in the Universal GUI**The new error indicator in the Universal GUI* Security updatenewWe have fixed the following security advisory: GHSA-mmhx-hmjr-r674.This resolves a security issue affecting some areas where HTML is displayed in the Universal GUI, including:HTML control (view-only mode) Preview component displaying an HTML field Prefilter, task, and report button tooltips Column, report, and task column tooltips Tooltips for grid headers Maps marker popupsIf a malicious actor were to inject an HTML value into one of these areas, such as through the Indicium API, this vulnerability could be exploited. In such a case, if a user had one of these elements visible, the attacker's JavaScript payload could be executed. In the worst-case scenario, the attacker could execute Indicium requests using the victim's credentials.Thanks to Indicium's Content Security Policy, the risk of exploitation was low. In addition, we strongly recommend always configuring Security headers. Minor fixes and tasksFor hierarchical trees without grouping, the conditional layouts were not applied the first time the user entered the screen. This has been fixed. Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!