Product Updates

Hi everyone!We’ve released the following platform improvements this week: SF 2025.3, 2025.220251016 - Assign rights PK error on menus In the event that a menu group and menu item had the same name, the process to assign rights had the potential of throwing a duplicate key error upon assigning rights. This has been fixed.   SF All supported versions20251014 - Keep authentication fields with parameter value when exporting model When exporting models, sensitive data, such as API keys, is omitted from the model.dat. However, if you were using parameters in Web connections for such fields, the value would still be replaced, therefore interfering with the Web connection functionality. This has been fixed.

Hi everyone!We’ve released the following platform improvements this week: SF 2025.3, 2025.220251009 - Synchronization cache procedure clean up Due to an oversight, records in a used temporary table could be deleted when they shouldn't. New task/report variants that were created on task/reports that already have variants could experience issues in IAM regarding rights. We have added the missing task and report variant ID field to the clause for integrity reasons, ensuring that only the correct records are deleted.

Hello everyone,In this release, we have added support for using a managed identity to connect to an Azure SQL Database from an Indicium Linux Web App. Furthermore, we have improved the usability of system flows and made some minor fixes.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.3.10 here. ContentsAbout Indicium New and changed Linux Azure Web App now supports managed identity Process flow monitor can now start system flows from IAM meta source Minor fixes and tasks Questions or suggestions? New and changedLinux Azure Web App now supports managed identitynewYou can now configure Indicium to use the managed identity to connect to the Azure SQL Database. To configure this, open the Web App in the Azure Portal and enable System assigned identity in the Identity screen.Configure Indicium to use this managed identity by adding the following settings to the appsettings.json file (or environment variables):"MetaSourceConnection": { "Server": "<server>", "Database": "<database name>", "UseAzureActiveDirectory": true}For more information see Azure Active Directory as pool user. Process flow monitor can now start system flows from IAM meta sourcechangePreviously, you could only start system flows from the Process Flow Monitor from the Software Factory meta source. Since the Software Factory is typically not available in acceptance or production environments, this limited usability. With this update, you can now start system flows from the IAM meta source in the Process Flow Monitor. Minor fixes and tasksDB2 In a previous release, we added CLOB support for DB2 using the new DB2 Core driver. This is now also implemented for the older iSeries driver. Fixed an issue where the OpenAPI endpoint did not work correctly when the model contained a view without a primary key. Note that the platform still requires every view to have a primary key. This is enforced through a validation in the Software Factory. Previously, when you exported date and time columns from a grid to Excel, the format would differ from the user's settings in the Universal GUI. This has been fixed. Fixed an issue that caused export queries to fail when sorting was applied but there was no pagination.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 the ability to filter on text columns in the grid header. Furthermore, we have improved the behavior of the 'User preferences' pop-up and fixed some minor 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.3.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.3.10 here ContentsDemo Universal GUI version 2025.3.10 New and changed Filter on text columns in grid header Updated behavior for 'User preferences' Minor fixes and tasks What we will be working on next sprint Questions or suggestions? New and changedFilter on text columns in grid headernewYou can already filter several value types from the grid header in the Universal GUI. A filter lookup appears when you select the three vertical dots in a column grid header. Using this allows you to filter on columns with checkboxes, dropdowns, and lookups.We have now extended this functionality to include (normal) text columns. The filter lookup displays all possible values from the selected dataset for these column types. When the number of listed items exceeds the threshold of 25, an auto-complete editor is shown. You can then type a search criterion to filter the available options and select values from the filtered list. The filter is applied when the filter lookup is closed.The filter menu displays a maximum of 25 items. You can adjust this number by using the extended property LookupGridHeaderFilterOptionsLimit.  Filter in a column with checkboxes Updated behavior for 'User preferences'changePreviously, when you changed only the Density or Theme in User preferences, the whole page would reload. We have changed this behavior, so the page is only reloaded when changing Language, Date format, or Number format. Minor fixes and tasksIn a previous release, we added support where a specific column would be focused when you opened the filter pop-up. In some cases, this did not work yet for lookup-type columns during initial load. This has been fixed. When opening a subject from a deep link URL or reloading the browser with a subject open, user-defined prefilters could be disabled or the dataset could keep loading unexpectedly. This has been fixed. Fixed an issue where clicking a lookup link in the grid opened the lookup popup for the active record instead of the clicked record. What we will be working on next sprintThe next sprint we will be working on:Filter bar screen component. Grid header filtering on numbers and amounts. Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

 This release takes a significant step in modernizing the Universal GUI. Applications now feel closer to native mobile apps, with support for push notifications and advanced localization for language, date, and number formats.Users can now save advanced filters as prefilters in the Universal GUI, making it easier to reuse complex filter setups. In the Intelligent Application Manager, the Authorization and Web domains screens have been further refined to improve usability.To support developers, we have added the ability to generate unit tests with AI, significantly speeding up the creation of test cases. In addition, you can now use any OpenAI Compatible LLM with the Thinkwise Platform, including self-hosted models.We have also added several quality-of-life improvements:Creating new branches or models directly from the Switch branch pop-up Automatic copying of program objects when creating a new branch More efficient handling of base models during model import Extended import options for Thinkstore models Automatic copying of translations for task and report parametersAn important addition for Administrators and Developers alike, is the Slow Query Log in IAM. This feature provides visibility into all queries exceeding the Query runtime threshold, which is set to 200ms by default. And while not strictly related to Platform release 2025.3, we would like to highlight the significant UI styling and data density changes that we introduced with Universal GUI 2025.2.13 onwards, as well as the introduction of the Debug center with Indicium 2025.2.13.Lastly, we would like to remind you that this release (2025.3) is the last LTS release to support the 2-tier architecture. The 3-tier architecture is much more secure and stricter regarding the quality of your model. If you are still working in a 2-tier environment, fix all findings in validations and smoke tests to prepare for the transition to a 3-tier environment. More documentation to support your transition will become available soon.This release includes 12 community ideas representing 254 votes. The most popular ideas are: A full overview of all release notes is available at  Thinkwise Platform 2025.3!

Hi everyone!We’ve released the following platform improvement this week: SF 2025.220250929 - Assign process flow performance optimization When authorizing complete process flows and their underlying objects, it could take quite some time for all objects to have their rights granted. We have improved the enrichment process that addresses this, significantly enhancing its performance.

September 29, 2025Full release (from release candidate 2025.2.13) Additional fixes in this release: Fixed an issue where images in the radio buttons in the release candidate (2025.3.13) were invisible. An issue occurred in grids when fields had grouped labels combined with pinned columns that did not fit in the available space. This caused an error, which prevented row switching from working as intended. This has been fixed. Resolved an issue where editable pivot grids would not focus on the first editable cell. Note the following: Editable cells are only focused if visible on the screen. Editable cells that belong to collapsed groups are not focused. You can now use the keyboard to navigate between a pivot grid's editable cells: Enter - moves the focus to the next editable cell in the same row within the pivot grid. If there are no more editable cells in the current row, the focus will move to the first editable cell in the next row. Shift+ Enter - moves focus to the previous editable cell in the same row. If there are no previous editable cells in the current row, the focus will move to the last editable cell in the previous row.  Hello everyone,With this Universal release we are introducing impactful, long-awaited updates to the Universal UI styling and Data density! Most notably the Outline style for Form fields and displaying the Lookup value as a hyperlink (in Read mode). All Controls are slightly smaller in height, compared to the previous styling. The most important implications are the following:Form field height is reduced, resulting in more data density on the Form Default Grid row height is reduced from 36px to 28px, resulting in more data density on the Grid Grid row height is now also respected for Editable grids. Control buttons are properly display up until a minimum Row height (px) of 20 pixels. Field labels are no longer enlarged in empty fields Lookups in Read mode are displayed as hyperlinks and now also available on a Grid in Read mode Mandatory indicator (*) is now shown at the beginning of the label instead of the end to ensure it won't fall out of sightAs a result the following Ideas are marked as Completed:These changes have made the extended properties useFormFieldBackgroundColor and DisableGridRowHeightSafeguards obsolete. Support for these is removed. 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.2.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.2.13 here ContentsDemo Universal GUI version 2025.2.13 Breaking Support for Thinkwise Platform release 2023 has ended Removed the useFormFieldBackgroundColor configuration option Debug center available in profile menu Filter multiline value types in grids Drag-and-drop upload support for file and image controls Updated layout for radio button controls Improved conditional layout for resource columns in Scheduler Improved form and grid styling Clickable hyperlinks for read-only fields Improvements to cursor placement in filter pop-ups Changed display order of prefilters Improved tile texts Improved breadcrumbs Minor fixes and tasks What we will be working on next sprint Questions or suggestions? BreakingSupport for Thinkwise Platform release 2023 has endedbreakingIn accordance with our Lifecycle Policy, the Universal GUI support for Thinkwise Platform releases 2023.1, 2023.2, and 2023.3 has ended.Upgrade to at least Thinkwise Platform version 2024.1. Removed the useFormFieldBackgroundColor configuration optionbreakingWe have removed the configuration option useFormFieldBackgroundColor. This option could be enabled or disabled to control whether form fields had a background color or not, for both editable and non-editable fields.We now use the 'outline' field style, meaning that all form fields get a border. Non-editable fields can still have a background color. Both colors can be configured with custom CSS.Check your custom CSS We cannot guarantee compatibility with your current custom CSS.The classes filled-input and filled-style have been removed from the Universal GUI because they were used for the removed configuration option useFormFieldBackgroundColor. We have made various changes to the DOM structure to enable outlined fields.Custom CSS example with the new styling (background colors for disabled and read-only fields, outline color for mandatory fields):Background colors are set for disabled and read-only fields, and the outline color is set for mandatory fields. /* Background color for non edit mode inputs */ .tsf-control.disabled { background-color: pink; } /* Background color for Read Only inputs */ .tsf-control.read-only { background-color: purple; } /* Outline color for mandatory fields */ .tsf-control.mandatory .tsf-control-outline { border-color: fuchsia; } To set no color, use: .tsf-control.tsf-control { background: transparent; } Outlined fields, the non-editable fields have a different background Debug center available in profile menunewThe Debug Center was introduced in the Indicium release 2025.2.13. It combines the Error log, the Database Event Log and the Process Flow Monitor into one centralized page with a new look and feel. By selecting Debug Center from the profile menu in the Universal GUI you can access the Debug Center directly. Alternatively, you can access it through the Indicium url (for example, /indicium/account/ui/login). Access the 'Debug Center' from the profile menu Filter multiline value types in gridsnewYou can now filter columns that contain multiline values in a grid. To do this, select the three vertical dots in a column header. The menu is automatically available if the column contains multiline values. In the pop-up, enter a query in the field Contains. Close the pop-up to apply the filter.Filter multiline values in a column Drag-and-drop upload support for file and image controlsnewPreviously, files for file and image domain controls could only be uploaded by selecting the corresponding icon in the Universal GUI. You can now drag files for the following domain controls to upload them:FILE LINK FILE UPLOAD IMAGE LINK IMAGE UPLOAD Updated layout for radio button controlschangeThe Radio button control now follows the setting Field height in positions.Previously, a Radio button control distributed all radio options over a maximum of two columns. This sometimes caused options to be out of sight. For example, a radio button with the Field height in positions set to '2' would show a maximum of 6 options, with three options under each other in two columns.Radio buttons were previously displayed in columnsWith this release, all radio options are now displayed according to the number of rows specified in Field height in positions, and distributed over a dynamic number of columns. A radio button with the Field height in positions set to '2' will now show a maximum of two options under each other, displaying them in as many columns as necessary.This improvement ensures that all radio options are always visible, but it may reduce their readability. Therefore, review your screens to avoid situations such as the one below. In this situation, the Field height in positions is set to '2', but the options have become unreadable. You can resolve the issue by setting Field height in positions to '3'.Review screens using radio buttons, as options may become unreadable Improved conditional layout for resource columns in SchedulerchangePreviously, when you applied a conditional layout for a subject to a scheduler resource, it was applied to all scheduler resource columns for a table instead of the selected one, even if the selected column was not visible.Now, the selected column to which the conditional layout is applied is no longer ignored. So, no conditional layout will be shown if the column is not the Group by column that is visible in your application as the resource for the schedule.To configure the conditional layout for a subject: go to the menu User interface > Subjects > tab Data > tab Conditional layout, select Show conditional layout, select a Column, and select Apply to Scheduler resource. To configure the Group by column: go to the menu User interface > Schedulers > tab Tables > tab Scheduler, and select a column in the field Group by column.When conditions are evaluated, only the first matching record per resource is considered to determine which layout is applied. Additional matching records are ignored.As of Thinkwise Platform release 2025.3, you can set multiple resource columns for a scheduler, increasing the amount of information for a resource. From that release onward, it is possible to apply a conditional layout to any of the selected resource columns. Improved form and grid stylingchangeThe form fields and grids have been redesigned to a more compact look and feel. With this change, you can now lower the grid row height to as little as 20px.For more information about this change, see Form fields – Outlined style in the Community blog "Styling update of the Universal GUI".Example of the new design for grids, with the lowest possible row height configured  Clickable hyperlinks for read-only fieldschangeThe lookup control is no longer displayed as a clickable icon for read-only fields in grids and forms. Instead, the field text is now a clickable hyperlink to the lookup pop-up.The clickable hyperlinks behave as follows:In grids, when a row is active or hovered, the lookup text is styled with the Accent color. When hovering over the lookup cell, an underline appears to indicate interactivity. Empty look-ups show a placeholder: 'Nothing selected' which is also clickable.These changes apply only to read-only grids and forms. Editable grids and forms remain unchanged.A clickable hyperlink is shown instead of a lookup control Improvements to cursor placement in filter pop-upschangeWe have improved the cursor placement when you open the filter pop-up in grids and forms. Now, when opening the filter pop-up, the cursor is automatically placed in the column's filter condition that matches the active field of the related subject. In grids and forms, the active cell determines in what filter condition the cursor is placed. For example, when you open the filter pop-up when 'Employee' is selected, the cursor is placed in the filter condition 'Employee'. This behavior only applies to default editable forms; it does not apply to non-default editable forms. Changed display order of prefilterschangePreviously, the Universal GUI displayed user-defined prefilters after the model-defined prefilters in the action bar. To improve visibility, user-defined prefilters are now displayed at the start of the action bar. This makes it easier for users to find and apply their custom filters. Improved tile textschangeWe have improved the tooltip and text truncation behavior for tiles:Menu tiles - When text is truncated, hovering over a menu tile will now show a tooltip containing the full text. Menu tile with tooltip   Detail tiles - A tooltip with the full text will now be shown when hovering over a detail tile. Detail tile with tooltip  Task tiles - The tooltip would sometimes not be shown when no custom tooltip text was defined. This has been fixed. Now, tooltips are always shown on task tiles, even when no custom tooltip text is defined. In those cases, the tooltip displays the translated title. All tiles - When tile text was truncated with an ellipsis (…), the top of tall characters (such as “h”, “i”, “}”) would incorrectly appear on the next line. This was a rendering issue and has been resolved.   Fixed text truncation in tiles Improved breadcrumbschangeWe have made the following changes to the breadcrumb behavior: Previously, the breadcrumb would disappear from the top bar if you did not select any row. Now, it displays a dash ('-') at the end when no row is selected, indicating that no selection is made.   Breadcrumbs now display a dash where no row is selected  When you add a new row, the breadcrumb now displays the label 'New row' at the end. This label is translatable and will reflect the user's preferred language settings. Breadcrumbs now display 'New row' when a new row is being added   In cubes, the breadcrumbs now display the cube view name. Breadcrumbs now display the cube view name  Minor fixes and tasksFixes for aggregations in grids:When the Aggregation type is Max, "5e-324" was wrongly shown in some cases. When the Aggregation type is Min, "1.7976931348623157e+308" was wrongly shown in some cases. When the aggregation value is "0", it was not displayed.Fixes for icons:We removed the width and height attributes from .svg images in the Image combo domain to prevent icons from being displayed at incorrect sizes. We fixed the misalignment between the selectable icons and the main field of the Image combo domain.Other fixes:Previously, if a user changed the Language in Profile menu > User preferences, it could take up to a minute for Indicium to apply the new setting. During this time, users continued to see messages in the old language. We have improved the functionality so Indicium now updates immediately when a user changes their language preference. This ensures a smoother and more consistent experience. When a whole row was set to read-only in a grid, the layout checkboxes appeared to be editable even though they were not. This has been fixed. Resolved an issue when using defaults in combination with layouts on checkboxes in a grid. In this case, clicking rapidly on the checkboxes caused the Universal GUI and the backend to lose synchronization. Previously, when entering an incomplete date in a date/time field, the Universal GUI cleared the field. Now, when you partially enter a date into an empty field, the Universal GUI automatically completes the entry with today's date and time. For example, when you enter the day '9', the current month and year are automatically added to the field. The time defaults to 0 minutes and 0 seconds. Fixed an issue where the settings Apply to cell, Apply to total cell, Apply to custom total cell and Apply to grand total cell were not applied correctly in conditional layouts for cube views. Resolved an issue where, in cases with many dimensions and few values, the pivot grid incorrectly added Other columns to the series.  What we will be working on next sprintThe next sprint we will be working on:Filter bar screen component. Extended filtering support for grid headers. Improvements for initial focus and navigation for editable pivot grids. 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: IAM 2025.2, 2025.1, 2024.3, 2024.220250923 - IAM synchronization improvement When synchronizing from the Software Factory to IAM, the data does not contain the model_id and branch_id of the synchronized model. This is because it is possible to synchronize using a difference branch name. However, when IAM receives this data, it incorrectly assumed the model_id and branch_id were present in the XML data, resulting the MERGE statement to always remove all present data and insert all synchronized data as the model_id and branch_id (null/null) did not match. This has been fixed.   SF 2025.220250924 - Fix object assignment for copy unit test task When copying a unit test to a different object, the object assignments of the input and output parameters were incorrect. After copying, the input and output values could not be modified due to the difference in object assignment. This platform improvement will fix all current mismatches as well as correct the copy unit test task.  

This is an additional release for the Universal GUI version 2025.2.12.We fixed an issue that sometimes caused the wrong tab to be activated when going into add or edit mode. Also when you go into edit mode, the focus will remain on the column you already had active in the grid. We also fixed cursor to col for column that were outside of the view in the grid.The 2025.2.12.3 release is now available for download in TCP.

Hello everyone,In this release, we are excited to introduce the new Debug Center, which consolidates essential debugging tools into a single, user-friendly interface. This enhancement simplifies troubleshooting, allowing you to trace issues quickly and efficiently. Furthermore, we have applied updated styling to several pages, ensuring a consistent and modern look across the platform. We have also made other minor improvements, such as adding icons for attachments in the email previewer.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.2.13 here.ContentsAbout Indicium New and changed Introducing the Debug center Updated styling for several pages Email previewer shows icon for attachments New session variable available for user language Questions or suggestions? New and changedIntroducing the Debug centernewWith this Indicium release, we introduce the Debug Center. It brings together the Live Error log, the Database Event Log and the Process Flow Monitor into one centralized page with a renewed look and feel. This integration makes it easier to trace issues across application layers, without switching between different pages. The new design aligns with the Universal GUI and the recently updated login pages. You can access the Debug center via the profile menu in the Universal GUI, or via the Indicium landing page (section Debug Center).The Debug Center provides easy access to essential debugging tools  Updated styling for several pagesnewAs part of this release, the License, User simulation pages have been updated to match the new login page styling. We have also updated the Indicium landing page as well, to ensure a consistent look and feel across all pages. New styling of 'License' and 'User simulation' pages Updated Indicium landing pageEmail previewer shows icon for attachmentsnewWe have enhanced the email previewer to display icons for common file types attached to email files (.eml and .msg) .Previously, attachments were listed without any visual indication of their type, making it harder for users to quickly identify them. The previewer now shows icons for the following file types:PDF (.pdf) Excel (.xls, .xlsx) PowerPoint (.ppt, .pptx) Word (.doc, .docx) ZIP (.zip) Images (.jpg, .jpeg, .png) Text (.txt)Email previewer with icons for attachments New session variable available for user languagenewThe session variable tsf_appl_lang_id contains the user's selected language, but the variable is overwritten by the application's fallback language when the chosen language is unavailable.We have introduced tsf_global_lang_id as a new session variable that is not overwritten by the application's fallback language. This ensures the user's original language preference is always preserved, even if the application falls back to another language. Questions or suggestions? Questions or suggestions about the release notes? Let us know in the Thinkwise Community! 

Hello everyone,In this release, we have introduced a new solution to the Thinkstore, the Process queue. This solution is especially useful when you need to run processes asynchronously in the background, such as generating management data or sending data to external systems.The changes in this release are available for Thinkwise Platform version 2025.2 and higher. 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 Enrichments > 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. Thinkwise Process queuenewYou can now download and install the Process queue from the Thinkstore. This solution offers an asynchronous queue that controls the execution of processes, so you no longer need to use database triggers. You can now invoke processes that integrate web connectors, application connectors, and other advanced functionalities without affecting the integrity or performance of the database.The Process queue is especially useful for asynchronous background processes, such as:Generating (management) data. Sending data to external systems. Processing uploaded files.You can read more about this solution in the Process queue guide. 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.2.12.We fixed an issue that caused tab pages with editable grids to sometimes switch unexpectedly when you began editing. The tab you’re working in will now stay active as expected.The 2025.2.12.2 release is now available for download in TCP.UPDATE 18-9-2025: This fix introduces another problem, the GUI won’t navigate from Grid to Form when both are on different Tabs and someone is trying to Add a new record from the (non-Editable) Grid tab. Therefore we have disabled the ability to download it from TCP.

This is an additional release for the Universal GUI version 2025.2.12.We have fixed clicking on group nodes of the hierarchy tree not changing the active record and not updating related detail data.This was caused by changes in the 2025.2.12.0 release.The 2025.2.12.1 release is now available for download in TCP.

Hi everyone!We’ve released the following platform improvements today: SF 2025.2⚠️ 20250908 - Prevent origin model version update when merging unrelated branch When merging an unrelated branch to another branch, the origin model version may be updated unintentionally. This can cause some issues when merging the targeted branch to its origin, as modifications are overlooked due to the origin model version being moved. This has been fixed. It is recommended to install this hotfix with priority.   SF - All supported versions (2025.2 <->2024.1) 20250908 - Remove calculated datatypes from insert and update handlers For SQL Server models, Insert and Update handlers defined parameters with calculated datatypes, which was not intended to happen. From now on, columns with calculated datatypes are excluded. This means that columns using the datatype ROWGUID and ROWVERSION are no longer added to the handler definition.   SF - 2025.2, 2025.1, 2024.3 20250909 - Fix cleanup for history Earlier we had disabled parts of the clean-up history data task due to the possibillity of system-versioned tables being unlinked in case of the process being stopped abruptly, leading to potential model integrity issues and merging issues down the line. We have addressed this and fixed this. This means that even if the process is stop abruptly, the system-versioned tables will stay linked with their history table.  The clean-up part has a maximum run time of 3 hours and currenly cannot be tweaked in the model. You can rerun the task from the Advanced menu > Software Factory > Clean-up model history

September 1, 2025Full release (from release candidate 2025.2.12)Hello everyone,As of this release, users can filter Boolean value types (true/false/null) in grids. We have also made significant improvements to pivot grids, grouped grids and grid navigation. Furthermore, we have added badge icons in menu groups to help users notice updates or alerts and added clickable hyperlinks for read-only fields.This release contains some breaking changes, such as the removal of support for legacy browsers and devices. 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.2.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.2.12 here ContentsDemo Universal GUI version 2025.2.12 New and changed Badge icons added in menu groups Export pivot grid to Excel or CSV Improvements for pivot grid and grouped grid New filter for Boolean value types in grid Shortcuts for page navigation Tile group titles truncated when too long Minor fixes and tasks What we will be working on next sprint Questions or suggestions? New and changedBadge icons added in menu groupsnewThe Universal GUI now displays a dot badge whenever one or more items within a menu group have a badge. This helps users notice updates or alerts, without needing to expand each group individually. The dot badge is automatically removed when none of the items in the menu group have a badge. Dot badges indicate if items within the menu group have active badges Export pivot grid to Excel or CSVnewYou can now export the active pivot grid to Excel or CSV format. The Export option is available in the separate Cube view bar for versions lower than 2025.1, or as part of an action bar.To make Export visible in the action bar, the following conditions must be met:The underlying table used for the pivot grid allows exporting. The screen type contains a pivot grid.When you export a pivot grid:Domain element fields are exported as displayed in the pivot grid, including their translations. Numeric fields are exported as raw numbers without their regional formatting. Date fields are exported as raw values without their regional formatting. Only visible data is exported, underlying values in collapsed groups will be excluded in the export. Exporting a pivot grid to Excel or CSVKnown issueIf Show total for rows is disabled, then exporting a cube view will only include rows that belong to the innermost grouping level. Parent group rows will not be included in the export.  Improvements for pivot grid and grouped gridchangeWe have made the following improvements to pivot grids and grouped grids: Pivot column totals - You can now hide the extra row showing column totals by clearing the checkbox Show total for columns in menu Cubes > Cube views > Pivot settings in the Software Factory. Users can also toggle this option from the Pivot settings pop-up in the action bar in the Universal GUI. This allows more data to be displayed in the same space.    Side-by-side comparison of row totals   Row totals are hidden  Row totals are shown    Loading indication - When a pivot grid is being loaded, the pivot now shows skeleton loaders instead of rotating cogwheels. Header text wrapping - Previously, if the pivot header text did not fit within the column width, it would be cut off. The header text now wraps over multiple lines.And for grouped grids: Non-grouped data - In grouped grids, non-grouped data is now aligned with the same level of indentation as grouped data, so more data can be displayed.Side-by-side comparison of non-grouped data display Before, non-grouped data was displayed with more indentation  Now, non-grouped data is aligned with the same level of indentation as grouped data  Group labels - The border between regular header labels and empty group labels has been removed. Furthermore, we corrected a slight misalignment between the header and group label. Lastly, when scrolling horizontally, group labels are kept in view.   Group labels are kept in view when scrolling horizontally  New filter for Boolean value types in gridCommunity idea newIt is now possible to filter Boolean value types (true/false/null) for checkboxes in grids. This was also possible in the Windows GUI.When a user hovers over a column containing Boolean values, three dots appear that indicate that the column can be filtered. When selected, a pop-up opens that allows them to select which information they would like to see in the grid. Shortcuts for page navigationnewWe have added shortcuts for navigation in paginated grids.In a grid in non-edit mode, with only one row selected: ↑ (arrow up) or Page Up - when on the first row, go to the previous page. ↓ (arrow down) or Page Down - when on the last row, go to the next page.In a non-default editable TAB and NOT in edit mode, a grid, a card list or a form, with the focus on a component:Alt + Page Up - go to the previous page. Alt + Page Down - go to the next page.Where page navigation is available, tooltips are shown for the footer pagination arrows.< Previous Page - tooltip: "Previous page (Alt + Page Up)" > Next Page - tooltip: "Next page (Alt + Page Down)" Tile group titles truncated when too longchangeTile group titles that are too long are now truncated with an ellipsis (…) instead of being placed on a new line. The full title is displayed in a tooltip.A tile with a truncated title and the full title in the tooltip Minor fixes and tasksFor the pivot grid:Resolved an issue where clicking a cell in an editable pivot grid with more than two levels of nested categories could cause a crash. The crash would occur after expanding the deepest level. When the pivot field setting of a dimension was set to Default expanded, it would not be applied if the dimension was the top-level series or column. This has been fixed.For navigation URL stability:Fixed a crash that could occur after logging in again if the session expired while using a navigation URL. Improved error handling for invalid navigation URLs. Instead of a technical error message ('Cannot read properties of undefined (reading 'tab_id')), users now see a user-friendly message: 'This link is broken. If this is unexpected, please contact support.' When the Universal GUI was opened or refreshed via a navigation URL, the translation of opened documents would be incorrect (e.g., “Customer” instead of “Customers”). This has been fixed.Other fixes:Applying a conditional layout without conditions to a scheduler resource would lead to a crash. This issue has been fixed. Resolved an issue where values entered in an active Form control were not saved if a user immediately interacted with a Signature control afterward. Fixed an issue where resizing a screen using the splitter could cause the Universal GUI to freeze. Users would sometimes get the error 'Dataset refresh not possible on a non-table context' when working within a modal pop-up screen. This has been fixed. When both Auto-edit and Auto-save were enabled, the search bar in the action bar would unexpectedly lose focus when typing. Furthermore, clearing the search input when no rows were available caused the focus to move to the first editable column. This has been fixed. Previously, the behavior of Ctrl + Shift + Click in a grid to select consecutive rows was inconsistent. It sometimes acted like Ctrl + Click when used on selected rows, meaning only the clicked row would be selected, and like Shift + Click when used on non-selected rows, meaning all rows between the last selected row and the clicked row would be selected. We have corrected this behavior. In a default editable grid with Auto-save enabled, the parent row did not change when you selected a different parent row immediately after changing a value in a child. This has been fixed. What we will be working on next sprintThe next sprint we will be working on:Additional Excel-filter types, such as text, numeric, date/datetime/time. Displaying lookups as links. Adding resource columns to the Scheduler (2025.3). Localization improvements (2025.3). Editor style improvements (outlined styling). Adding support for push notifications (2025.3). Adding the ability to save advanced filters as prefilters (2025.3). 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.220250829 - Task and report parameter look up rights During the refactor of rights assignment as implemented in the 2025.2 release, a small bit of functionality was lost. This became apparent when granting rights on either task or report parameters (Access Control > Roles > Tasks > Task parameters / Tables > Tasks > Task parameters / Reports > Report parameters / Tables > Reports > Report parameters). Any parameter that had a look-up reference to another table/column combination would not be granted because this was missing in the enrichment that is executed in the background.  This has now been fixed, meaning they will be included from now on and will also be visible when choosing the option to first review changes.

Hello everyone,In this release, we have made several improvements and fixes.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.2.12 here. ContentsAbout Indicium Minor fixes and tasks Questions or suggestions? Minor fixes and tasksOn the DB2 iSeries database platform, wildcard characters for LIKE conditions (% and _) were not escaped correctly but treated as wildcard characters instead of literal characters. This has now been fixed. SQL Server and Oracle were not affected by this issue. On the DB2 iSeries and Oracle database platforms, some constraint error message types were treated as unknown errors, causing a 500 error status code on the request and an entry in the error log. These errors are now correctly treated as known error messages that result in a translated message for users, with the ability to correct the cause of the error. If it took too long to log in on the Indicium login page, you would not be redirected back to the Universal GUI. This has been fixed. We reintroduced the background image for the root Indicium page. Unfortunately, it had disappeared after the new login styling of release 2025.2.10. 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: IAM 2025.220250821 - Improve i_ui_gui_appl loading time We have optimized parts of the i_ui_gui_appl view code to improve its speed. The opening of applications should now load much faster.   20250820 - Implement Tenant email template fallback to system email provider The From email address and From name fields did not fall back to the Tenant/System email provider settings for these fields. Whilst Indicium does automatically fall back to these settings, IAM now also does the same.

Hi everyone!We’ve released the following platform improvements this week: IAM 2025.2, 2025.120250812 - Fix history check iam models The check which determines the old models that should be cleaned-up within IAM had the potential to delete offline GUI applications without clean-up date. This has been fixed.

This is an additional release for the Universal GUI version 2025.2.11.We have added a minimum width to the filter popup to keep it comfortably usable and prevent it from shrinking to an impractical size. Besides this, long titles in the filter popup are now allowed to take up at most 2 lines and after that are truncated with an ellipsis to maintain a clean and consistent layout.The 2025.2.11.2 release is now available for download in TCP.

This is an additional release for the Universal GUI version 2025.2.11.Last sprint, we improved scrolling behavior on the Cardlist.When the initial dataset loads very slow and the Cardlist is already shown, this new logic could cause a crash. This is prevented now.The 2025.2.11.1 release is now available for download in TCP.

August 4, 2025Full release (from release candidate 2025.2.11) Additional fixes in this release: Resolved an issue where forms appeared editable in default edit mode, even though editing was disabled in the layout procedure by setting update_button_type to '1' or '2'. Previously, when the Accent color was set to white in light mode or black in dark mode, some buttons were invisible in the Sort and Export pop-ups. The same problem affected messages with custom message options. This has been fixed. When pasting content from Word into the HTML editor, unnecessary Word metadata would be retained, resulting in HTML fields taking up more space than necessary. The metadata is now removed, reducing database usage. A loading screen would remain visible after changing the Screen type by using the Screen type... button in the action bar, until the user opened or reopened the document, or reloaded the Universal GUI fully. This has been fixed.   Hello everyone,In this release we have introduced a loading pop-up for refreshing the model, changed the double-click behavior for records to match the Windows GUI, and made performance improvements when initializing forms. 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.2.11For more information about setting up the Universal GUI, see the Universal GUI setup guide.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.2.11 hereContentsDemo Universal GUI version 2025.2.11 Contents New and changed Load pop-up for refreshing model Changed double-click behavior for records Performance improvements Short-term-support platform version numbers in the 'About' screen Minor fixes and tasks What we will be working on next sprint Questions or suggestions? New and changedLoad pop-up for refreshing modelnew 2025.2.11When executing the task Refresh model from the profile menu, there was no visual indication that the action was in progress. A loading pop-up has now been added to indicate the status during the model refresh.*Loading pop-up for refreshing the model*Changed double-click behavior for recordschangePreviously, when double-clicking on a record in a lookup pop-up, the Universal GUI would navigate to the Form tab if there was one present. We have changed this behavior so that it matches the Windows GUI. Now, double-clicking a record will select the record and close the pop-up. This behavior only occurs when no double-click task has been assigned to the column that is double-clicked. If you have assigned a double-click task, then the task will be executed instead. Performance improvementschangeWe have improved the performance when initializing a form, especially when there are many form fields inside collapsed sections. In addition, the Search bar is now shown before the initial dataset is loaded. If the initial dataset takes a long time to load, users can start searching immediately, which will result in quicker data loading. In the future, the initial dataset request will also be canceled when a search is performed. Short-term-support platform version numbers in the 'About' screenchangeIn Thinkwise, we work with two types of platform version numbers: LTS (Long Term Support) and STS (Short Term Support). The LTS version is the main version that is supported for a longer period, while the STS version is a more frequent release that includes new features and fixes. Previously, only the LTS version number (for example: '2025.2') was displayed in the About screen. Now, the STS version (for example: '2025.2.11') is displayed.*Version numbers in the 'About' screen*Minor fixes and tasksWe have implemented some fixes for the Advanced filter pop-up: When applying a quick filter on a column with VisibleForFilter set to hidden, the fields are no longer shown in the filter pop-up. Filtering on lookup-type columns has been improved when a duplicate filter condition on the same column already exists. The filter pop-up now dynamically increases in width as groups are added. Rapidly clicking on the link x conditions opened the reference filter pop-up multiple times. This is prevented now, and when it takes longer to open, a progress dialog is shown. We have added support for DisableFilterOnDetail for platform versions 2025.1 and older to disable reference filtering. From version 2025.2 onwards, this control is available in the Software Factory: Visible for filter. The user could not open the Treeview because the icon's height was too high. This has been fixed. Fixed an issue where the Total position was set to Near. The pivot grid would show an expand row button on the grand total row instead of the last pivot row. When using the up and down arrow keys to navigate the editable grid in the Universal GUI, key inputs were occasionally ignored after multiple presses. This has been fixed. Fixed an issue where navigating to a specific row using the Go to row process action did not automatically scroll the card list to bring the selected row into view. When a detail containing a task was opened in a detail tab, switching records in the main subject and immediately navigating to the detail tab could result in the task executing with parameters from the previously selected record. We have fixed this by blocking tasks while the dataset is refreshing. When opening a detail screen as a zoom detail document, the badge count reset to '0' in the opened documents list. This has been fixed. Fixed an issue where the menu badge was incorrectly synced to the badge count of a detail. What we will be working on next sprintThe next sprint we will be working on:Grid header filtering on text, number, and checkbox type columns. Support for push notifications. Badges on open menu groups. Editor style improvements (outlined styling). Pivot grid: Export to Excel. Save advanced filters as prefilters (2025.3). Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

Hello everyone,In this release, we have removed support for Indicium 2023.1, 2023.2, and 2023.3 in accordance with our lifecycle policy. Furthermore, we have re-enabled script support in DevExpress reports, which was disabled in the previous release due to an upgrade of our reporting library.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.2.11 here.ContentsAbout Indicium Breaking Indicium 2023 deprecated New and changed Re-enable script support in DevExpress reports Minor fixes and tasks Questions or suggestions? Breaking Indicium 2023 deprecatedbreakingIn accordance with our lifecycle policy, we have removed support for Indicium version 2023.1, 2023.2, and 2023.3.Upgrade your Software Factory and IAM to version 2024.1 or higher. Check that your email provider is configured in IAM. See Email providers. The backwards compatibility code is no longer available in Indicium. New and changed Re-enable script support in DevExpress reportschangeIn release 2025.1.14.0, we upgraded our version of DevExpress (our reporting library). This had the consequence that reports with C# scripts started to fail. The error message you will see is:"DevExpress.XtraReports.ScriptExecutionException: Report scripts were found in the application while script execution is disabled."To solve this, we are now providing a toggle in the appsettings.json.WarningBy default, scripts are not allowed. DevExpress recommends keeping scripts disabled for security reasons. The alternative DevExpress provides is "Expression bindings". You can read more about it here: Data binding modes Only enable scripts in DevExpress reports if you are aware of possible security risks. Enabling scripts can lead to security vulnerabilities if not handled properly.If you nevertheless want to enable scripts, you can do so by adding the following to the appsettings.json: "Reporting": { "DevExpress": { "UnsafeScripts": true } } Minor fixes and tasksWe fixed an issue for DevExpress reports with parameters in combination with DB2. Fixed an issue where underscores could not be used in web domain based login. Specifying a non existent prefilter through the $prefilter query option will now result in a '400 Bad Request' response. Fixed an issue when using characters with diacritics in user provisioning. 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.220250724 - Multirow selection role rights fix When executing the Assign rights task while selecting multiple rows from either Task or Reports (Access Control > Roles > Tables > Tasks / Reports), rights were only granted for the first task or the first report of the selection. This has been fixed.   SF 2025.2, 2025.120250725 - Add change_log_id as sorting column of Code review When developing, control procedures may be modified and reviewed multiple times. After merging into the Origin, the Code review records are added to the Origin with a timestamp of the moment at which the merge session was executed.  The Code review screens sorts records using the 'Modified on' column. When merging, multiple records will be added simultaneously, which can cause records to be presented in an incorrect order, potentially confusing the developer. We have added the hidden unique Change log ID to the sorting to ensure the Code review records are always shown in the correct order.

This is an additional release for the Universal GUI version 2025.2.10.We have fixed the issue where, on a slow connection, a user could start tasks on the wrong record after switching rows and then tabs.