Product Updates

Hi everyone!We’ve released the following platform improvements this week: SF 2025.320251210 - Prevent adding meta view parameters when only comment lines In 2025.3, we have added example queries to many of the available query fields. If you were to add a Meta auto or Meta custom view, the examples would be added in the View code, causing syntax errors. This has been fixed.

This is an additional release for the Universal GUI version 2025.3.12.We fixed an issue where charts are not usable due to a watermark saying “license has expired".If you can not upgrade to this Universal version and need a hotfix on your current version, make sure to create a TCP ticket. We will then make a hotfix for you.We will be starting on replacing this third party component charts in the near future so problems like this cannot arise again.The 2025.3.12.1 release is now available for download in TCP.

Hi everyone!We’ve released the following platform improvements this week: SF 2025.320251124 - Link base model to work model using provided context The task to link a base model to a work model always used the user's session context to determine the values for the work model and work branch parameters. This meant that trying to link a base model to another work model would be unsuccessful. This has been fixed. IAM 2025.320251126 - Refresh web domain When changing configurations that would affect the web domain, the newest Indicium version will now be informed in more situations to reload the Web domain configuration, such as when changing an OpenID provider configuration. SF & IAM 2025.320251127 - Show table task and table report variant translations When using table task and table report variants, the translation shown would be that of the base object rather than the variant translation. This has only been fixed for 2025.3.

November 24, 2025Full release (from release candidate 2025.3.12) Additional fixes this release: When a Context procedure disables a detail tab when the detail tab page was already open, it was still possible to interact with the detail tab page.  This has been improved in the following ways: Styling: Higher opacity for the detail tab page Cursor indicates that clicking is not allowed in the detail tab page Elements within the detail tab do not have any hover styling Clicking: It is not possible to click on any of the elements in the detail tab page Tabbing: It is not possible to use Tab to navigate into the detail tab page Shortcuts: It is not possible to use (Task) shortcuts to trigger any actions within the detail tab page Process flows: Process flow actions that try to interact with the detail tab page, e.g. "Add Row", will be unsuccessful  This means that, if relevant, the red arrow of the process steps is followed. Editable Components The components within the detail tab page will never be in edit mode, even if they are set to "auto-edit" in "Subjects". We have fixed scrolling to the start or end of the Code editor and SQL editor resulting in scrolling stopping. If there is more content in the form scrollable, the form scrollbar will now take over. Keyboard shortcut to go to a row new You can now use the keyboard shortcut CTRL+G to open the pop-up Go to Row. In this pop-up, you can enter a row number to quickly navigate to that row in a Grid, Tree or Card list screen component.   Enter a row number to quickly navigate to that row  Hello everyone,In this release we have significantly expanded the column header filtering, allowing you filter more data types. We have added some nice-to-have features such as color pickers in the HTML editor and a keyboard shortcut to quickly navigate to a specific row. Additionally, we have improved the performance of pivot tables and made several minor fixes. Note that this release contains a few breaking changes, so make sure to check these out before upgrading. 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.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.3.12 here ContentsDemo Universal GUI version 2025.3.12 Breaking Dropped support for legacy browsers and devices Grid conditional layouts without conditions will now be applied Changed data-testids for Excel-style filters Changes to 'GROUP HEADER LABEL' and 'LABEL' controls New and changed Added data types to column header filtering Color pickers for HTML editor Added functionality for custom components Action buttons Expand all/Collapse now work for grouped Grids too Version check performed before login Improvements for pivot tables Updated order of buttons for Schedulers Minor fixes and tasks What we will be working on next sprint Questions or suggestions? BreakingDropped support for legacy browsers and devicesbreakingAs part of our modernization work, we have removed a legacy code compatibility transformation to improve performance, maintainability, and future compatibility.In line with our lifecycle policy, we are dropping support for iOS versions below 16.4. This means the following devices are no longer supported:First-generation iPhone SE iPhone 6s and 6s Plus iPhone 7 and 7 Plus Seventh-generation iPod TouchUsers on these devices may experience degraded functionality or may no longer be able to access the application. Additionally, older browsers are now more likely to crash. We strongly recommend using a recent browser on a supported device to ensure continued access and optimal performance.Grid conditional layouts without conditions will now be appliedbreakingJust like the Windows GUI, Universal will now always apply grid conditional layouts that don't have any conditions.Changed data-testids for Excel-style filtersbreakingOnly relevant if you're using custom CSS or automated testing based on test-ids on column headers of the grid.As a result of improvements made to grid header filtering, we have updated the data-testid attributes for the Excel-style filter elements. This should only impact automated tests that actively interact with Excel-style filter functionality. Check your automated tests and update them if necessary.All grid header filters now adhere to the following naming convention:Component names - <type>-excel-filter (for example, numeric-excel-filter, domain-excel-filter) List containing checkboxes - <component name>__<field>__list ListItemButton (select all) - <component name>__<field>__list-item-button Select all checkbox - <component name>__<field>__list-item-select-all-checkbox ListItem - <component name>__<field>__list-item__<value> ListItemButton (individual items) - <component name>__<field>__list-item-button__<value> Individual checkbox - <component name>__<field>__list-item-checkbox__<value> Checkbox text - <component name>__<field>__list-item-name__<value> Autocomplete - form-field__<field>__controlThe following data-testids have been changed:Autocomplete Renamed label primitive-value-autocomplete-editor to form-field_<field>__primitive-control__<value> Renamed editor primitive-value-autocomplete-editor to form-field_<field>__primitive-control Boolean Basename excel-filter changed to boolean-excel-filter Added __<value> to individual items. Renamed individual checkbox excel-filter__<field>__list-item-option__<value> to boolean-excel-filter__<field>__list-item-checkbox__<value> Single line Added __<value> to individual items. Domain Basename change excel-filter to domain-excel-filter Added __<value> to individual items. Renamed thumbnail image excel-filter__<field>__<filename>__list-item-image to domain-excel-filter__<field>__<filename>__list-item-image  Changes to 'GROUP HEADER LABEL' and 'LABEL' controlsbreakingIn the Windows GUI, when using GROUP HEADER LABEL or LABEL domain controls, both the column name and value are shown. We have included this functionality in the Universal UI as well to ensure consistency across platforms. Additionally, conditional layout is now correctly applied to both LABEL and GROUP HEADER LABEL controls. Before, labels only displayed values After, labels now display column and valueDue to these changes made to the GROUP HEADER LABEL and LABEL controls, some breaking changes have been introduced.Label controls no longer apply values set in Field height in positions. To achieve the same effect as a multiline label control, use a read-only multiline control with Field height in positions. Label controls now display both the column name and value by default. This may affect existing screens that use these controls, for example, if the layout is designed to accommodate only the value. To revert to the previous behavior of only showing the value, set Label width (px) to '0'. New and changedAdded data types to column header filteringCommunity idea newWe introduced the ability to filter columns using the column header in the Universal GUI 2025.2.13 release. This functionality has been extended to include numeric data types (for example, Integer, Decimal, Float). The list of items is limited to 25 by default to optimize performance and usability. When the number of unique values exceeds 25, the list of checked items is replaced with a dropdown list with a search function. You can change these settings by using the extended property LookupGridHeaderFilterOptionsLimit.Filter numeric values in the column header by selecting from a list of items If the number of values exceeds 25, use the search function to find specific values Color pickers for HTML editornewYou can now select colors for text and background in the HTML editor using a color picker. Use the color picker to select text and background colors in the HTML editor Added functionality for custom componentsnewYou can use custom components to extend the functionality of Thinkwise applications. To further assist in developing custom components, you can now start a process flow from your custom component by posting a message to the parent (Universal) window.Use the following code to do this:window.parent.postMessage({ type: 'startProcessFlow', processFlowId, dataParams }, '*');In this code:processFlowId is the ID of the process flow you want to start. dataParams is a JavaScript object containing the process flow variables, for example, { 'variable_1': 'value of variable 1' }.In addition, we have added the IndiciumRootUrl property to the context message passed to custom components. This property provides the root URL of the Indicium server, which can be useful for constructing paths to resources or services hosted on the Indicium server.For more information, see Custom component. Action buttons Expand all/Collapse now work for grouped Grids toochangeWhen you have a Tree component with an action bar, the options Expand all and Collapse all are available from the overflow menu. These options are now also available for the Grid component.For a Grid, grouping in a grid must be enabled for these options to be available. If the Grid component does not have any groups, these options are not available. If a Tree and Grid component are present in a screen type, using these options expands or collapses all rows in both components simultaneously. Version check performed before loginchangeThe Universal UI checks for a new version on the web server each time it is accessed. Previously, the user would immediately be redirected to the OpenID or Indicium login screen without waiting for this version check to complete. Now, the Universal UI waits for the version check to complete before redirecting the user to the login screen. This ensures that the latest version of the Universal UI is applied before login, preventing potential issues caused by version mismatches. The text 'Checking for updates...' is now displayed while the version check is being performed. Improvements for pivot tableschangePreviously, some query calls were always executed in pivot tables, even when they were not required. We have optimized the performance of pivot tables by removing several of these unnecessary query calls.You can further improve the performance of your application by configuring the general settings of subjects that you do not use in a pivot table. To configure these settings, go to the menu User Interface > Subjects > tab Settings > tab General.For each subject:Set Max no. of records to '1'. Set Page size to '0' to disable paging. Select Start with empty filter. Updated order of buttons for SchedulerschangePreviously, when you changed a selected date range in a Scheduler, the previous and next buttons would move in the interface if the new date occupied more space. The order of the 'Today' button, the previous and next buttons, and the date has been changed to prevent this behavior. This ensures consistency in the user interface when changing date ranges.Previously, the previous and next buttons were positioned before the dateNow, the previous and next buttons are positioned after the date Minor fixes and tasksFixes for Model insights: When Model insights was active and you opened a Filter pop-up, the dropdown for any Operator field did not open. This has been fixed. When the user selected an HTML field with Model insights active, the information for that field was not displayed. This has been fixed. Fixes for modal documents: When a modal document was opened, the underlying document would show unwanted behavior by trying to display the same content as the modal document. This has been fixed. Fixed an issue where closing a modal document that was opened via a process flow would unexpectedly activate the tiles menu, instead of keeping the underlying document open. Fixes for the Scheduler: When deselecting Labels for lowest timescale in a Scheduler view, the events would incorrectly snap to time cells. For example, events occurring within a 15-minute interval would snap to the nearest hour if the lowest timescale was set to 15 minutes. This has been fixed. In the Scheduler, when using the Between / Not between conditions with the Value type set to Constant and the Until value type set to Column, the condition did not function as expected. This has been fixed. In some cases, grid header filtering would show an outdated list of items after the global search or filters on other columns were changed. This has been fixed. DB2 - Fixed an issue where messages sent from control procedures using SET V_MESSAGE_TEXT would only display one character instead of the full message. Previously, opening a screen or menu that contained many tasks or reports triggered numerous network requests, resulting in slow loading times. This was especially noticeable when the Software Factory was used as a metasource. Lazy loading has now been implemented to improve performance. The task or report model is only loaded when you open the task or report. In some cases, all prefilters would disappear after updating a user-defined prefilter. This has been fixed. Previously, if a lookup reference (for example, an untranslated lookup column) did not have a display column, a 'bad request' error would occur in the FormList when attempting to save data. This has been fixed. Previously, the date picker icon was clickable for read-only fields with a Date or Time control. This has been fixed. When you imported data from an Excel file (.xls, .xlsx) and no column header row was found by Indicium, incorrect values were shown in the fields Row which contains column headers and First row from where import begins in the interface. This has been fixed. Fixed an issue where the settings Show grand total for columns and Show total for columns were incorrectly translated in the user interface. In some cases, conditional layout was applied incorrectly: The Font color was not applied in to Read only fields in edit mode. The grid did not apply conditional layout when there were no defined conditions. In some cases, tasks on a custom action bar would not become visible after selecting a record. This issue has been resolved. In some cases, pivot grids would indefinitely show a loading indicator when a cube had no cube views defined. If there are no cube views, users can now create a cube view if the Enable cube panel is selected. Auto refresh for Modal documents did not work as expected. This issue has been resolved. In some cases Export was not visible in the action bar or toolbar for pivot tables. This has been fixed. What we will be working on next sprintThe next sprint we will be working on:Excel-style filtering for date and time columns. Support for date-interval filtering in filter pop-ups. Additional filter options for lookup-type columns, such as contains and starts/ends with. Support for filtering on empty values in both quick filters and the advanced filter pop-up. Numerical range filters following the Excel-style model. A new process action to open the filter pop-up directly (planned for 2026.1). Full support in the Software Factory for all Universal GUI filter functionality, including modeler and code-editor integration (planned for 2026.1). Improved grouping options: tasks, reports, prefilters, and cube views available as group dropdown buttons in the action bar when submenu mode is enabled (planned for 2026.1). Grid group summaries to better visualize aggregated data within grouped 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.320251117 - Correct sending notifications to tenant users When sending a notification to all users of a Tenant using a large title and text, the notifications could fail to be added. This has been fixed. SF all supported versions (2025.3 - 2024.2)20251119 - Ensure cleanup of unassigned triggers and instead of triggers when upgrading When upgrading an end product using the Smart method, only new objects, actual changes to objects, and deletions are performed on the end product database. However, the cleaning up of old removed triggers and instead of triggers did not function properly, causing these objects to remain on the database after an upgrade if the table or view was not being rebuilt or redeployed. This has been fixed.  Note: to ensure that no triggers and instead of triggers are left over on your end product databases, you can opt to perform a Full upgrade and only execute the Triggers and Instead of triggers code files. SF all supported versions (2025.3 - 2024.2)20251120 - Update cube view when modified through Windows GUI UP When, for example, deleting a saved user preferences cube view in the Windows GUI (2-tier), the GUI would reorder the remaining cube views. During this process, the contents of the user-created cube views were lost. This has been fixed.

Hello everyone,In this release we have added support for connecting to Azure Cache for Redis using an Azure Managed Identity. Additionally, you can now export i-net Clear Reports to Excel format in Indicium. Finally, we have included a Redis health check in Indicium.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.12 here.ContentsAbout Indicium New and changed Support for Azure Managed Identity Added support for exporting i-net Clear Reports to Excel Added health check for Redis Minor fixes and tasks Questions or suggestions? New and changedSupport for Azure Managed IdentitynewIndicium now supports connecting to Azure Cache for Redis using an Azure Managed Identity. To enable this, add the following section to appsettings.json (or through environment variables)."RedisSettings": { "ConnectionString": "<connection string>", "UseAzureActiveDirectory": true}We updated the Microsoft Azure SDK libraries to enable this functionality. If you are using Azure Blob storage in combination with a Managed identity, ensure that it works correctly in your environment.  Added support for exporting i-net Clear Reports to ExcelnewIn the Windows GUI, users could already export i-net Clear Reports to various formats, including Excel. We have now added support for exporting i-net Clear Reports to Excel format (.xlsx) in Indicium. This allows you to export reports directly to Excel from Indicium when using the Universal GUI. Minor fixes and tasksFixed an issue where the Debug Center did not behave as expected when Indicium was scaled to multiple instances. In the Windows GUI, automatic column mapping is case insensitive for direct matches and translated values when importing data. Indicium now matches this behavior. Fixed an issue on Oracle where the tsf_global_lang_id session variable could return a stale value. Before, the extended property IgnoreDiacritics was only implemented in Indicium for combined filters. It has now also been implemented in the regular filter form, to align with the Windows GUI behavior. 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.3, 2025.220251031 - Assign treeview item rights error In a previous hotfix, we resolved an issue when assigning rights to menu groups and items. However, when assigning rights to treeview items, it was possible that an error would be returned. This has been fixed. SF 2025.320251029 - Show all available application languages in SF meta When starting an application on the SF metasource, so the model is read directly from the Software Factory, the available application languages in the User profile menu in the Universal GUI was limited to solely the current language of the user. This has been changed. You can now select any language that is available for applications that are active for you. Note that changing the language will change your user's language in IAM.

Hello everyone,We’re pleased to announce Testwise v0.1.63, delivering enhancements that improve stability, broaden UI component support, and refine the end-to-end testing experience for Thinkwise applications. As always, this Testwise version is fully compatible with the latest Universal GUI version available at the time of release. Alongside usability updates and new component support, this release lays the groundwork for upcoming model-driven automation capabilities.For those new to Testwise: It's a Playwright support library purpose-built for Thinkwise applications, making end-to-end testing simpler, more reliable, and seamlessly aligned with the platform. Learn more in our blog here: What's New in v0.1.63Debugging and LoggingConfigurable log-level support has been added for improved troubleshooting and runtime visibility.Bug FixesResolved a known issue with GoToDeepLink.Grid Testing EnhancementsNew helper functions simplify grid behavior validation:verifyNumberOfRowsInGrid() noResultsFound() rows()See the documentation for examples and guidance.Session ManagementIntroduced page.logOut() to streamline session resets during test automation.Dropdown Component SupportAdded support for dropdown controls, with full usage details in the documentation.Expanded UI Component CoverageNew components and tab support include:TaskTile and TaskTileObjects — see End-to-end tests | Task tiles Component and Detail tab componentsTest StabilityMultiple improvements increase reliability and reduce test flakiness.DocumentationComplete usage examples are available in the End-to-end tests documentation.Coming Next — v0.2.0The next release will introduce the first phase of model-driven automation, enabling automatic generation of Page Objects and UI components directly from Thinkwise application models. This will significantly reduce setup effort and improve test suite scalability.More details coming soon!

This is an additional release for the Universal GUI version 2025.3.11.We fixed an issue where a report parameter bound to the Action Property results in an empty dropdown list. This only happened when the parameter was non-required.The 2025.3.11.1 release is now available for download in TCP.

Hello everyone,An extra release of Indicium has been made available in TCP with version number 2025.3.11.3.In this release we have updated the driver that Indicium uses for SQL Server, because it contained a performance issue which, even though it was rare, could dramatically impact the performance of model loading for Indicium. The most notable situation which triggered this performance issue was having multiple active applications of the same model / branch. If you have not noticed severe performance issues when loading application models (i.e. when switching applications or after a cold start), then this fix is not relevant to you.Version 2025.3.11.2 of Indicium was not made available in TCP, but contains a fix to the Debug Center when using Redis. If you do not have RedisSettings configured in the appsettings of your Indicium, then this fix is not relevant to you.Our apologies for any inconvenience caused by these issues.

October 27, 2025Full release (from release candidate 2025.3.11) Additional fixes this release: In some cases, the application would crash if there was a delay in loading user information. This has been fixed. Fixed an issue where user preferences would occasionally not load when starting a new session. In some cases, editable pivot grids would continuously refresh when displayed as a detail of subject. This has been fixed.  Hello everyone,In this release, we focused on improving the user experience for several components of the Universal GUI. The behavior of the Filter pop-up, grid header filtering, lookup hyperlinks, and HTML form fields have been improved.Additionally, we added an error message for cube views without configured fields. We also made improvements to domain and report action controls and fixed various issues for cubes, editable grids, conditional layouts, and the Scheduler.This release also includes a breaking change for time scale conditions in the Scheduler. Read the release notes carefully before updating. 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.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.3.11 here ContentsDemo Universal GUI version 2025.3.11 Breaking Updated time scale conditions in the Scheduler Review custom CSS and test IDs usage New and changed Error message added for cube views Improvements to domain and report action controls Improvements for grid header filtering Improvements for lookup hyperlinks Improvements for HTML form fields Minor fixes and tasks What we will be working on next sprint Questions or suggestions? BreakingUpdated time scale conditions in the SchedulerbreakingYou can add conditional time cell formatting in the Scheduler based on different time scales, such as day, week, or month. Previously, to add a condition based on the month, you had to set the value to '0' for January, '1' for February, and so on. To make this more intuitive, values now match the actual month numbers. January is now represented by '1', February by '2', and so on.Check existing month-based time scale conditions and update their values accordingly. Review custom CSS and test IDs usagebreakingAs a result of improvements made to domain and report action controls, we recommend that you review the following:data-testid usage - The data-testid for the editor remains unchanged, however accessing child elements is now different. To access the input, use form-field__<your column id>__select__input To access the dropdown list, use form-field__<your column id>__select__options-list. Custom CSS - Check your custom CSS to ensure it is still working as expected in your applications.For grid header filtering, data-testids are renamed:list-option > list-item. list-option-button > list-item-button. list-item-option > list-item-checkbox (text-types). list-option-checkbox > list-item-checkbox (lookup-types). list-option-name > list-item-name. single-line-control-filter-loader > single-line-list-selection-filter-loader. single-line-control-filter-no-option (new). lookup-control-filter-no-option (new).  New and changedError message added for cube viewsCommunity idea changePreviously, when no cube view fields were configured in the Software Factory the user would see a continuous loading screen, without any visible result. To improve clarity, the error message "No cube fields configured" is now displayed when no cube view fields are defined. Improvements to domain and report action controlschangeWe have made improvements to domain and report action controls. You can now search by typing in the dropdown of a domain or report control, allowing you to quickly search and select items.The dropdown is automatically opened when a domain is selected and you start typing. To clear the field, use the Clear button. When the dropdown is open you can use the ↓ and ↑ keys to navigate the dropdown.Previously, you could select items from the dropdown Now, you can type to search as well as select items from the dropdown Improvements for grid header filteringchangeWe introduced the ability to filter columns using the grid header in the Universal GUI 2025.2.13 release. In some cases, header filtering would lead to unexpected behavior or crashes.To fix these issues the following changes have been made:Checkboxes are enabled by default. Improvements in synchronization between the header filter, the pop-up filter and the search bar. The header filter is only applied after closing the pop-up. Improvements for lookup hyperlinkschangeUsers can open a lookup pop-up directly from the grid and the card list by clicking a lookup hyperlink. Previously, all lookup hyperlinks in a grid were clickable, which sometimes caused users to unintentionally open the lookup pop-up of a row while selecting another row. To prevent this, clickable hyperlinks and their hover styling are now only active for the selected row. Improvements for HTML form fieldschangePreviously, when you edited a form field with an HTML control, the screen scrolled to the bottom of the field. We have corrected this behavior. Now, when you enter edit mode and the field already has content, the cursor is placed at the end, and the view scrolls smoothly to that position. Minor fixes and tasksFixes for the Filter pop-up:When a column was initially available in the overflow, was selected and the operator was set to Is (not) empty, the condition was not shown again when re-opening the popup. When a numeric column was filtered on the value of '0', it would not be applied. When the operator of a column filter was set to Between and no values were provided, a bad_request error would occur. In some cases, the Filter pop-up would ignore changes in the filter conditions. Fixed an issue where single-condition, single-column filters (also known as elementary filters), were not properly recognized in nested or complex filter groups.Fixes for cubes:Fixed an issue where editing a pivot field with the DATETIME2 or DATE domain in a pivot table could result in a bad request error. When a field of a category in a pivot table had the Field width (px) set to a fixed value, longer content would not be fully displayed. Now, ellipsis and a tooltip with the complete content are displayed when this occurs. In some cases, when editable cube view fields were deep nested in categories and series, they would not be saved. This has been fixed.Fixes for editable grids:Fixed keyboard shortcut behavior in default editable grids: When focus is on a field and the dropdown list or the date picker is not open, you can use ↑ and ↓ to navigate rows. When focus is on a field and the dropdown list or the date picker is opened, you can use ↑ and ↓ to select a value. Fixed an issue where switching rows in a grouped or default editable grid could cause unexpected behavior of grid headers. When you edited a column with an IMAGE COMBO in an editable grid, the selected column became misaligned with inactive records. This has been fixed. If an editable grid had a row height bigger than 44px, the IMAGE COMBO editor would be aligned incorrectly. The editor is now centered inside the cell.Fixes for conditional layouts:Conditional layouts are now correctly applied for negative values with Between conditions. When a condition for a negative value was defined on one column but the styling applied to a different column, the styling was not correctly applied. This has been fixed.Fixes for the Scheduler:When adding cell color conditions, using a column for Type of value did not work. This has been fixed. Fixed an issue where column conditions would be evaluated as true when no records match. Fixed an issue where having multiple copies of the same view caused the cell colors to only appear in the last view, instead of all views.Other fixes:In some cases, primary colors and accent colors set up in themes for the Universal GUI would result in insufficient contrast between screen elements such as text and background. This affected the following components: Third party licenses button in the About menu pop-up Update now button in the profile menu pop-up and the snackbar Install button in the snackbar Indicium error messages with links to logs 'Row not found' message This has been fixed. Black or white is now applied in cases where the accent color does not provide enough contrast with the background color. When a screen type included both an action bar and a bar component (Prefilter bar, Cube view bar, Report bar, Task bar) actions would be displayed twice if they were configured in both. We have changed this behavior so actions are no longer duplicated in the interface. If you want bar components to be displayed in the action bar in the correct order, enable the corresponding action bar actions. For more information on configuring the action bar, see Configure the default Action bar settings. If the preferred language was available in the User preferences menu but not yet loaded when opening the popup, the language options could be empty. This has been fixed. When you used a domain with elements and a RADIO BUTTON control, elements set to Unavailable were still displayed in the user interface. This has been fixed. The style of focused cells in editable pivot tables has been updated. When an editable cell is focused, its background color is now removed. Additionally, focused cells now use the main color of the application theme. The message pop-up displayed when users disabled push notifications was not translated correctly in the application. This has been fixed. Fixed an issue where alignment settings for grouped columns in a grid was not applied correctly. What we will be working on next sprintThe next sprint we will be working on:Add model caching over sessions to enhance performance when, for example, opening subjects or tasks. Introduce task/report/prefilter/cube as group split buttons in the action bar to optimize space. Start adding support for the Software Factory on Universal, including styling, custom components, and code editing. Implement grid header filtering for numeric and date(time) columns. Add interval filtering on date(time) columns, such as year, quarter, month, day, etc. 2026.1 - further enable customization of Scheduler views, including: Configuring a minimum and maximum displayed time, for example, to hide non-office hours. Ability to hide weekdays, for example, to hide the weekend. Offering an option to configure minimum timeslot width in pixels to prevent timeslots from being too narrow.  Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community! 

Hello everyone,We are releasing a new version of Indicium that includes functionality which didn't make it into the 2025.3.11.0 release. Download Indicium release 2025.3.11.1 here.Support for Azure Managed IdentitynewIndicium now supports connecting to Azure Cache for Redis using an Azure Managed Identity.To enable this, add the following section to appsettings.json (or through environment variables)."RedisSettings": {  "ConnectionString": "<connection string>",  "UseAzureActiveDirectory": true} We updated the Microsoft Azure SDK libraries to enable this functionality.If you are using Azure Blob storage in combination with a Managed identity, please validate that it works correctly on your environment.

Hello everyone,In this release we have fixed a few minor issues in Indicium.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.11 here. ContentsAbout Indicium Minor fixes and tasks Questions or suggestions? Minor fixes and tasksPreviously, you could use the keyboard to select a user on the user simulation page. Since the restyling update in the Thinkwise platform 2025.3, this was no longer possible. With this update, keyboard navigation is possible again. Fixed an issue where Indicium could not update imported records in cases where models had a look-up dependency on read-only columns. 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.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.