Skip to main content
  • 618 Product updates

Filter by product

🚀 Platform improvements for week 46, 2026

🚀 Platform improvements for week 46, 2026

Hi everyone!We've released the following platform improvements this week: SF 2026.220261111 - Generate and deploy all selected program objects In 2026.2, you can select several program objects in the Code overview or Functionality screen and click Generate selected or Execute selected. Only one of the selected objects was generated or executed. The others were skipped without a warning. The job still finished as successful, so the database could end up partly out of date without you noticing. Generate selected and Execute selected now process every program object you selected. All selected objects are generated or executed in one job, as expected. Selecting a single object works the same as before. This was already fixed in 2026.3 and beyond   SF 2026.3.11, 2026.320261110 - Speed up flagging of views that depend on modified objects Previously, flagging the modified objects for a smart upgrade could take hours in Db2 for i and PostgreSQL models with many views. Every possible route between dependent views was checked separately. Also, a view was considered dependent on a table when the table name only appeared as part of a longer word, such as a column name. As a result, a smart upgrade could select almost all views. We have improved how the views and MQTs that depend on a modified table, view or MQT are found. Each view is now checked only once, and a name only counts when it appears as a whole word. Flagging now takes seconds instead of hours, and a smart upgrade only selects the views that actually depend on a change. Views that refer to an object in upper case, or in Db2 for i by its alias, are now also selected. In Db2 for i, journaling is now also restarted when only an MQT has changed.

Related products:Software Factory
Release notes Testwise 0.2.111

Release notes Testwise 0.2.111

Hello everyone,This release makes tests easier to write and more stable, with new ways to work with grids, task buttons, and date fields. Grid row counts now include only data rows, so tests that add 1 for the header row need an update. Testwise now also works with Universal 2026.3.11.Tests can now do more with action bars and grids: Generated action bars have a getter for every task button, so your editor suggests task buttons while you type. For grids, you can read the values of the summary row and select a row without starting an edit.Tests also no longer depend on the date settings of the test user, because date fields are filled the same way under every date format.Several quality-of-life improvements round out this release. Timeout errors now say what Testwise was waiting for, so you find the cause of a failed test faster. Fixes for grid column values, combo boxes, prefilters, date fields, and names with accents make tests more reliable. ContentsBefore you upgrade Breaking Grid row counts limited to data rows New Support for Universal 2026.3.11 Getters for every task button on generated action bars Summary row values in grids Grid row selection without starting an edit Date fields filled the same way under every date format Changed Clearer timeout errors Fixed Questions or suggestions? Before you upgradeTestwise 0.2.111 supports Universal 2026.3.10 and Universal 2026.3.11. Check Support for Universal 2026.3.11 for more details. BreakingGrid row counts limited to data rowsPreviously, the rows of a grid also included the header row, and the summary row when the grid had one. Now, the rows of a grid include only its data rows (@thinkwise/testwise > Grid > rows()). The number of rows equals the number of records a user sees, also in grids with a summary row. Checking the record count with verifyGridRecordCount() works as before, and now also in grids with a summary row.For example, for a grid that shows 3 events:const event = await page.subject.EventMain;// 0.2.105: the header row was counted tooawait expect(event.grid2.rows()).toHaveCount(3 + 1);// 0.2.111: only the data rows are countedawait expect(event.grid2.rows()).toHaveCount(3);After updating to 0.2.111, tests that add 1 for the header row fail until you remove the extra 1.To fix these tests:Look in your tests for row counts that add 1 for the header row, for example, toHaveCount(3 + 1). Remove the extra 1. Run the tests. NewSupport for Universal 2026.3.11Testwise 0.2.111 now supports Universal 2026.3.11. The Filter pop-up is different compared to previous versions of the Universal UI. This affects how Testwise interacts with the Filter pop-up in tests.In earlier versions, Select field in the advanced filter was a button. In Universal 2026.3.11, Select field in the advanced filter is a combo box. Previously, selecting a field timed out, because the test could not find the picker. @thinkwise/testwise > FilterPopup > selectField() and addField() now finds the picker in both versions.In Universal 2026.3.11, a date interval row gets a new, empty interval row below it as soon as it has a value. This allows the date column to have multiple interval rows. @thinkwise/testwise > FilterPopup > intervalSelector(), intervalSelectorInput(), openInterval(), and setInterval() use the column's first interval row by default.To use a different one, pass its position among the column's interval rows (counting from 0) as index.For example, set and check the interval of a date column's second interval row in the advanced filter:import { FilterPopup } from '@thinkwise/testwise';const filterPopup = new FilterPopup(page);await filterPopup.setInterval('event-date', 'year', { index: 1 });await expect(filterPopup.intervalSelectorInput('event-date', { index: 1 })).toHaveValue('Year'); Getters for every task button on generated action barsYou can now use a generated getter for every task button on the action bar of a generated subject.Previously, the generated action bar only had getters for the CRUD buttons, such as Add, Save, and Delete. To reach a task button, you had to use getTaskButtonById() with the id as the page renders it, with hyphens instead of underscores, for example, send-invitation. getTaskButtonById() now also accepts the task id as it is written in the model.Your editor now suggests task buttons while you type. When a task is removed from the model, the editor shows an error in the test instead of the test waiting for a button that is not there.The getters are in Test project > test-artifacts > subjects > [Subject] > Components > [Subject][Variant]ActionBar.ts. In a test, you reach them through page.subject > [subject, such as EventMain] > [toolbar] > [task name]Button.To use a task getter:Update Testwise to 0.2.111 and run npx testwise sync. In a test, type the toolbar property of a generated subject, followed by a dot. Your editor lists every task on that action bar as [task name]Button. For example, task send_invitation is listed as sendInvitationButton. Call click() on it to start the task.For example, a test that sends the invitation for an event:const event = await page.subject.EventMain;await event.toolbar3574C040.sendInvitationButton.click();Tasks with custom display type 4 are not standard toolbar buttons, so they have no getter. Summary row values in gridsYou can now read the summary row that a grid shows when a column has a count or sum. Tests can check the totals and counts a user sees in a grid, for example, that the sum of a column is updated after a record is added.The methods are in @thinkwise/testwise > Grid > getSummaryCellByColId() and getSummaryValueByColId(). Generated grid columns have getSummaryCell() and getSummaryValue().To check a summary value:In a test, get the generated subject whose grid shows a summary row. Call getSummaryCellByColId() on the grid with the id of the column. Check the cell with toHaveText(). The check passes when the summary row shows that value.To get the text itself, use getSummaryValueByColId() instead. It returns null when the column has no summary.For example, check that the total number of attendees in the grid is 250:const event = await page.subject.EventMain;await expect(event.grid2.getSummaryCellByColId('max_attendees')).toHaveText('250'); Grid row selection without starting an editYou can now select a grid row by clicking a column you choose (@thinkwise/testwise > Grid > selectRowByIndex()). Previously, the usual way was to click the middle of the row. On an auto-edit grid, that click could land in an editable cell, opening an editor and changing the record instead of selecting it. Clicking a read-only column now selects the row without editing it.To select a row without starting an edit:Choose a column that is read-only in the grid, such as the key column. In a test, call selectRowByIndex() on the grid with the row number (counting from 0) and the id of that column. The row becomes the active record, and no editor opens.For example, select the first event without editing it:const event = await page.subject.EventMain;await event.grid2.selectRowByIndex(0, 'event_id'); Date fields filled the same way under every date formatTests no longer depend on the date settings of the test user. A date written as YYYY-MM-DD is now entered as the same date for every test user, no matter their date format (for example, DD-MM-YYYY or MM/DD/YYYY). This works in the date fields of forms (@thinkwise/testwise > DateControl > fill()) and in the date inputs of the Filter pop-up (@thinkwise/testwise > FilterPopup > setDate()).Previously, a date was typed exactly as written, so a test only entered the right date for users with the date format it was written for. A date written another way is still typed as before.To enter a date:When you fill a date field of a generated form (named [column]DatePicker), write the date as YYYY-MM-DD, for example, fill('2025-03-15'). If the field has a time, add it as YYYY-MM-DD HH:mm:ss. For a date in the filter pop-up, call setDate() with the field id and the date. FilterPopup.setDate() is new, so it only accepts YYYY-MM-DD or YYYY-MM-DD HH:mm:ss, and gives an error for any other format. Run the test with any test user. The field shows 15 March 2025 in that user's date format.For example, enter an event date and filter events on a date:import { FilterPopup } from '@thinkwise/testwise';const event = await page.subject.EventMain;await event.form1.eventDateDatePicker.fill('2025-03-15');const filterPopup = new FilterPopup(page);await filterPopup.setDate({ fieldId: 'event-datetime', part: 'date', value: '2024-01-15' }); ChangedClearer timeout errorsPreviously, when a Testwise wait timed out, the error only said that the wait had timed out. Now, the error also says what Testwise was waiting for, how many times it checked, and the last value it saw. A failed test tells you directly what did not happen, so you find the cause faster.This applies to @thinkwise/testwise > Grid > verifyGridRecordCount() and hasNoRowsOverlay(), and to the waits during login, user simulation, and the delete-all-rows pop-up.For example, the error when a grid shows 4 records where the test expects 5:pollUntil timeout after 10000ms waiting for the grid to show 5 records; 47 attempts over 10066ms, last value: 4 Fixed In a grid with a summary row (count or sum), reading the values of a column also returned the summary value, so the list had one value too many (@thinkwise/testwise > Grid > getCellValuesByColId()). Reading a column now returns only the values of the records in the grid. A test that worked around this issue, for example, by dropping the last value from the list, now fails. So does a test that expects the summary value in the list. Remove the workaround, and read the summary value on its own with the methods from Summary row values in grids. When selecting a combo box option whose text contains a space, such as Human resources, the test waited for the option until it timed out (@thinkwise/testwise > FormComboBox > selectOption() and lookupSelect()). Every option can now be selected by its visible text. When saving a filter as a prefilter (@thinkwise/testwise > FilterPopup > applySaveAsPrefilterWithName() and saveAsPrefilterPopup()), the test could click the wrong Save, because the Filter pop-up and the Save as pop-up each have one. The step also finished while both pop-ups were still closing, so the next click could land on one of them. Now, the test clicks Save in the Save as pop-up and continues only after both pop-ups have closed. Filling, clearing, and reading a date field of a generated form (@thinkwise/testwise > DateControl > fill(), clear(), inputValue(), and inputElement()) acted on the whole form instead of on the date field. Filling a date only worked when the click happened to land in that field, and checking the field's value could not pass. npx testwise sync stopped with an error when the model had a screen type or table with an accent in its name, such as Algemeen hiërarchie, because the generated code did not compile. After npx testwise sync, a subject or variant with an accent in its name was missing from page.subject.  Questions or suggestions?Do you have any questions or suggestions? Let us know in the Thinkwise Community!

Related products:Testwise
🚀 Platform improvements for week 44, 2026
Release notes Thinkwise Platform 2026.3.11

Release notes Thinkwise Platform 2026.3.11

Hi everyone,This release makes modeling in the Software Factory faster, keeps your databases lean, and makes filtering and keyboard use in Universal UI quicker. Note that this release includes several breaking changes, so check the details before upgrading.Modeling in the Software Factory takes fewer steps. The screen New objects now suggests which roles should get rights to each new object, so you no longer need to switch between screens. Code search has new options, such as case-sensitive search and excluding comments, and code review has a new prefilter that shows only your own comments. You can also exempt a user, such as a service account, from exclusive branch access, so jobs keep running on these branches.Managing the size of your databases has now become easier. You can clean up old model versions in active branches such as MAIN and DEVELOP, manually or based on a retention period. In IAM, old deployment runs and their logs are now deleted automatically.In Universal UI, filtering is faster. Users can now open the Filter pop-up from a column header and set up date ranges without adding the column again. They can also do more with the keyboard: jump to a row by typing in a grid, navigate the menu with shortcuts, and keep navigating right after editing a record, because the focus returns to where they were.Several quality-of-life improvements round out this release. Users can now copy multiple rows from a grid, for example to paste them into Excel, and read-only lookup fields show as hyperlinks in edit mode.This is a short-term support (STS) release of the Thinkwise Platform. STS release support expires as soon as a new release is made available. For example, support for version 2026.1.12 ends when version 2026.1.13 is released.See our Lifecycle policy for information about supported versions. ContentsBefore you upgrade Demo and download Breaking Renamed column for 'Execute source code' for CI/CD Data loading based on the components on a screen Fewer conditions for time-based cell colors in schedulers Software Factory Quality - Own comments filter and logical sort order Business logic - Improved code search Models - Exempt a user from exclusive branch access Access control - Suggested roles for new objects Maintenance - Clean-up of model versions in active branches Intelligent Application Manager Applications - Scope override for OAuth servers Database servers - Automatic cleanup for deployment runs Indicium Support for web connection endpoint timeouts in Indicium Universal UI Open 'Filter' pop-up from a column header filter Faster date interval filtering in the 'Filter' pop-up Quick search by typing in grids Domain alignment in forms, reports, and tasks Keyboard navigation in the menu Copying multiple rows from a grid Improved display of lookup hyperlinks Focus returns to the original component after editing Fixed Software Factory and Intelligent Application Manager Indicium Universal UI Data model changes Table changes in the Software Factory Column changes in the Software Factory Table changes in the Intelligent Application Manager Column changes in the Intelligent Application Manager Questions or suggestions? Before you upgradeFeatures for the Software Factory and the Intelligent Application Manager are only compatible with this STS version of the Thinkwise Platform. Indicium and Universal UI features are backwards compatible with previous Thinkwise Platform versions, unless otherwise noted.Demo and downloadTry a demo of the Thinkwise Platform here. Download the latest versions of our components here. BreakingRenamed column for 'Execute source code' for CI/CDSoftware FactoryWhen executing the task Execute source code, two jobs are used. The connect job connects to the database and creates the execution row. The execute source code job then executes the selected code files.The column for the connect job has been renamed from job_id to connect_to_db_job_id, to clarify its purpose. This change affects CI/CD pipelines that use the job_id column.Before: POST [indicium]/iam/sf/code_file_execution_overview(...,job_id=123)/abort_execute_source_codeAfter:POST [indicium]/iam/sf/code_file_execution_overview(...,connect_to_db_job_id=123)/abort_execute_source_codeThe following still works as before:Starting the jobs with connect_to_db or add_job_to_execute_source_code. Getting or waiting for a job with job(...) or wait_for_job.If you call one of these tasks or read these tables through the API, replace job_id with connect_to_db_job_id in the key or field name. Data loading based on the components on a screenUniversal UIPreviously, Universal UI always loaded data based on the pagination and record limit settings of the subject.Now, Universal UI picks one leading component on the screen and loads data for that component. This prevents unnecessary data and pagination requests. For now, this applies to forms, pivot tables, and charts.Without a grid, card list, or tree on the screen, only one record is loaded. For example, on a screen with only a form, or with only a pivot table and a chart. This means you no longer need to set Max. no. of records to '1' and Page size to '0' yourself for these screens. With a pivot table or chart as the leading component, pagination is disabled. Other grids, card lists, and trees on that screen only show the number of records set in Max. no. of records, with a default of '1'. Double-clicking a pivot table cell to show its underlying data still uses pagination.When the screen type changes, for example at a breakpoint, Universal UI picks the leading component again.After upgrading, check screens that show a pivot table or chart next to a grid, card list, or tree. Set Max. no. of records for those subjects if they need to show more than one record. Fewer conditions for time-based cell colors in schedulersSoftware FactoryIn preparation of Scheduler conditional formatting based on time and day of week some breaking changes have been introduced in this release.The available conditions Type of time scale have been changed. This affects all types: Column, Time scale, and Datetime.The following conditions have been removed:Starts with Contains Does not contain Is empty Is not empty Does not start with Ends with Does not end with In Not inExisting conditions that use these conditions are set to Equal to during the upgrade.The following conditions remain: Between, Equal to, Greater than, Greater than or equal to, Not between, Not equal to, Smaller than, and Smaller than or equal to.After upgrading, check whether the conditional formatting for your Schedulers still works as expected. Software FactoryQuality - Own comments filter and logical sort orderchangeThe tabs Changes and All comments now have the prefilter Own comments (menu Quality > Code review). It only shows your comments, so you can quickly check how the developer addressed them.Previously, the tab Changes sorted changes by their last update. Now, control procedure changes come first by default. This is followed by template changes in the order they are assigned to the program object. This new order makes the code easier to follow.The order of changes can be manually updated using the sort options in the column headers. Business logic - Improved code searchchangeWe have improved the search options in the menu Business logic > Code search:Comments - Previously, search results always included matches inside comments. Now, you can exclude these matches by clearing Comments under Extend search to. Case-sensitive search - Select Case-sensitive to only find matches with the exact same capitalization. Combined search options - Previously, selecting Whole words only or Use wildcards cleared the other option. Now, you can combine both options and Case-sensitive at the same time for more precise results. For example, with all three selected, searching for User%Name only finds UserName. It does not find username, because the capitalization is different. It also does not find -- get User by Name, because User and Name are separate words. Inactive unit tests - Previously, search results always included code from inactive unit tests. Now, this code is only included when you select Inactive code under Extend search to. Previously, exclusion only applied to code from inactive control procedures.Combined search options in Code searchModels - Exempt a user from exclusive branch accessnewNew branches created with Exclusive access, gives full access to the creator and automatically assigns read-only rights to all other users. This would also block any service accounts, for example, Indicium, from accessing the branch and running jobs on it.To address this, you can now exempt a user from this restriction. To exempt a pool user, select the checkbox Exempt from exclusive access in the menu Maintenance > Users > tab General. This applies to all new branches.If a new branch is created with Exclusive access selected, a user with Exempt from exclusive access keeps full access rights to it.Exempt a user from exclusive accessAccess control - Suggested roles for new objectsnewWhen you add a new object to your model, such as a column or a table detail, you typically also decide which roles get rights to it. Previously, this meant switching between several screens, including New objects, Model rights, and Roles (all under menu Access control).To simplify this workflow, the screen New objects (menu Access control) now suggests which roles are likely candidates for each new object. This helps you organize and assign rights more efficiently.For each new object, the Software Factory gives a role a match indication. This is based on the role's rights on related objects. For example, for a new column, it looks at the role's rights on the other columns of the same table and on the table itself.The Software Factory rates each role for an object as follows:Green up arrow - Almost certain, more than 90% Yellow diagonal-up arrow - Likely, 50-90% Orange right arrow - Possibly, 25-50% Red diagonal-down arrow - Very low, 5-25% Gray down arrow - Rare, 5% or lessSuggested roles for a new tableMaintenance - Clean-up of model versions in active branchesnewPreviously, history data was only removed for archived branches. Branches that are never archived, such as MAIN and DEVELOP, kept every change. As a result, the Software Factory database continued to increase in size.Now, you can clean up old model versions of active branches, along with their history data. To do this, go to the menu Advanced > Master data > Software Factory > Model version clean-up. Select a model and a branch, and enter a date in the field Clean up before. By default, the indexes and statistics are optimized after the clean-up. To skip this, clear the checkbox Optimize afterwards.When your clean-up is ready, execute the task Ready for clean-up. The nightly system flow Clean up model versions executes the clean-up at its scheduled time. To make changes before the clean-up starts, execute the task Back to draft. Furthermore, you can change the schedule of the system flow in IAM.The following model versions are always kept:The origin of a branch. The source version for upgrades. Model versions with a status, such as test, acceptance, or production. The origin of an open merge session.The oldest of these versions limits the clean-up: model versions after it are kept as well. The field Effective cutoff shows the date that is actually used, and which branch limits it. The latest model version of a branch is never removed.The tab Preview shows which model versions will be removed. The columns Will be removed and Kept because indicate which model versions are removed, which are kept, and why.By default, Model version retention is set to Indefinitely, so nothing is cleaned up automatically. To clean up automatically, select a period, such as 1 year, in the field Model version retention in the menu Maintenance > Configuration. The nightly run then creates a clean-up for every active branch with model versions older than this period.The following applies to clean-ups of model versions:A nightly run stops after three hours. A clean-up that did not finish gets the status Incomplete. The next nightly run continues this clean-up first.After a clean-up, you can only create a branch, revert, merge, or compare from a remaining model version or a moment after the cutoff.Clean-up of model versions in an active branch Intelligent Application ManagerApplications - Scope override for OAuth serverschange main administrator application administratorAn OAuth scope specifies the permissions that your application requests from the external service. For example, User.Read is used to read a user's profile in Microsoft Graph.Previously, scopes of an OAuth server could only be added and changed in the Software Factory. The model then had to be synchronized to IAM to apply the changes.Now, administrators can also override OAuth scopes in IAM (menu Authorization > Applications > tab General settings > tab OAuth servers). This makes it easier to adjust the scope without needing a new synchronization. Database servers - Automatic cleanup for deployment runschangeOld deployment runs and their logs are now deleted automatically by the scheduled system flow system_flow_clean_up.The new setting Deployment run retention decides which runs count as old (menu Settings > Global settings > tab Form > group Logging). The default is 90 days. When you set it to Indefinitely, nothing is deleted.For each database, these runs are always kept:The latest successful run and every run after it. The most recent run. Any run that is still running.Each step in the Deployment run log now shows a status icon: green when the step succeeded, red when it failed or was prevented (menu Deployment > Database servers > tab Deployment runs > tab Deployment run log). The new prefilter Failed shows only the failed steps. Exports contain the status as text.Status icons in the deployment run logIndiciumSupport for web connection endpoint timeouts in IndiciumnewIndicium now supports the Timeout setting for web connection endpoints that was introduced in Thinkwise Platform 2026.3. It is available in the menu Integration & AI > Web connections > tab Endpoints > tab General.You can use this setting to override the default timeout of 100 seconds with a different value. You can use {parameter} markers to set the timeout value at runtime.The timeout is in seconds:'-1' - No timeout. '1' to '2147483' - The number of seconds to wait.Indicium rejects other values with the new status code -24 (invalid timeout). Universal UIOpen 'Filter' pop-up from a column header filternewUsers can now open the filter pop-up directly from the filter in a column header of a grid.To open the filter, users can select the filter icon in the column header. This pop-up now contains the following new options:Filter icon - Opens the Filter pop-up for the selected column. Filter - Applies the filter conditions selected in the pop-up. Cancel - Closes the filter pop-up without applying any changes.As before, clicking anywhere outside of the filter pop-up closes it and applies the selected filter conditions.Open the filter pop-up by selecting the 'Filter' icon in the column header Faster date interval filtering in the 'Filter' pop-upchangePreviously, users who wanted several interval conditions on a date or datetime column had to add the column again for each one, through Add extra field.Now, a new interval condition appears below as soon as the previous one has a value. This works in both the default and advanced filter pop-up. The next interval type and the same operator are already selected, making it easier to set up a date range. Clearing the value removes the empty condition. In the default filter, the conditions are combined with AND.After entering a year, 'Month' appears as the next interval condition Quick search/find by typing in gridsnewUsers can now jump to a row in a grid by typing the first characters of a value, just like in the Windows GUI. This way, they can find rows with the keyboard, without scrolling or opening a filter.Quick search works in grids, including pop-up grids where users select a value. It is available on desktop when find is allowed on the subject and the grid is not in edit mode. It is not available in trees, card lists, or pivot tables.To search, users click a cell in the column they want to search and start typing. The grid moves to the next matching row and keeps the same column active. For example, typing 'ams' jumps to the next row with 'Amsterdam' in that column. Capital letters and accents do not matter.The search starts below the active row and continues from the top after the last row. It only searches the rows loaded on the current page. If nothing matches, the active row stays the same.Users can keep typing to make their search more specific. After a pause, the next characters start a new search. You can change this pause with the new quickSearchDebounceTime setting in config.json (default 900 milliseconds). Domain alignment in forms, reports, and tasksnewPreviously, the Alignment setting only affected grids. You can now use the extended property ApplyDomainAlignmentToForms to apply the domain setting Alignment (menu Data > Domains > tab Form) to forms, reports, and tasks. This extended property works for text and numeric fields that are not lookups.To enable it, set its value to true. Check your screens after enabling this setting to ensure the alignment is configured as expected. Keyboard navigation in the menunewUsers can now navigate the sidebar menu with the keyboard, in both the list and tree views. This way, they can find and manage menu items without repeatedly pressing Tab or switching to a mouse.Available shortcuts:Alt + M - Focus the Menu search field. Enter - After entering a search term, focus the first matching item. Press Enter again to activate the item. ↑ / ↓ - Move between items. While searching, group headings are skipped. Otherwise, they are included. Ctrl + ↑ / Ctrl + ↓ - Move between groups. → - Go to an item action, such as close or favorite. ← - Go back to the item. Delete - Close an open document or remove an item from Favorites. The focus moves to an adjacent item or to the Menu search field if no items remain. Esc - Clear the search and return the focus to the Menu search field. Copying multiple rows from a gridchangePreviously, when a user selected multiple rows in a grid and copied them using Ctrl+C, only the value of the last selected cell was copied.Now, the full contents of all selected rows are copied to the clipboard. This allows the user to paste the rows directly into Excel, for example. If only one row is selected, the value of the selected cell is copied, as before.Related changes:Shift+click in a cell no longer selects the text in that cell. This makes it easier to select multiple rows. Values in Image combo columns are now copied too. Previously, they were only included in exports. Improved display of lookup hyperlinkschangePreviously, read-only lookup fields in edit mode showed as a disabled field with a pop-up button. This made it unclear that the field was a lookup and could be interacted with. Now, they show as a lookup hyperlink, the same as outside edit mode. This applies to both the form and the grid. Focus returns to the original component after editingchangePreviously, when a user edited a record from a non-editable Grid, the focus moved to the Form. After saving or canceling the changes, the focus stayed in the Form. Because of this, the user could not use the arrow keys to move to another row.Now, after saving or canceling, the focus returns to the component that had focus before editing. The user can continue navigating right away. This works for the Grid, Tree, Card list, and Form.If Auto-edit is enabled, the focus stays where it is, because the user never leaves edit mode. If only Auto-save is enabled, the focus returns as soon as the user leaves edit mode. FixedSoftware Factory and Intelligent Application ManagerPreviously, when you aborted a source code execution job in the menu Maintenance > Jobs, only the job itself stopped. The execution in the menu Deployment > Creation > tab Execute source code kept its previous status instead of being set to Aborted. Code files that were running or waiting for your input did not get the status Failed. This has been fixed. Also, when you wait for a source code execution job through the API with wait_for_job and show_msg, a failed code execution is now reported on that job. When running a complete creation with the error handling for Execute source code set to Ignore, only the first error of each code file was logged. This made it look like only one object had failed to deploy, while more objects could have failed. This has been fixed. All errors are now shown in the Execute source code log. For Code search (menu Business logic > Code search): A search result could point to the wrong line. Searching could fail with a "duplicate values" error. Repeating a search could remove it from the Select previous search list, because the cleanup used your first search instead of the last. When Show badge was enabled for a subject, but the Badge concept (menu User interface > Subjects > tab Default > tab Settings > tab Performance > group Use concept) was disabled, the system still requested badges. Failed requests caused unnecessary server load and flooded monitoring tools, so other failures were harder to find. This has been fixed for subjects, detail tabs, tasks, and reports, including their variants and tasks and reports on a subject. Badges are now only requested when both settings are enabled. Files or images uploaded to a new file storage location with storage type Database were emptied right after a value was provided. Indicium then showed the error System.Collections.Generic.KeyNotFoundException: The given key '...' was not present in the dictionary. This has been fixed. After support for manifest schema specification V4 was added to the manifest generation, the Install type in the generated manifest had no path to the Install folder. This has been fixed. Some generated rename and copy tasks ran their statements in the wrong order. As a result, a rename task could fail with a foreign key violation. This has been fixed. The base model VALIDATIONS gives work models validations that check, for example, whether the default value of a date time column is valid. These validations used the SQL Server function try_cast with data type DATETIME. This could fail on some default values that DATETIME cannot handle. Now, the validations use DATETIME2.IndiciumPercent-encoded characters in a file name could give access to files outside the base path of a file storage location. This affected SFTP and URL-based file storage types. This has been fixed. Fixed an issue where the field Table variant could not be emptied. This could occur when, for example, the table variant was removed from an Open document process action (menu Processes > Process flows > tab Process actions). DB2 In applications on DB2, an expression that depended on an identity column with a decimal data type, such as numeric(5,0), resulted in an error, for example when adding or editing a record. This has been fixed.Universal UIFor keyboard navigation:Since Universal UI version 2026.2.13.0, Page Up, Page Down, Home, and End did not set the active row in a grid. Ctrl+↑ and Ctrl+↓ also had issues setting the active row, and in some cases stopped working after switching pages. This has been fixed. In a pivot table, entering values quickly and confirming each one with Enter could cause the focus and the input to get lost. This has been improved. While typing in a combobox with the dropdown list open, Home and End moved through the options instead of moving the cursor. This has been fixed in forms and editable grids: Home and End move the cursor to the start or end of the text. Shift+Home and Shift+End select the text up to the start or end. On macOS, use Fn+← or Fn+→ instead, and add Shift to select. In a grid, ↑ and ↓ sometimes did not move the active row from a checkbox cell. As a result, checkboxes that users toggled with Space could be reset to their previous value. This has been fixed.For filtering:In the Filter form, users could change IN filters on text or numeric fields while editing a record. Removing a selected value could make the record that was being edited disappear from the grid. Filters now become read-only while a record is in edit mode. After saving or canceling, users can change them again. In the Filter pop-up, the IN and NOT IN operators did not work with date intervals. With Year, Week, or Day, the operator was selected, but an empty pill was shown as a Value. With Quarter, Month, or Day of week, an error occurred. This has been fixed. When a search in a grid returned no results, switching to another document and back hid the filter icon in the column header. The filter itself stayed active. This has been fixed. When a grid was filtered on an interval, such as a date grouped by year, executing an action such as a task on All rows could affect rows outside the filter. Now, the option All rows is disabled for this case.For local date and time handling: DATETIME and TIME values are stored in UTC. Datetime and time columns who have the underlying domain set to Local show these values in the user's local time zone. When users entered a filter value on such a column, the value was sent to the server without conversion to UTC. For users outside the UTC time zone, this returned wrong or missing rows. This has been fixed. Filter values are now converted from the user's local time zone to UTC. This applies to the filter pop-up, the Filter form, and the filter in a column header. Prefilters on these columns are also converted to UTC. Existing prefilters keep working. Conditional layouts on these columns had the same issue. Now, they use the same local time as the displayed value. Date intervals in the filter pop-up, such as Year or Month, are still evaluated in UTC. The column label now shows (UTC). Date grouping in cube views also stays in UTC. In the Import wizard, these columns now show (UTC) in the column matching step. A warning shows that data from CSV, Excel, or the clipboard must be in UTC. Users with a default time zone (Etc/UTC) are not affected. The history of a template or control procedure (Ctrl+H) showed no code when the user's time zone differed from the server's. This happened in the Functionality screen (menu Business logic > Functionality). This has been fixed. For pivot tables and cube views:When a process flow opened a detail screen with a pivot table as a pop-up, drilling down into a cell showed the wrong records. Instead of only the records behind that cell for the parent record, it showed all records in the table with the same row and column values. With large tables, this could return far too much data and slow down the database server for other users. This has been fixed. In a pivot table, selecting a row label, such as an employee, and then starting a task or report opened it with empty parameters. This has been fixed. Charts with date intervals, such as year, quarter, or month, requested every level, including those collapsed by default. With large data sets, this caused performance issues and slowed down loading. Charts now request only the levels shown. A chart on a cube view failed when a dimension was sorted by a field that the chart did not request. Now, that dimension is sorted by its own values. The Export pivot action was not available for cube views whose first row dimension is collapsed by default, or after Collapse all. Now, the action is shown whenever the pivot table contains rows.For focus: In some cases, switching rows in a default editable detail grid moved the focus to the parent grid or lost it compl- In forms and grids (editable, or with Auto-edit enabled), clicking a read-only cell in a record other than the active one moved the focus to the first editable field. Now, the column of the clicked cell stays active, so the filter pop-up also opens with the focus on that column. etely. This has been fixed. When users switched between component tab pages, the search in the action bar kept taking the focus. This has been fixed. Previously, when a document opened with a form as its top-left component, the focus sometimes went to the second field of the form. This happened when the first field had a barcode scanner or lookup control. This has been fixed. For maps:When a user selected another row, the marker's pop-up on the map no longer opened automatically. This has been fixed. The Maps component turned partially gray after switching component tab pages and back, opening a document and back, or moving a splitter. This has been fixed.Other fixes:After reordering rows by drag-and-drop in a nested detail grid, the grid kept showing the old order until the data was reloaded. Users could think the reorder had failed, even though the new order was saved. Now, the grid shows the new order immediately. In edit mode, a HTML control would not load HTML that contained an <img> tag without image data, such as <img src="data:image/png;base64,">. This has been fixed. Added Clear and Today translations to the calendar of a Date control. You can change the translations by changing the translation objects clear and date_today. A modal document with a hidden footer showed extra empty space at the bottom. This happened if Hide breadcrumb was enabled for its screen type. This has been fixed. On screens with nested tabs, adding a record sometimes did not open the tab with the form. Because the other tabs are disabled while adding, users could get stuck. This has been fixed. When users imported data from the clipboard (overflow menu > Import > Use clipboard as data source) with Date format or Number format set to Based on browser, the import failed. This has been fixed. Uploading a file or image in a default editable screen sometimes did not work correctly. This has been fixed. When a task sent a progress update with tsf_send_progress before its progress dialog opened, the first message and percentage were missing. Users did not see that update, even though the task kept running. This has been fixed. Data model changesData model changes for the Software Factory and IAM meta-models are listed here. This overview can be used as a reference to fix dynamic control procedures, dynamic model code or custom validations after an upgrade.Table changes in the Software FactorySF - From table SF - To table - model_vrs_clean_up Column changes in the Software FactorySF - Table SF - From column SF - To column Mandatory Default value execute_source_code job_id connect_to_db_job_id 1 - execute_source_code_log job_id connect_to_db_job_id 1 - execute_source_code_step job_id connect_to_db_job_id 1 - execute_source_code_step_log job_id connect_to_db_job_id 1 - sf_configuration - model_vrs_retention 1 -1 usr - exempt_from_exclusive_access 1 0 Table changes in the Intelligent Application ManagerNo changes in this release.Column changes in the Intelligent Application ManagerIAM - Table IAM - From column IAM - To column Mandatory Default value appl_db_deployment_run_log message deployment_run_msg 1 -  Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!.

Related products:Software FactoryIntelligent Application ManagerUniversal UIIndicium Service Tier
🚀 Platform improvements for week 43, 2026

🚀 Platform improvements for week 43, 2026

Hi everyone!We've released the following platform improvements this week: SF 2026.320261021 - Fix ordering of references in rename tasks Renaming a table or process action could fail because child objects were added before their parent. This was already fixed in 2026.3.11 and is now also available for 2026.3.   SF All supported versions20261022 - Add missing action bar actions In 2024.3.13 we released the action bar actions Collapse all and Expand all, which collapse or expand a Tree component. Only a hotfix for that release added them to existing action bars, so environments that upgraded past it never got them. This hotfix adds both actions to every branch with an action bar that is missing them.   20261022 - Apply variant rights to form fields and task and report parameters Form fields and task and report parameters used the rights of the base object instead of those of the variant. As a result, a task parameter could be shown even though it was hidden in the task variant. This has been fixed. SF 2026.2, 2026.1, 2025.3, 2025.2, 2025.120261022 - Rename table fix for task variant look-up settings Renaming a table failed with an error when a task variant had look-up settings for that table. This has been fixed.  SF 2026.2, 2026.1, 2025.320261022 - Fix for user start objects After a model was synchronized to IAM, favorites that users had added in the Universal GUI could disappear. This affected favorites that did not use a variant. This has been fixed. In version 2026.1, this hotfix also fixes an issue where favorites with a long name could be saved incorrectly.

Related products:Software FactoryIntelligent Application Manager
Extra release - Universal GUI 2026.3.10.1
🚀 Platform improvements for week 41, 2026
Release notes Thinkwise Deployment Center 4.0.0

Release notes Thinkwise Deployment Center 4.0.0

Hello everyone,In this release, we have added support for deploying IAM to IBM Db2 for i databases, from both the GUI and the command-line interface. To make this possible, we have introduced manifest schema version 4, which allows a single manifest to contain packages for multiple database platforms. We have also added a dependency check for SQL Server 2022, and the command-line interface is now available for Linux.Upgrade to version 4.0.0 of the Thinkwise Deployment Center. It remains fully backward compatible with existing SQL Server manifests and scripts.Windows SmartScreen may prevent you from opening the application. To solve this, open the properties of the executable and select Unblock. Then open the application again.Download the Thinkwise Deployment Center 4.0.0 here. ContentsBreaking DbConnection settings in 'twdeployerGUI.appsettings.json' New in the Thinkwise Deployment Center Support for IBM Db2 for i  Required for Db2: the IBM i Access ODBC Driver Manifest schema version 4 Compatibility level 160 (SQL Server 2022) Command-line interface for Linux Changed in the Thinkwise Deployment Center Connection settings per database platform .NET 10 Questions or suggestions?BreakingDbConnection settings in 'twdeployerGUI.appsettings.json'GUIThe DbConnection section of twdeployerGUI.appsettings.json is now divided per database platform. This only applies to the GUI. The command-line interface does not use a appsettings.json file, so existing CLI scripts are not affected. Move your existing settings into a SQLServer or DB2 sub-section in the twdeployerGUI.appsettings.json. Otherwise, the Server Connection step no longer fills in these settings for you. Before:"DbConnection": { "Host": "example.com\\instance", "AuthenticationMethod": "UserPassword", "Username": "sa"}After:"DbConnection": { "SQLServer": { "Host": "example.com\\instance", "AuthenticationMethod": "UserPassword", "Username": "sa" }, "DB2": { "Host": "IBMI-SYSTEM", "Username": "<IBM i USER PROFILE>" }} New in the Thinkwise Deployment CenterSupport for IBM Db2 for iGUI CLIWith the Thinkwise Platform 2026.3 release, you can now deploy IAM to IBM Db2 for i databases. In addition to SQL Server, you can install, upgrade, hotfix, and synchronize IAM on an IBM i system.GUI When the manifest offers packages for more than one database platform, the Server Connection step shows a new Provider field. Select IBM DB2 to deploy to an IBM i system.Db2 connections use Username/password Authentication. The SQL Server Encryption and certificate options do not apply, so they are hidden. The library to deploy to takes the place of the database name. System libraries are excluded when you browse for a library.CLI The IAM commands (iam install, iam upgrade, iam hotfix, iam sync-model, and iam auto) have a new --rdbms option. Use it to select the database platform to deploy to: SQLServer or DB2.When you do not specify --rdbms, the platform is taken from the manifest. If the manifest contains packages for more than one platform, the Deployment Center uses SQL Server. Existing scripts against a SQL Server-only manifest keep working unchanged. Db2 always connects with an IBM i user profile and its password, so -u|--username is required. If you specify an authentication method that Db2 does not support, such as a Microsoft Entra method, you now get an error immediately instead of when connecting. Pass the library to deploy to with -n|--name, in place of the database name.Example:twdeployer iam install --server "IBMI-SYSTEM" --name "TW_IAM" --rdbms DB2 --username "<IBM i USER PROFILE>" --password "<USER PROFILE PASSWORD>" Select IBM DB2 as provider on the Server Connection step Required for Db2: the IBM i Access ODBC DriverGUI CLIThe Thinkwise Deployment Center connects to Db2 for i using ODBC. You must install the ODBC driver separately on every machine that deploys to Db2 as it is not included in the Deployment Center.Register the driver under the name IBM I Access ODBC Driver. The Deployment Center looks for the driver by this exact name. When it cannot find the driver, it shows the following message: ‘The IBM i Access ODBC Driver does not appear to be installed on this machine. Install it before deploying to a Db2 database.’.Windows installationDownload IBM i Access Client Solutions - Windows Application Package from IBM: IBM i Access Client Solutions (a free IBM ID is required). Run the installer and make sure the 64-bit ODBC driver is included. Verify the installation by opening ODBC Data Sources (64-bit). The driver IBM i Access ODBC Driver should be listed on the Drivers tab.Linux installationOn Linux, the driver is part of IBM i Access Client Solutions - Linux Application Package. It requires the unixODBC driver manager.Download the Linux Application Package (.deb or .rpm) from IBM i Access Client Solutions, or install it from the IBM i Access ODBC package repositories. Install unixODBC and the driver:# Debian / Ubuntusudo apt install unixodbcsudo apt install ./ibm-iaccess-<version>_amd64.deb# RHEL / Fedorasudo dnf install unixODBCsudo dnf install ./ibm-iaccess-<version>.x86_64.rpmVerify that the driver is registered under the correct name. The output should contain [IBM i Access ODBC Driver].odbcinst -q -d   Manifest schema version 4GUI CLIWe have added support for manifest schema version 4. The IAM product can now declare a providers list. This way, you can ship IAM packages for both SQL Server and Db2 in a single manifest. Each provider has its own version, dependencies, and packages.Manifests that use schema version 2 or 3 remain supported. The Deployment Center reads them as SQL Server products. { "schema": 4, "products": [ { "type": "IAM", "version": "2026.3", "providers": [ { "provider": "SQLServer", "dependencies": [ "CompatibilityLevel160" ], "packages": [ { "type": "Install", "path": "IAM/SQLServer/Install" } ] }, { "provider": "Db2fori", "packages": [ { "type": "Install", "path": "IAM/Db2fori/Install" } ] } ] } ]} Compatibility level 160 (SQL Server 2022)GUI CLIWe have added support for the database dependency CompatibilityLevel160. The Dependency Check step now checks whether the compatibility level of the database is set to 160 or higher (SQL Server 2022). Command-line interface for LinuxCLIThe Thinkwise Deployment Center command-line interface (twdeployer) is now also available for Linux. This way, you can run deployments from Linux build agents, containers, and servers, without a Windows machine. The commands and options are the same as on Windows.The following builds are available:Platform GUI CLI Windows x64 ✔ ✔ Linux x64 (such as Ubuntu, Debian, and RHEL)   ✔  The Linux builds are self-contained, so you do not need to install a .NET runtime. After you extract the files, make twdeployer executable:chmod +x twdeployer./twdeployer --version Changed in the Thinkwise Deployment CenterConnection settings per database platformGUIPreviously, the Deployment Center remembered the last used database connection settings globally for all database platforms. It now remembers them per database platform.When you switch the Provider on the Server Connection step, the Deployment Center fills in the fields with the values you used last for that platform. .NET 10GUI CLIWe have updated the Thinkwise Deployment Center to .NET 10. All builds are self-contained, so you do not need to install a separate .NET runtime. Questions or suggestions?Questions or suggestions about the release notes? Let us know in the Thinkwise Community!

Related products:Deployment Center
Thinkwise Platform 2026.3

Thinkwise Platform 2026.3

Note: The original voice-over was lost after our Platform Ambassador spoke at the Thinkwise Summit. This video is an AI-generated replacement created with Claude Opus 5.5. With Thinkwise Platform 2026.3, the Model Context Protocol (MCP) changes how you interact with your Thinkwise applications and their data. MCP support was introduced as beta release in Thinkwise Platform 2026.2.12 and is generally available with this LTS release. You can connect any MCP client, such as your preferred AI tool, to your business applications and the Software Factory using the /mcp endpoint in Indicium. Instead of navigating to the right screen and searching for data manually, you can ask your AI tool to find and analyze the data for you. Adding data becomes easier too, because your AI tool can turn unstructured input, such as an email, document content, or a voice message, into structured data in your database without any manual typing.Because the MCP server is built into Indicium, you do not need any additional components; you set up MCP and manage its access in the Intelligent Application Manager (IAM). To give AI tools and AI agents secure and granular access, follow our best practices for role-based access control, access delegation, and logging. MCP is freely available in development and test environments, so you can speed up development in the Software Factory and test MCP with end users. Using MCP in production requires an amended license agreement with Thinkwise, so contact your account manager for more information.To learn more, read our Community blogs Thinkwise Platform as MCP Server, Getting started with MCP, and MCP on the Software Factory.You can also use MCP on the Software Factory, and together with our published skills, it significantly changes the way developers work. Your AI agent can take on tasks such as creating a data model, creating screen types, and setting up a Scheduler, so you can spend more time understanding, describing, and refining business needs. You can also hand over repetitive work while you review and decide, such as finally adding those missing unit tests for existing functionality. Unlike vibe coding, where AI leaves you with a mountain of generated code to maintain, your AI agent works with the model. This model-driven development and Technology-as-a-Service approach lets you deliver business value with as little code as possible.The MQTT broker capabilities from Thinkwise Platform 2026.2 let you publish messages, and with this release, you can also subscribe to MQTT topics. A subscription listens to a topic on your message broker and starts a process flow every time a message arrives, whether it comes from a machine, a sensor, or another Thinkwise application. Your applications can now receive sensor data and machine status updates directly, enabling real-time interaction between the shop floor and your business applications.With IAM on DB2 for IBM i, we take a major step toward running the entire Thinkwise Platform on IBM Power. We have already proven that it works, and we are now completing a dedicated Indicium distributable for IBM Power. You can then deploy Indicium and the Universal UI on a Red Hat Linux partition, on the same IBM Power machine that runs your DB2 databases.The inline action bar is our answer to a long-standing and popular community idea: showing tasks on grid rows. We took this idea further, so you can now configure any action inline. Note that this is still a beta feature. We plan to improve the user experience and add support for card lists.Besides MCP, developers also get a major upgrade to Model insight and the Thinkwise Workspace Listener for Linux and macOS. Thinkwise Deployment Center 4.0.0 is now also available for Linux, and you can use it to deploy IAM on DB2.This release includes 19 community ideas, representing 367 votes.A full overview of all the release notes of the Thinkwise Platform 2026.3 is available now!The Indicium and Universal UI 2026.3.10 features below are backwards compatible with previous Thinkwise Platform versions. Therefore, these fixes are not part of the release notes for Thinkwise Platform 2026.3.ContentsBreaking Important: Redeploy required objects to DB2 application schemas Restricted file access outside the base path Check custom CSS Removed support for Thinkwise Platform version 2024.3 New and changed in the Universal UI and Indicium (2026.3.10) Configurable timeout for i-net Clear Reports Select resources directly in the Scheduler Search and open documents pinned in the menu Application backplate shown after switching applications MacOS-specific keybind text in shortcut labels Fixed Indicium Universal UI BreakingImportant: Redeploy required objects to DB2 application schemasSoftware Factory DB2From Thinkwise Platform 2026.3, Indicium requires the following functions and procedures on the schema of DB2 applications:tsf_user and tsf_original_login - If these are not updated, user authorization does not work as expected. tsf_set_session_variable and tsf_clear_session_variables - If one of these is missing, Indicium cannot open connections to the application database.The DB2_DB base model adds these objects to your work model. You still need to deploy them to your application schema.Required action for all DB2 applicationsDeploy these objects directly after upgrading to Thinkwise Platform version 2026.3. Without these steps, the upgrade to 2026.3 does not succeed for DB2 models.To deploy the objects:Go to menu Business Logic > Functionality. Deactivate the prefilter Hide generated. Search for the object name, see the list above. Deploy the object to your application on the tab Deploy.Alternatively, upgrade the DB2 applications. The upgrade applies these objects automatically. Restricted file access outside the base pathIndiciumPreviously, in non-database file storage configurations, file paths outside the configured base file storage path could still be retrieved, downloaded, and previewed.From Thinkwise Platform version 2026.2.14 onwards, the database record is retrieved successfully, but with an invalid file contract. Trying to download or preview the file now returns a 404 Not Found error.Check that your file paths are within the configured base file storage path. To temporarily restore the previous behavior, set the extended property AllowPathOutsideBasePath to True. Only use this setting as a temporary solution, as it will be removed in a future release. Check custom CSSUniversal UIAs a result of improvements to the Scheduler in Thinkwise Platform version 2026.2.14, the structure of the HTML and the CSS classes used have changed significantly.If you have custom CSS for the Scheduler, review your styles and update the selectors if necessary. Contact support if any selectors are missing. Removed support for Thinkwise Platform version 2024.3Indicium Universal UIIn accordance with our lifecycle policy, we have removed support for Thinkwise Platform version 2024.3 in Indicium and Universal UI.Upgrade to Thinkwise Platform version 2025.1 or higher. New and changed in the Universal UI and Indicium (2026.3.10)Configurable timeout for i-net Clear Reportschange IndiciumPreviously, the timeout for generating reports with i-net Clear Reports was raised from 100 seconds to 5 minutes. Some reports need even more time than that, so you can now configure the timeout with the extended property clearReportTimeoutSeconds. The value is in seconds. If you do not set this property, the default of 5 minutes (300 seconds) still applies. Select resources directly in the Schedulernew Universal UIUsers can now change the active record of a resource by directly clicking on it in the Scheduler.The user can select a resource in the following ways:Selecting a resource directly in the Scheduler. Selecting a resource's activity. Selecting the corresponding record in another screen component, such as a form or grid.Once a resource is selected, the active record is shown in other screen components, such as a form or grid. Similarly, if the user changes the active record of a resource in another screen component, the corresponding resource in the Scheduler is highlighted.For example, if a user clicks on employee in the Scheduler, the data of that employee is displayed in the form. If the user then selects a different employee in the grid, the corresponding resource in the Scheduler is highlighted. This improves the user experience by keeping related screen components in sync and making it easier to navigate between resources and their corresponding records.Screen components show the active record of the selected resource Search and open documents pinned in the menuchange Universal UIPreviously, when a user scrolled in the sidebar menu, the Search field and the Open documents section scrolled out of view. Now, they stay pinned to the top of the menu while the rest of the menu scrolls underneath. This way, users can use them to navigate and to see the current state of the application. The collapsed state of Open documents is remembered across sessions.Search and open documents pinned in the menu  Application backplate shown after switching applicationschange Universal UIPreviously, when a user switched to another application using the application switcher, the previous application's document remained on screen. Because it was shown in the new application's theme, it could be unclear which application the document belonged to.Now the new application's backplate is shown, with the focus on the menu. The previous application's document remains available in the Open documents section. When a user selects it, the theme and menu switch to the application it belongs to. MacOS-specific keybind text in shortcut labelschange Universal UIShortcut labels used to show the same key combination on every operating system.On MacOS, shortcut labels now show MacOS-specific keybinds. Instead of Ctrl + E, the edit shortcut now shows Cmd + E.The shortcut itself still works the same way on every operating system. If you connect a Mac keyboard to a Windows computer, Cmd + E still works. On MacOS, Ctrl + E still works too.For non-MacOS users, nothing changed. Mobile devices still do not show shortcut labels. FixedIndiciumWith the extended property IgnoreDiacritics enabled, Search did not ignore diacritics if the lookup column was part of the primary key. This has been fixed.Universal UIUsers can sort a column by selecting its header in ascending or descending order, but could not disable sorting. This has been fixed. Sorting of grouped columns has not changed. When the parent record changed, sub-details nested under an unrelated detail lost their data. Their tabs stayed empty until you selected Refresh. This has been fixed. In a pivot table, selecting a row label, such as an employee, and then starting a task or report opened it with empty parameters. This has been fixed. In a Date control, you could not type a date later than 31/12/2500. This has been fixed. You can now type dates up to 31/12/9999. The date picker still goes up to 31/12/2500. When you went from a subject with an active variant to a detail without one, Model insight still showed the variant of the previous subject. Now, it hides the variant in this case. In a form, radio button labels did not line up vertically with other fields. Also, a radio button field that shared a row with another field could be too narrow. As a result, its option labels could be cut off or overlap. This has been fixed. Previously, when executing the Go to row process action, the newly added grid row would in some cases not automatically become the active row. The screen had to be refreshed manually for this to take effect. This has been fixed. In some cases, the action bar did not fully fit the screen and the Search field was next to the overflow menu. The overflow menu then sometimes opened unexpectedly. This has been fixed. When the action bar did not fully fit the screen, it would shift around when you opened a document. This behavior has been improved. Added translations for the NOT IN operator for older platform versions. When tasks are disabled, they are grayed out in the user interface and cannot be selected. Previously, a disabled task could still be executed using its keyboard shortcut. This caused the application to freeze, requiring users to restart it manually. This has been fixed. Users can no longer trigger a disabled task using its keyboard shortcut.

Related products:Software FactoryIntelligent Application ManagerUniversal UIIndicium Service Tier
Release notes Thinkwise Platform 2026.2.14

Release notes Thinkwise Platform 2026.2.14

Hi everyone,This release extends deployment control to IAM administrators and strengthens governance for delegated and AI-driven access. Note that this release includes several breaking changes, covering the Execute all creation steps parameter order, Indicium file access, and Scheduler and theme behavior.To support safe delegated and AI-driven access, branches can now allow delegated mutations from a personal access token (PAT) or client application. The trace fields now show whether a change came through delegated access instead of directly from a user. The Software Factory also introduces eight default user groups, so you can scope down what developers and AI agents can do.Based on a request from the community, models with a single database type can now always show query details, for instance, to view historical versions of a query.Several quality-of-life improvements round out this release. Indicium can now resolve a lookup when patching a staged resource, and no longer requires create schema and create table permissions on the IAM database. In the Universal UI, keyboard focus improves when opening or switching documents, and Search bars can now be reached with a keyboard shortcut. The new  ‘NOT IN’ filter operator lets you exclude multiple values at once.Thinkwise Platform 2026.3 releases on October 5, 2026, shortly after this release. Because the two versions are released close together, the differences between them are limited.This is a short-term support (STS) release of the Thinkwise Platform. STS release support expires as soon as a new release is made available. For example, support for version 2026.1.12 ends when version 2026.1.13 is released.See our Lifecycle policy for information about supported versions.ContentsContentsContents Before you upgrade Demo and download Breaking Check parameter order of 'Execute all creation steps' calls Restricted file access outside the base path Check custom CSS Check application themes Model Context Protocol (MCP) and AI Models - Allow delegated mutations for a branch Generic - Delegated access trace field Deployment Deployment - Synchronization runs before the tests in Creation New and changed Data - Removed case type setting for columns, task parameters, and report parameters Quality - Description column in Code review changes Processes - Process action 'Activate Search' Access Control - Default user groups for the Software Factory Deployment - Application database name in post-synchronization code Analysis - Changed function point calculation to Easy Functional Sizing (ISO/IEC 25986) Maintenance - Toggle to show query details for single-RDBMS-type models Updated required permissions for Indicium for IAM databases Patch a staged resource with a lookup translation Server timings in response header Removed unused grant types in OpenID metadata document Updated Next.js to 16.3.3 Improved screen component focus Improved Search Show subtitles for focused detail subjects in Open documents Selection order stored for multi-row selections Enforce automatic 'Show top X' limit for cube views Combined filter search with 'Enter' Support for 'NOT IN' operator Model insight includes screen component ID Improvements to column header filter Autofill on fields no longer available Fixed Software Factory and Intelligent Application Manager Indicium Universal UI Data model changes Changes Software Factory Table changes Column changes Changes Intelligent Application Manager Table changes Column changes Before you upgradeFeatures for the Software Factory and the Intelligent Application Manager are only compatible with this STS version of the Thinkwise Platform. Indicium and Universal UI features are backward compatible with previous Thinkwise Platform versions, unless otherwise noted.Demo and downloadTry a demo of the Thinkwise Platform here. Download the latest versions of our components here. BreakingCheck parameter order of 'Execute all creation steps' callsSoftware FactoryAs a result of synchronization running before the tests in Creation, the parameter order of the task Execute all creation steps has changed.The synchronization parameters run_sync, sync_run_type, and sync_target_iam_id now come before execute_unit_tests and execute_smoke_test.If you start the task with named parameters, nothing changes for you.If you call the task directly from the database without parameter names, the values now bind to different parameters. No error message appears, so the task runs with settings you did not intend. For example, the task now reads a call that meant "run the tests, do not synchronize" as "synchronize to storage, do not run the tests."Positions 1 to 14 are unchanged. Following the CI/CD example from the previous release, the new order for positions 15 to 22 is:New parameter orderexecute_source_code_error_handling run_sync sync_run_type sync_target_iam_id execute_unit_tests execute_smoke_test debug job_idUse named parameters to avoid this. Supply every parameter, because the task procedure has no default values. You can pass null for parameters that your selected creation steps do not use:For example:declare @job_id id;exec dbo.task_add_job_to_do_complete_creation @model_id = 'MY_MODEL', @branch_id = '1.12', @execute_complete_creation = 0, @model_vrs_name = '1.13', @generate_definition = 1, @generate_definition_error_handling = 1, @validate_definition = 1, @validate_definition_error_handling = 3, @generate_source_code = 1, @upgrade_method = 0, @write_code_files = 0, @write_prog_objects = 0, @execute_source_code = 0, @runtime_configuration_id = null, @execute_source_code_error_handling = null, @run_sync = 1, @sync_run_type = 0, @sync_target_iam_id = 1, @execute_unit_tests = 0, @execute_smoke_test = 0, @debug = 0, @job_id = @job_id output; Restricted file access outside the base pathIndiciumPreviously, in non-database file storage configurations, file paths outside the configured base file storage path could still be retrieved, downloaded, and previewed.Now, the database record is retrieved successfully, but with an invalid file contract. Trying to download or preview the file now returns an 404 Not Found error.Check that your file paths are within the configured base file storage path. To temporarily restore the previous behavior, set the extended property AllowPathOutsideBasePath to True. Only use this setting as a temporary solution, as it will be removed in a future release. Check custom CSSUniversal UIAs a result of improvements to the Scheduler, the structure of the HTML and the CSS classes used have changed significantly.If you have custom CSS for the Scheduler, review your styles and update the selectors if necessary. Contact support if any selectors are missing. Check application themesUniversal UIPreviously, if a theme only had one image configured for either Light or Dark mode, the Universal UI would display that image for both modes. Now, the Universal UI displays the background color for the mode that does not have an image configured.After upgrading, check your themes in Light and Dark mode to ensure they behave as expected. Model Context Protocol (MCP) and AIModels - Allow delegated mutations for a branchnew Software FactoryIt is now possible to allow a PAT or client application to edit a branch via delegated access on behalf of a developer. You can use this to determine which branches can be edited via delegated access, which is useful for MCP in the Thinkwise Platform.You can find the checkbox Allow delegated mutations in the following locations:menu Model overview > Branches > Form. When you create a new branch via the menu Models > Switch branch. Generic - Delegated access trace fieldnew Software FactoryYou can now see whether a record was changed through delegated access, such as a personal access token (PAT) or an agent with the correct permissions.The trace fields now include a Modified delegated access checkbox. It is selected when the last insert or update on a record was made via delegated access rather than directly by a user. Any manual change to the record clears the checkbox.The 'Modified delegated access' checkbox in the trace fieldsDeploymentDeployment - Synchronization runs before the tests in Creationchange Software FactoryIn the previous release, we added synchronization to IAM to the Creation process. It ran as the final step, after the unit tests and smoke tests. However, during development, you often want your model available in IAM as soon as the application database is up to date. You do not want to wait for the tests to finish. For this reason, we moved synchronization earlier in the process. Moved synchronization before the tests - Synchronization now runs directly after the tab Execute source code, before the unit tests and the smoke tests. Your model becomes available in IAM sooner, so you can continue working with it while the tests run. Because each creation step waits for the previous one, this also reverses which step cancels which. Before, a failed unit test or smoke test canceled synchronization. Now, a failed synchronization cancels the unit tests and smoke tests. Moved the Synchronization to IAM tab - The tab now appears directly after the tab Execute source code (menu Deployment > Creation). Changed the order of the options - In the task Execute all creation steps (menu Deployment > Creation > Generate definition > Current), the synchronization options now come before the test options. The same order applies to the screen Creation presets (menu Maintenance). Your existing creation presets retain their settings after this update, and the new order applies to every creation. Changed the job that the task returns - The task returns the job of the last step in the Creation process. This is now the smoke test instead of the synchronization job. Automation that waits for this job still waits for the whole Creation process to finish. Breaking: Changed the parameter order of the task Execute all creation steps - See Check parameter order of 'Execute all creation steps' calls for more information.  New and changedData - Removed case type setting for columns, task parameters, and report parameterschange Software FactoryPreviously, you could set the Case type to determine the capitalization of text for individual columns, task parameters, and report parameters. This capability has been removed to keep the case type defined in a single place and reduce the risk of inconsistencies. You can still define the Case type for a domain.When upgrading to this version, the existing case type settings for individual columns, task parameters, and report parameters are migrated to new domains. Quality - Description column in Code review changeschange Software FactoryPreviously, the tab Changes in Code review did not show the description of a changed control procedure or template. You can now see this in a new Description column (menu Quality > Code review > tab Changes). It shows the control procedure description or the template description, depending on which object changed.The new 'Description' column in the Code review changes tab Processes - Process action 'Activate Search'new Software Factory Universal UIWe have added a new process action: Activate search (menu Processes > Process flows > tab Process actions). You can use it to activate the Search field in the context of a table. No input parameters are required for this process action.The process action cannot be used as a trigger or starting step in a process flow. It is useful to bring focus to the search field in a table after performing other actions in a process flow. Therefore, it is typically used as the last step in a process flow.For example, after a user selects a record in the main subject, the process flow can bring focus to the search field in the detail subject. This allows the user to continue their work seamlessly.This process action was added as part of Improvements to search in the Universal UI.Screen component tabs are automatically opened by this process action. However, detail tabs must be activated using the process action Activate detail. Access Control - Default user groups for the Software Factorynew Software FactoryYou can now limit what developers can do in the Software Factory using eight default user groups. This helps restrict access for AI agents and lets you scope down roles for specific tasks. For example, you can limit testers to registering test findings only, rather than giving them direct access to the data model, functionality, and more. You can create custom user groups in IAM based on these default roles.application_logic_developer - Writes business logic and behavior: process flows, tasks, reports, functionality, and the dynamic model. data_subject_modeler - Builds the data layer and how it is consumed: table, column, and domain design, plus settings for individual subjects. integration_automation_engineer - Sets up external connections and database- and AI-driven automation: all of integration and AI, plus enrichments and the Thinkstore. platform_model_administrator - Oversees the Software Factory rather than contributing directly: the whole model group, plus the non-QA-related half of Analysis. qa_test_engineer - Verifies quality and its dashboards: the entire quality menu group, plus the test- and validation-related parts of Analysis. rbac_administrator - Sets up who can do what and who they are: everything related to access control and user management. release_deployment_manager - Ships and operates: deployment, plus the operations side of Maintenance, such as runtime configuration, hotfixes, and jobs. ui_ux_navigation_modeler - Sets up the shell around the data, not tied to any one table: modeling the application's UI, navigation, and messaging. Deployment - Application database name in post-synchronization codenew Software FactoryYou can now use the name of your application database in post-synchronization code within a deployment package, using the new variable @tsf_appl_db_name. This variable sits alongside the existing @model_id and @branch_id variables.Post-synchronization code often needs to find or create the application registration in IAM for the database a deployment targets. With this variable, the same deployment package works in every environment, without hardcoding the database name into the code.You can add this code in the menu Deployment > Deployment package > tab Post synchronization code. The Deployment Center automatically sets the variable to the application database name.If you run the generated synchronization script yourself instead of through the Deployment Center, the script carries the SSMS template parameter <@db_name,,> in that position. Fill it in with the application database name to use the variable, or leave it untouched to keep the variable empty.For example, to look up the application database registration for the current deployment:declare @database_id idselect top 1 @database_id = database_idfrom appl_dbwhere db_name = @tsf_appl_db_nameThe variable @tsf_appl_db_name is not available for post-synchronization code for Synchronization to IAM or Synchronization to storage.Deployment application database name in post-synchronization code Analysis - Changed function point calculation to Easy Functional Sizing (ISO/IEC 25986)change Software FactoryYou can automatically calculate the number of function points for your application using the task Calculate function points (menu Analysis > Function point analysis).The task now uses Easy Functional Sizing (ISO/IEC 25986), a streamlined function point standard developed by Nesma (Netherlands Software Metrics Association) that measures the functional size of software. This standard allows you to compare objective metrics across your applications, such as:Productivity - effort hours spent per function point delivered. Cost efficiency - cost per function point delivered. Delivery speed - function points delivered per month.These metrics can be aggregated at different levels to support data-driven decision-making.Our implementation of Easy Functional Sizing (ISO/IEC 25986) is certified by AgileBenchmark. You can request the certification details via your Thinkwise account manager. Maintenance - Toggle to show query details for single-RDBMS-type modelsCommunity idea new Software FactorySince Thinkwise Platform version 2026.2, query data is stored in a dedicated query table per query type, for example tab_prefilter_query for prefilter queries. For models with a single RDBMS type, the detail tab showing this record was hidden because it held only one value.You can now always show these detail tabs, for example to view historical versions of a query. Select Always show query details in the menu Maintenance > Users > tab General.Select the checkbox 'Always show query details' Updated required permissions for Indicium for IAM databaseschange Intelligent Application Manager IndiciumIndicium no longer requires 'Create schema' and 'Create table' permissions on the IAM database from Thinkwise Platform version 2026.2.14 onwards.The following permissions for the database pool user (or maintenance pool user) are sufficient for SQL Server databases:USE [db_name]GRANT SELECT, INSERT, UPDATE, DELETE, EXECUTE ON SCHEMA::dbo TO [user];Note that creating a new database from the Software Factory does require the additional permission:USE master;GRANT CREATE ANY DATABASE TO [login_name]; Patch a staged resource with a lookup translationnew IndiciumPatching a staged resource now supports resolving a property's value via choose, choose_by_display, or choose_by_element. This is similar to what we already support for patching on a table directly.For example, if you have a column named manager_id, Indicium can now look up the matching key for you, so you do not need to know it in advance. PATCH the staged resource like this:PATCH /iam/<appl>/staged_employee(#) HTTP/1.1Content-Type: application/json{ "manager_id": { "choose_by_display": { "display_value": "<Manager Name>" } }} Server timings in response headerchange IndiciumIndicium now adds server timings in the response header even if the timed action results in an error. Previously, this was not the case; server timings were only added when the timed action succeeded. Removed unused grant types in OpenID metadata documentchange IndiciumIn the OpenID metadata document, unused grant types have been removed to better reflect the capabilities of our OpenID clients. Updated Next.js to 16.3.3change Universal UIWe have updated Next.js from version 16.2.11 to version 16.3.3. This update addresses two reported vulnerabilities, GHSA-2xp9-vwfh-vxw4 and GHSA-p293-qw3h-jr36. Although Universal UI was not affected by either vulnerability, we updated Next.js anyway to include the latest security and performance fixes. Improved screen component focusnew Universal UIWe have improved the initial focus behavior when opening or switching between documents. This update improves keyboard navigation and overall user experience.The focus behavior is as follows: By default, focus is placed on the most top-left interactive component of the main subject. Focus is placed on the Search element whenever the first interactive component is an action bar with a Search element. This allows users to immediately filter data upon opening the document. If the Search element is displayed as an icon, it expands to reveal the search bar. Users navigate away from it using the Esc key. If the action bar has no Search element, focus is placed on the next screen component (for example, Grid, Tree, or Cardlist). This allows users to immediately navigate within the screen component. Focus is placed within a detail tab if it is the most top-left interactive component of the main subject. Tab bars are never focused when opening a document or switching between documents. Users can use F6 or Shift + F6 to navigate to the tabs. When no documents are opened, focus is placed on the menu's search bar. This focus behavior applies in the following situations:Opening a document Switching between documents Opening a document as a Modal document (by using Shift + Click) Opening a document as a Zoomed document (by double-clicking a detail tab)This focus behavior does not yet apply to nested detail tabs or lookup pop-ups. Support for these is planned for a future update. Improved Searchnew Universal UIA Search bar in a screen component can now be quickly focused using the shortcut Ctrl + K. When multiple Search bars are present (for example, if each tab or screen component has one), the priority is as follows:If a Search bar exists on the current tab, this is focused. If not, but a Search bar exists on an ancestor tab, this becomes focused. If not, but a Search bar exists on a child tab, this becomes focused.This also works for icon-only Search bars and even if it is inside the overflow menu. Note that the sidebar menu has its own Search bar, which can now be quickly focused using the shortcut Alt + M.As part of this update, we also added the process action Activate search, allowing you to activate the Search field in the context of a table. See also Process action 'Activate Search'.Use keyboard shortcuts to quickly focus the different 'Search' bars in the Universal UI Show subtitles for focused detail subjects in Open documentsnew Universal UIThe option to add subtitles to open documents was introduced in the 2026.2.12 release, allowing the active record context to be displayed. Open documents now also show the subtitles of focused detail subjects. If the detail subject is nested several levels deep, the subtitle displays a condensed version of its path. Selection order stored for multi-row selectionsnew Universal UIIn grids or trees with multirow selection enabled, the order in which rows are selected is now stored. Any task executed on the selection now receives the selected rows in the order they were selected, instead of in dataset order.The order depends on how the rows are selected:Ctrl/Cmd + click - Rows are ordered by click order. Deselecting a row with Ctrl/Cmd + click only removes that row from the selection. Shift + click - Rows are ordered from the anchor row towards the clicked row, with the clicked row last. Shift + arrow keys - The anchor row is first, and the other rows follow in the order they are added. Reversing direction now correctly shrinks the selection, deselecting rows one by one as the cursor moves back through the previously selected range. Ctrl + A - Rows follow the dataset order. Enforce automatic 'Show top X' limit for cube viewschange Universal UI Software FactoryPreviously, if a cube view had no Show top x value configured, all records would be loaded. This could result in performance issues, especially for applications with large datasets.The Universal UI now automatically caps the number of items displayed on each axis to 1000 if no Show top x value is configured. If you have configured values for Show top x on an axis, those settings take precedence over the automatic limit.The limit applies to all cube views in the Universal UI and is enforced separately for each axis and nesting level. Totals and subtotals still reflect the full underlying dataset, not just the items displayed in the cube view. Combined filter search with 'Enter'new Universal UIFor faster search performance, it is now possible to use Enter after entering a value in the Search field in the action bar to immediately trigger the search action. This skips the delay caused by the configured debounce time. Support for 'NOT IN' operatornew Universal UIYou can now exclude multiple values in Filter pop-ups and Filter forms, using the NOT IN operator. Previously, you could only include values through the IN operator when you applied filter conditions with multiple values. Model insight includes screen component IDnew Universal UIThe Screen section of Model insight now includes the screen component ID. This makes it easier to identify the exact screen component you are inspecting, for example when a screen contains multiple components of the same screen type. Improvements to column header filterchange Universal UIPreviously, the column header filter in a grid listed all domain element values, even if no matching records existed in the current dataset. Now, it only shows values present in the current dataset. If filters are applied to the dataset, the shown values reflect the filtered dataset.Additionally, the column header filter now includes a search bar, allowing users to quickly find specific values within the filter options.The column header filter now includes a search bar Autofill on fields no longer availablechange Universal UIPreviously, selecting a field could suggest values that a user previously entered in similar fields. This type of suggestion and autofill is browser-specific behavior and unrelated to, for example, the Software Factory's own controls with suggestions and autofill.We have removed the browser-specific suggestions and autofill. This prevents unwanted behavior where autofill was not working as expected or other fields were cleared after an accepted suggestion.Due to technical limitations, Safari is not included in this change and will still show autofill suggestions based on saved contact information. A user can choose to turn this off in Safari's autofill settings.A browser may still prompt the user to generate and save passwords when entering a value in a password field. If the user disables password management for their application, this should no longer happen. For example, in Chrome this can be done by selecting Never when prompted to save a password:Example: Select 'Never' when prompted to save a password FixedSoftware Factory and Intelligent Application ManagerThe Software Factory allows you to translate check constraints, so you can define a custom error message per language for each constraint violation. Since the introduction of support for multiple RDBMS types for a model in the Thinkwise Platform 2026.2 release, these translations have not been displayed correctly in the user interface. This has been fixed. Previously, if an encrypted Web connection was edited, the Layout logic still required the Password field to be entered, resulting in failed attempts to save the edits. This has been fixed. Previously, an attempt to start a model synchronization to IAM without configured pool user credentials would result in an error message stating that it had been canceled. However, the synchronization run would still proceed and be reported as successful, even though no synchronization had effectively taken place. This fixes an issue already mentioned in the 2026.2.13 version release. Previously, a variant default value query override for a column, task parameter, or report parameter returned NULL through the Indicium interface view. This happened when there was no base default value query, and it led to incorrect behavior. This has been fixed in the platform improvements for week 37, 2026. IAM was not affected. The overall performance of the i_ui_col view in the Software Factory has been improved, resulting in faster screen loading times when developing your applications.IndiciumContent type values for Web connection endpoints rejected charset=utf-8 specifications. For example, text/xml worked, but text/xml; charset=utf-8 did not. This has been fixed. Web connections still only support UTF-8 encoding, so a different charset still results in an unsuccessful status code. DB2 Deleting a record could fail when the subject had an expression field and a SQL authorization prefilter. This has been fixed. Fixed an issue where the Application connector process action returned incorrect status codes if the target database did not exist and Azure Active Directory authentication (for example, Managed Identity) was used. This affected process flows that rely on the status code, such as the Creation screen in the Software Factory. As part of this fix, the Provision database connector timeout has been increased from 30 seconds to 5 minutes. This prevents the provisioning step from failing due to a timeout. Previously, the printing orientation configured in the Software Factory was ignored. This has been fixed in extra release Indicium 2026.2.13.1. The configured orientation now takes precedence over the orientation of the document itself. If you set an explicit orientation, check your printed output. An incorrect setting is now visible in the print result.Universal UIFor the Scheduler:Improved the performance of the Scheduler, for example: when opening a Scheduler, navigating to the next or previous time frame, and when expanding or collapsing all items in a hierarchical Scheduler. Resources are now displayed in the same order as they appear in the dataset. If one of the Activity linked columns (Title, Tooltip, Start date or End date) is within the sort columns, activities within a resource are now displayed in the same order as they appear in the dataset. If vertical space can be saved by moving an activity into an otherwise empty time slot, this will take precedence over the dataset order. Fixed an issue where the conditional layout of a child resource would not be applied after its collapsed parent was expanded by the user. Fixed an issue where the red arrow and line indicating the current time would sometimes be placed incorrectly, for example at the start of the slot for hour "10:00" even though the current time was '10:59'. The Today, Previous, and Next buttons have been moved to the left of the Scheduler toolbar. This aligns with where these buttons are typically placed in other calendar applications. For Scheduler resources that did not use the full height of the Scheduler, a bottom border is now displayed for the last resource to show the end of the resource. Fixed an issue where the Scheduler toolbar would sometimes be sized incorrectly. This occurred in cases where many Scheduler views were configured or if a Scheduler view had long translation labels. Scheduler views with Hours set as the highest timescale now open on the current hour, instead of incorrectly opening on an earlier hour. The arrow and line indicating the current time are now correctly positioned relative to the current hour. Fixed an issue where the first timescale headers (e.g., "2026" or "August") sometimes had a gray background color. Fixed an issue where time cell borders sometimes had a doubled width when cell colors were configured. Previously, when certain network requests were delayed, it was not possible to drag an external row on a Scheduler. This has been fixed.  For cubes:In pivot tables, the highest-level series was not always collapsible or expandable. This has been fixed. In pivot tables, subtotals would sometimes be missing in series. This has been fixed. Weekdays were not translated in a cube, so 1 was displayed as 1 in the user interface. This has been fixed. For example, 1 is now shown as Monday for series and categories, depending on the translation in the Software Factory and the user language.For grids:Previously, when a field in a grid row was changed using a Combobox control before the record was saved, Indicium could apply default values to other fields in the same record (for example, filling in a date or checking a checkbox). These updated values were not displayed in the grid until the record was saved. As a result, the row appeared unchanged despite the defaults being applied. This has been fixed. Previously, for a grid column with checkboxes, the Filter icon could incorrectly show that a filter was active. This could occur, for example, when selecting and clearing the same value in the dropdown until all values were checked again. This was a display issue only, as filtering itself worked as expected. This has been fixed. Previously, executing a task on all selected rows of a page in a grid could cause performance issues. This could occur when Page size was set to a high value, for example 1000 rows. The Universal UI sent a separate request for each selected row, even when the selection matched all rows shown under the current filter. This has been fixed: the Universal UI now sends a single request for the entire selection. Previously, the search terms in Filter form fields using the IN operator could still be removed when the grid was in Edit mode. This has been fixed. Previously, when editing a row in a grid, read-only cells with a lookup had no icon to open a pop-up to view their values. Now, it has one. In a future version, read-only cells with a look-up will be displayed as hyperlinks instead. In some cases, navigating to a different page in a grid would cause the detail tab to display the wrong data. This has been fixed. Previously, automatic refreshes after editing a record, executing, or cancelling a task could override the user's manually selected active record. This occurred if the user selected a different record before the refresh completed. This has been fixed. When Add in grid row was enabled and a checkbox was changed in a copied row, the checkbox in the original row changed too. This has been fixed.For filters:The NOT BETWEEN operator now includes NULL values for column filter conditions in the Filter pop-up, Filter form, and prefilters. Previously, the value entered in an active field would disappear when scrolling down in a Filter pop-up with more than 20 fields. This has been fixed. Previously, Indicium could not provide searches on the columns Date, Datetime, and Time. This resulted in the columns not appearing as searchable columns in the search bar tooltip in the Universal UI. This has been fixed. Previously, the activation of a custom Prefilter was not remembered between sessions. In a new session, it was always inactive. Now, it is remembered.Other fixes:In some cases, the code editor control would not display any content. This has been fixed. Previously, when clicking outside the input window in an HTML or Multiline pop-up editor, any available default procedures were run instead of waiting for the pop-up to be closed. This also happened when the user made an edit in an HTML pop-up editor and then selected one of the available styling buttons. This has been fixed. Previously, the following controls would not adhere to their width setting if they were empty or in edit mode: Email, Url, Phone Number, and Google Maps. This has been fixed. On macOS, Cmd + Click now selects rows in multiselect grids and trees, matching the Ctrl + Click shortcut for Windows. Fixed an issue where exporting selected rows with an invalid OData URL would fail if the primary key was a Date, DateTime, or Time column. When Set tab icons is disabled, icons are no longer requested when rendering a detail tab.Data model changesData model changes for the Software Factory and IAM meta-models are listed here. This overview can be used as a reference to fix dynamic control procedures, dynamic model code, or custom validations after an upgrade.A complete overview of the data model changes is available in the upcoming Thinkwise Platform 2026.3 release next week.Changes Software FactoryTable changesSF - From table SF - To table install_code_file - Column changesSF - Table SF - From column SF - To column Mandatory Default value branch - allow_delegated_mutation 1 0 col case_type - - - control_proc_log - no_of_reads 0 - control_proc_log - no_of_writes 0 - control_proc_log - cpu_time 0 - deployment_run - iam_rdbms_type 0 0 disk_sync_job - iam_rdbms_type 0 0 function_point_analysis_function path - - - model_vrs - from_branch_id 0 - model_vrs - from_model_vrs_id 0 - model_vrs - definition_generation_finish_date_time 0 - model_vrs - archived_date_time 0 - prog_object_item_parmtr - parmtr_value_hash 0 - prog_object_parmtr - parmtr_value_hash 0 - rdbms - is_iam_rdbms_type 1 0 report_parmtr case_type - - - role use_for_ai_assistant - - - sync_target_iam - rdbms_type 1 0 task_parmtr case_type - - - usr - always_show_query_detail 1 0 Changes Intelligent Application ManagerTable changesIAM - From table IAM - To table - appl_db_deployment_run - appl_db_deployment_run_log - prog_object install_code_file - Column changesIAM - Table IAM - From column IAM - To column Mandatory Default value appl_db - last_deployment_run_id 0 - branch - model_vrs_id 0 - branch - from_branch_id 0 - branch - from_model_vrs_id 0 - branch - definition_generation_finish_date_time 0 - branch - archived_date_time 0 - branch - model_last_modified_date_time 0 - branch - model_last_modified_type_of_object 0 - global_settings - appl_db_deployment_run_retention 1 90 msg - alt_transl_msg_id 0 - role use_for_ai_assistant - - -

Related products:Software FactoryIntelligent Application ManagerUniversal UIIndicium Service Tier
Release notes Thinkwise Platform 2026.2.13

Release notes Thinkwise Platform 2026.2.13

Hi everyone,This release brings the community-requested inline action bar to grids, improves IAM synchronization for separated environments, and continues to expand DB2 support. Note that this release includes several breaking changes, including updates to CI/CD invocations, DB2 trigger code groups, and Scheduler and grid behavior.Grids now support an inline action bar, letting users access action buttons directly from the active row without a dedicated toolbar.The Software Factory can now synchronize to IAM using the API instead of requiring direct database access, enabling synchronization in environments where the IAM and Software Factory are separated, such as in the Thinkwise Cloud. Synchronizing is now also available directly from the Creation screen.DB2 support continues to expand towards feature parity with other database types, with null exclusion for unique indexes, DYNAMIC RESULT SETS for procedures, and data-driven enrichments now supported.Several behavioral improvements are also included. Multi-row selection now correctly updates the active record, read-only fields are now focusable, and grid column headers behave more consistently when filtering, sorting, or scrolling. The Scheduler now evaluates all records for conditional time cell formatting, enabling more precise coloring conditions based on all matching records for a resource.This is a short-term support (STS) release of the Thinkwise Platform. STS release support expires as soon as a new release is made available. For example, support for version 2026.1.12 ends when version 2026.1.13 is released. See our Lifecycle policy for information about supported versions.Contents Breaking Check CI/CD invocation of 'Verify' for 'Synchronize to IAM' Check CI/CD invocation of 'Execute all creation steps' task Moved trigger code group for DB2 models Changed default communication method in DevExpress Improved performance of SFTP file storage types Changed column width behavior for grids Verify conditional formatting in Scheduler resources New and changed Data - Exclude null values from unique index in DB2 User interface - Inline action bar Business logic - Support for DYNAMIC RESULT SETS in DB2 procedures Deployment - Synchronize to IAM using the API Deployment - Added 'Synchronize to IAM' functionality to 'Creation' screen Deployment - Improved layout of Deployment screens Enrichment - Support for data-driven enrichments for DB2 New session variable 'tsf_is_delegated_request' Preserving application settings during Indicium upgrades Endpoints return additional results for PATs Updated MessagePack NuGet package Support for 'Time cell min width' for lower versions Added extended property 'AlwaysShowBarcodeKeyboard' Additional improvements to 'Model insight' panel All records now evaluated for Scheduler time cell formatting Support for video files in the Preview screen component Updated behavior of active record in multi-row selection Improved focus behavior for read-only fields Improved grid column header behavior Improved behavior when a newly added record is hidden by filters Fixed Software Factory and Intelligent Application Manager Indicium Universal UI Data model changes Changes Software Factory Table changes Column changes Changes Intelligent Application Manager Table changes Column changes BreakingCheck CI/CD invocation of 'Verify' for 'Synchronize to IAM'Software FactoryAs a result of adding Synchronize to IAM using the API, a breaking change has been introduced. The task parameter Verify has been removed from the task Synchronize to IAM because it is no longer possible to disable it.Verification is now always performed when synchronizing to IAM. This change affects synchronization using CI/CD. Check your CI/CD pipelines to ensure they are compatible with this change.Synchronization using the Software Factory is not affected, as the parameter was already hidden. Check CI/CD invocation of 'Execute all creation steps' taskSoftware FactoryAs a result of adding 'Synchronize to IAM' functionality to the 'Creation' screen, several parameters and task inputs have been added, renamed, moved, or excluded from the task Execute all creation steps. If you use CI/CD to invoke this task, upgrading to this version introduces a breaking change.Previously, all parameters in the task Execute all creation steps were mandatory, even when they were not used during task execution. Which parameters are mandatory now depends on the creation steps you select.Leave out parameters that are not used during task execution, as the task now rejects them if you provide a value. If a conditionally required parameter is missing, the task returns a message telling you which parameter is missing. These checks have also been extended to the standalone tasks to keep behavior consistent.When calling the task through an API, the default procedure may already supply a value for empty parameters, so omitting a parameter does not always trigger a validation message. Parameters with a lookup, such as runtime_configuration_id and sync_target_iam_id, may also be rejected by CI/CD before the task's own validation is reached if you provide an invalid value. When calling directly from the database, neither of these applies and the task's own validation messages are always shown.Use the example below for a correct invocation:POST [indicium]/iam/sf/add_job_to_do_complete_creation{ "model_id": "MY_MODEL", "branch_id": "1.12", "execute_complete_creation": 0, "model_vrs_name": "1.13", "generate_definition": true, "generate_definition_error_handling": 1, "validate_definition": true, "validate_definition_error_handling": 3, "generate_source_code": true, "write_code_files": false, "write_prog_objects": false, "upgrade_method": 0, "execute_source_code": false, "execute_unit_tests": false, "execute_smoke_test": false, "run_sync": true, "sync_run_type": 0, "sync_target_iam_id": 1, "debug": 1}  Moved trigger code group for DB2 modelsSoftware Factory DB2Previously, INSTEAD OF triggers were part of the TRIGGERS code group for DB2 models. This code group has been moved to the new code group INSTEAD_OF_TRIGGERS, aligning it with other supported RDBMS types. This change helps prevent possible issues when using multiple RDBMS types in a model.When you upgrade, the upgrade script automatically adds the new code group to models that use DB2 and have INSTEAD OF triggers. The upgrade script also updates the code group of control procedures that have statically assigned templates.The upgrade script cannot automatically modify the code group from TRIGGERS to INSTEAD_OF_TRIGGERS for control procedures that use SQL assignments in combination with the TRIGGERS code group. Modify the code group of these control procedures manually and inspect the control procedure code to make any necessary adjustments. Changed default communication method in DevExpressIndiciumIn some environments, generating a report on Azure Web Apps (Windows) caused failures starting the reporting child process (prockees.exe). As a result, the default communication method used by the DevExpress reporting child process (prockees.exe) has been changed from Named Pipes to Sockets.No action is required for existing deployments that already use Socket.If desired, the previous behavior can be restored by configuring this in the appsettings.json file of Indicium:"Reporting": { "DevExpress": { "TransportMode": "NamedPipe" }} Improved performance of SFTP file storage typesIndiciumThe performance of SFTP file storage type connections has been improved. Connections are now pooled and remain open for up to 5 minutes, allowing subsequent requests to reuse the same connection.Up to 100 connections can be open simultaneously. Connections that remain idle for 5 minutes are closed automatically by Indicium.You can configure the behavior of SFTP connection pooling by adding the following configuration to the appsettings.json file of Indicium: "Storage":{ "Sftp": { "PoolSize": 100, "IdleTime": "00:05:00" } } Changed column width behavior for gridsUniversal UIYou can determine whether the user interface automatically sets the column width in grids. Previously, setting Auto column width to No in grids could cause columns to appear wider than expected. The behavior has been updated to now render columns narrower than before, aligning with the behavior of previous generations of Thinkwise user interfaces. This change only affects the grid screen component; other components are unaffected.This change introduces a breaking change for existing grids, as data that previously fit within the column width may now be truncated or displayed differently. Check your existing grids after upgrading and adjust column widths where necessary. Verify conditional formatting in Scheduler resourcesUniversal UIAs a result of updating the behavior of conditional time cell formatting in the Scheduler, all records related to a resource are now evaluated for conditional time cell formatting.Verify existing Schedulers that use conditional time cell formatting after upgrading to this version. If any unexpected behavior occurs, add extra conditions to the cell color to ensure that only the intended cells are colored. New and changedData - Exclude null values from unique index in DB2New Software Factory DB2When you create a unique index on a DB2 database, the index considers null as a unique value by default. This means only one record with a null value can exist in the table.You can now exclude null values from the unique index for DB2 by selecting the checkboxes Unique and Exclude null values (menu Data > Data model > tab Tables > tab Indexes). Enabling these settings creates the index using UNIQUE WHERE NOT NULL, and nulls are no longer enforced for uniqueness. These settings were already available for other RDBMS types. User interface - Inline action barCommunity idea New Software Factory Universal UI BetaAction bar buttons in a grid are typically placed in a toolbar above or beside the grid. You can now also place them directly within the active row using the Inline action bar, keeping actions close to the data the user is working with. It becomes visible when hovering over the active row, and follows the active row as users navigate through the grid.The inline action bar is only available for grid screen components. To enable it, go to menu User Interface > Screen types > tab Design. In the form of the grid screen component, select the checkbox Enable inline action bar.Once this setting is enabled, a new action bar is added to the tab Action bars. Here, you can configure how the buttons are arranged, such as which buttons appear near the start, near the end, or in the overflow menu of the inline action bar. This is similar to how a custom action bar is set up.This feature is launched in Beta. The actions now only show on hover on the selected row, which is not the most intuitive behavior. We are currently evaluating alternative solutions. The inline action bar allows users to quickly select actions for the active row Business logic - Support for DYNAMIC RESULT SETS in DB2 proceduresNew Software Factory DB2For a procedure header, DB2 requires a DYNAMIC RESULT SETS and a value equal to the maximum number of returned result sets before it can return a result. For example, to return rows from customer_table as a single query result in a procedure, the header must include DYNAMIC RESULT SETS 1.These options can now be configured in the Software Factory for DB2 procedures. To do this, go to Business logic > Subroutines (procedures) > Subroutine options and select DYNAMIC RESULT SETS. Then, in the field Value, enter the maximum number of returned result sets. Deployment - Synchronize to IAM using the APINew Software FactoryPreviously, synchronizing a model to IAM required the Software Factory to have direct access to the IAM database. This approach was not ideal for environments where the IAM and Software Factory are separated, such as in the Thinkwise Cloud. To address this, a new synchronization method has been added that uses the IAM API instead of direct database access.A main administrator or a user with the role Developer mode in IAM must act as a pool user to set the necessary pool user credentials for the API method as described below. The new and required role Model synchronization is automatically assigned to Developer mode users in IAM.In the menu Maintenance > IAM configurations you can select whether the Synchronization method is set to Database or API. For the API method, you must provide an API URL pointing to the target IAM environment (for example, https://server/indicium/iam/iam). Then, execute the task Set pool user credentials to set up the necessary credentials. All existing configurations are automatically set to Database when upgrading.You can only set one synchronization method per IAM configuration. To synchronize with the same IAM using both methods, you need to create two separate IAM configurations.As part of this update, the field Custom version name has been removed. The field As version is still available to specify a different version name. It is prefilled with the most recently used version name, or the branch name if no previous version name is available.A breaking change was introduced as part of this feature. See Check CI/CD invocation of 'Verify' for 'Synchronize to IAM' for more information. Select 'API' as the synchronization method Deployment - Added 'Synchronize to IAM' functionality to 'Creation' screenChange Software FactoryAfter executing the source code of your application using Creation, you also need to synchronize the changes to IAM. These two steps were previously done in separate screens in the Software Factory, Creation and Synchronize to IAM respectively. To improve the development workflow, we have added Synchronize to IAM functionality into the Creation screen, allowing you to synchronize directly to IAM or to storage from Creation.You can now include synchronization as part of the Creation when you execute the task Execute all creation steps (menu Deployment > Creation > tab Generate definition). Several controls for existing parameters in the task pop-up have been changed from Radio button to Combo to accommodate the new synchronization settings.To configure the synchronization settings, select Synchronize to IAM in the task pop-up. After selecting this option, the field Version name becomes mandatory because it is used as the name under which the branch is synchronized. Synchronization runs after all preceding creation steps have completed. When synchronizing, the process now also checks for duplicate synchronization runs, missing pool user credentials, and an invalid synchronization type.Known issue: When you start a synchronization without configured pool user credentials, an error message states that it has been cancelled for this reason. However, the run still starts, generates all synchronization objects, and only stops afterwards. It is then reported as successful, even though no actual synchronization with IAM has taken place. This will be solved in the next STS version.Furthermore, the tab Synchronization to IAM has been added to menu Deployment > Creation. This tab provides the same functionality and layout as the tab Synchronization in menu Deployment > Synchronize to IAM. Changing which modules or roles are synchronized, or modifying the post-synchronization code, still requires using the Synchronize to IAM menu.Finally, Creation presets (menu Maintenance) have been updated with the option to include or exclude synchronization in a creation preset. The screen has been redesigned to make better use of the available space, and logic has been added to ensure that certain fields become mandatory when related fields are populated. Existing presets are left unchanged, so the synchronization option is not automatically enabled for them. If you want to include the synchronization step in a preset, create a new preset or update an existing one, optionally renaming it to reflect the change.As part of this change, several parameters and task inputs have been added, renamed, moved, or excluded from the task Execute all creation steps. If you use CI/CD to invoke this task, upgrading to this version introduces a breaking change. For more information, see Check CI/CD invocation of 'Execute all creation steps' task. Synchronize to IAM is now included in 'Execute all creation steps' Deployment - Improved layout of Deployment screensChange Software FactoryThe following screens in menu Deployment have been updated for consistency and usability: Creation > tab Generate Definition, Creation > tab Generate Source Code, Synchronization to IAM, and Deployment Package.Action bar - The action bar in Creation > tab Generate Definition has been moved to tab Current and changed to a custom action bar with only relevant actions. Search - The Search component in tabs History and Steps now only searches relevant columns. Tab headers - Tab headers for tab Steps are now displayed consistently across all affected screens. The tab header for tab Progress in Deployment Package is also now shown. Step-related tasks - On-error tasks (Retry, Skip, Abort) and follow tasks (Follow active step, Unfollow active step) have been moved to tab Steps and their display type updated to Icon + text. Enrichment - Support for data-driven enrichments for DB2New Software Factory DB2Support has been added for data-driven enrichments in DB2 models. To create a data-driven enrichment, select the checkbox Data driven (menu Enrichment > Model enrichments > tab Maintenance > tab Enrichment > tab Form). After selecting the checkbox, select a RDBMS type from the dropdown. The selected RDBMS type determines on which environment the enrichment will be executed. New session variable 'tsf_is_delegated_request'New IndiciumThe session variable tsf_is_delegated_request has been added to Indicium, indicating whether a request is authenticated using access delegation roles.It has the following possible values:1 - The request is authenticated via a Client Application or a PAT that is scoped using access delegation roles. 0 - The request is authenticated via any other method, including a Client Application configured with Full access.The session variable has been introduced as part of the recently added access delegation roles for a client application. This feature allows you to scope user-delegated API access for a client application, which is particularly useful for setting up MCP integrations. Preserving application settings during Indicium upgradesNew IndiciumPreviously, upgrading Indicium could cause the appsettings.json file on the current installation to be reset, resulting in a loss of the application settings. To address this issue, Indicium now comes with an appsettings.sample.json file, instead of appsettings.json. The appsettings.json file is no longer overwritten when a new version of Indicium is installed, preserving any custom application settings. Endpoints return additional results for PATsChange IndiciumPreviously, the $metadata and openapi endpoints always returned 403 Forbidden for PATs, regardless of the token's actual permissions. These endpoints now return results for applications within the PAT's permissions. Applications outside the PAT's permissions still return 403 Forbidden as expected. Updated MessagePack NuGet packageChange IndiciumWe have updated the MessagePack NuGet package from version 3.1.4 to version 3.1.8. Indicium uses MessagePack internally for communication with components such as reporting and printing. A previous version of this package was reported to have security vulnerabilities. Although Indicium was not affected, we updated the package to include the latest security fixes. Support for 'Time cell min width' for lower versionsNew Universal UIPreviously, the setting Time cell min width was only available in Thinkwise Platform version 2026.1 and higher. Entering a value for this setting adds a minimum width for time cells in the Scheduler. This is useful in Schedulers with many columns, where the time cells can become very small and hard to read.The extended property SchedulerTimeCellMinWidth has been added to make this setting available in Thinkwise Platform version 2025.3 and lower. Added extended property 'AlwaysShowBarcodeKeyboard'Community idea New Universal UIBy default, Barcode scanner and Cortex barcode scanner controls do not show the virtual keyboard when focused. Users can select the keyboard icon to show the virtual keyboard and enter data manually. You can configure this using the Show action button setting.In some cases, suppressing the virtual keyboard is not desired or could cause compatibility issues on specific devices. You can now set the extended property AlwaysShowBarcodeKeyboard to True to always show the virtual keyboard. When enabled, the keyboard icon is hidden, as it is no longer needed. Additional improvements to 'Model insight' panelNew Universal UIThe Model Insight panel can now be resized. To reset it to its original size, double-click the panel's header. During a model refresh, the current size and position of the panel is maintained.Furthermore, the Message field has been added to the panel. Whenever a message or notification is shown, the message identifier is displayed in this field. All records now evaluated for Scheduler time cell formattingChange Universal UIYou can add conditional formatting to time cells in a Scheduler to highlight certain time cells based on conditions. This allows you to highlight time cells based on a column value, for example, to color time cells red when a resource is unavailable.Previously, this functionality was limited in the Universal UI. It only evaluated time cell formatting for the first matching record for a resource. Subsequent matching records for the same resource were ignored and time cell formatting would not be evaluated for those records.Now, all records related to a resource are evaluated for conditional time cell formatting. This allows for more complex conditions, such as using a work time table to show when a resource is available or unavailable.This also makes it possible to use the worktime table functionality from the Windows GUI Scheduler in the Universal UI. Unlike the Windows GUI, the Scheduler in Universal UI only uses one table or view. To achieve the same result, create a view that combines resources, activities, and worktimes. Use this view as the data source for the Scheduler and then add conditions for time cell formatting as needed.Conditional formatting for time cells is now displayed for all time steps and resources if there are no conditions defined, aligning it with the behavior of conditional layout in other components.Time cells can now be conditionally formatted based on all relevant records for a resourceThis change may introduce unexpected behavior in existing Schedulers that use conditional time cell formatting. See Verify conditional formatting in Scheduler resources for more information. Support for video files in the Preview screen componentChange Universal UIThe Preview screen component now supports video files in the Universal UI. Previously, a file column in the Preview screen component that contained an .mp4, .webm or .ogv file would display the message "No preview available". These formats are now shown in a video player inside the Preview screen component, in the same way images are already displayed. All other file types behave as before. Updated behavior of active record in multi-row selectionChange Universal UIPreviously, selecting multiple rows in a grid did not update the active row. This meant form and detail tabs still showed the data of the originally active record, rather than the record last added to the selection.The active row now always follows the last record added to a multi-row selection. If the active record is removed from the selection, the first remaining selected record becomes the new active record.This behavior also applies in grids with Auto-edit enabled, but editing is suspended if more than one row is selected. Additionally, Auto refresh is now disabled during multi-row selection to prevent records from dropping out of the selection when the dataset updates. Improved focus behavior for read-only fieldsChange Universal UIPreviously, read-only fields in the Form and Formlist screen components could not be focused. Read-only fields are now focusable, both outside of edit mode and when set to read-only while in edit mode. Focused read-only fields display a distinct focus style, separate from editable fields.This also changes focus behavior when switching to edit mode:The focused field is retained when switching into edit mode. When using F6 or Shift + F6 to switch to a form, or when entering edit mode with no focused field, focus moves to the first focusable field instead of the first editable field. When adding a new record, the first editable field is focused, as before.In addition, if you focus a read-only field and then open the filter pop-up (CTRL + R or the filter button in the action bar), the same field is now focused in the filter pop-up.Image, videolink, and signature fields remain non-focusable. Improved grid column header behaviorChange Universal UIFiltering, sorting, or horizontally scrolling in a grid could sometimes cause unwanted behavior. For example, column header labels could be truncated or wrapped, or column widths could change unexpectedly.To ensure more consistent behavior of column headers, the following changes have been made:Space is no longer reserved for the Filter icon in the column header if no filter is applied, or if filtering is not allowed. When scrolling horizontally, the column width is now cached. Columns no longer dynamically resize when scrolling back and forth. The column width no longer changes when sorting is applied or removed.Additionally, for columns with right-aligned content, the Filter icon has moved from the right side of the column header to the left side. Previously, the space reserved for the icon on the right prevented the header text from being fully aligned to the right. This change applies to all grids, including pivot grids. Improved behavior when a newly added record is hidden by filtersChange Universal UIPreviously, if a newly added record triggered a process flow but was hidden by active filters, the process flow would abort. The message "The saved data can not be displayed on this screen." would appear with a Show button to navigate to the record.The active document's filters are now automatically replaced with a filter matching the primary keys of the newly added record. This allows the process flow to continue without any action from the user. FixedSoftware Factory and Intelligent Application ManagerDB2 Previously, running smoke tests on a DB2 database that included BLOB or DBBLOB columns would result in an error. This was caused by a deficiency in the DB2 database driver, which did not support the declaration of variables for these column types. This has been fixed. Smoke tests on DB2 that declare variables are now compiled into a stored procedure named tsf_smoke_test and called during the test run. Note that this procedure persists in the database after the smoke test has finished. Fixed a performance issue when loading comments in the Code review screen (menu Quality > Code review > tab All comments). When a comment contained many HTML tags, generating the Title shown in the grid was slow. This has been fixed. During the validation process, errors could occur indicating non-unique primary keys in the dataset on refresh. This has been resolved. An incorrect error could occur when upgrading a SQL Server datatype. Error: Domain ".." already exists with a different datatype configuration. This would only occur on nchar/nvarchar datatypes. This has been resolved. Platform version 2026.2 introduced the capability to download a deployment package from within the Software Factory. To be able to download a deployment package, the folder location of the Deploy folder is required. Due to an oversight, the registration of the folder location only succeeded for file locations using backslashes (\). This has been fixed. Now, back and forward slashes are properly handled.IndiciumThe $apply query parameter is now included in the OpenAPI specification, enabling code generators to produce clients that support it. Previously, searching for a date or time value did not respect the user's configured date format. For example, a user with the format dd-mm-yyyy could not find results by searching for 14-08 or 2026. This also occurred when using the Starts with, Contains, or Ends with conditions in the Filter pop-up. This has been fixed.Universal UIFixed an issue for custom prefilters and cube views that included reference filters in Manage prefilters. If a user tried to save after creating or changing a custom prefilter or cube view, it would result in an error. Clicking the drag-handle column header in a grid would cause a runtime error. This has been fixed. Previously, if a user pressed Tab in a grid, the user would skip past editable grid columns. This would occur only if the grid column was set to Read-only in layout_mode "navigate", but Editable in layout_mode "update". This has been fixed. If a user adds a record in a grid that was not directly visible due to applied filters, a notification appears. Users can select Show to navigate to a new screen where the newly added record is visible. Previously, using keyboard shortcuts would affect the incorrect record and screen. For example, deleting the record using Ctrl + -, would delete the active record of the previous screen. The affected keyboard shortcuts now work as expected. Fixed an issue where if a user typed a decimal number starting with the decimal separator (for example ',25' instead of '0,25') would cause the cursor to jump to the beginning of the field after the first digit was entered. Fixed an issue where the IN field in an inline filter form would remain editable. It is now set to Read-only, as expected. Fixed an issue where invalid options entered into a domain control with domain control elements, or a report action combo would remain in the input field after deselecting the field. The field now reverts to the latest selected valid option immediately upon deselecting the field. Previously, if a user closed a document with a pivot grid in edit mode, it could cause the application to crash. This has been fixed. If a user tried to edit a record that was already deleted by another user, or directly from the database, it would cause the interface to crash. Users would have to restart the application to continue working. This has been fixed. Fixed an issue where activities in a Scheduler would not be shown for subjects with a column named 'id'. In some cases, clicking the outer cell of a grid or using the keyboard to navigate the grid would cause the domain and its control to not show or update. This has been fixed. Previously, a process flow could get stuck on the process action Go to first/previous/next/last row or Go to row if the record was not on the current grid page. This has been fixed. Fixed an issue in which the grid summary row would sometimes not be displayed. Fixed an issue where partially typing a value in a lookup field and deselecting it before the options finished loading would reset the field to its original value. Now, the first matching option is selected, sorted by Starts with then Contains. If no options match the entered value, the field still resets as expected. Fixed an issue where lookup values were not shown when the lookup's underlying column used a Datetime control with the Time zone set to Local. Previously, if a model update was available, selecting Update from the profile menu > About would not clear the model cache or reload the page. Additionally, if a user interface update was available, selecting Update now from the pop-up would sometimes not reload the page. This has been fixed. Previously, after exiting edit mode in a grid using a keyboard shortcut (for example, Escape or Ctrl + Enter), users could no longer use the arrow keys to navigate the grid. This has been fixed. Fixed an issue where detail references in the advanced Filter pop-up were displayed inconsistently. Fixed an issue where holding down the ↑ or ↓ arrow key in a paginated grid would cause the application to freeze. In addition, holding ↑ or ↓ while on a record other than the first or last no longer switches pages. Data model changesData model changes for the Software Factory and IAM meta-models are listed here. This overview can be used as a reference to fix dynamic control procedures, dynamic model code or custom validations after an upgrade.Changes Software FactoryTable changesSF - From table SF - To table - message_broker_subscription - message_broker_subscription_mapping_mqtt - message_broker_subscription_mqtt - sync_object generate_sync_scripts generate_sync_object generate_sync_scripts_step generate_sync_object_step sync_script -   Column changesSF - Table SF - From column SF - To column Mandatory Default value creation_preset - run_sync 1 1 creation_preset - sync_run_type 0 0 creation_preset validation_result_creation validate_definition_error_handling 0 0 deployment_run verify - - - enrichment - rdbms_type 0 - generate_sync_object generate_sync_scripts_status generate_sync_object_status 0 0 generate_sync_object_step generate_sync_scripts_step_id generate_sync_object_step_id 1 - generate_sync_object_step generate_sync_scripts_name generate_sync_object_name 1 - generate_sync_object_step generate_sync_scripts_step_status generate_sync_object_step_status 1 - iam_sync_job_step - sync_object_pk_hash 0 - iam_sync_job_step - iam_sync_job_step_type 1 - message_broker_message_mqtt - correlation_data 0 - query_conv model_id - - - query_conv branch_id - - - sync_run - sync_url 0 - sync_run verify - - - sync_run sync_as_branch_id vrs_name 0 - sync_run generate_sync_scripts_job_id generate_sync_object_job_id 0 - sync_target_iam - sync_method 1 - sync_target_iam - sync_url 0 - sync_target_iam server_name server_name 0 - sync_target_iam db_name db_name 0 - tab work_flow_tab_id - - - tab priority - - -   Changes Intelligent Application ManagerTable changesIAM - From table IAM - To table - post_sync_code - sf_message_broker_subscription - sf_message_broker_subscription_mapping_mqtt - sf_message_broker_subscription_mqtt   Column changesIAM - Table IAM - From column IAM - To column Mandatory Default value sf_message_broker_message_mqtt - correlation_data 0 -   

Related products:Software FactoryIntelligent Application ManagerUniversal UIIndicium Service Tier
Release notes Thinkwise Platform 2026.2.12

Release notes Thinkwise Platform 2026.2.12

Hi everyone,This release expands AI capabilities, broadens DB2 support, and brings meaningful improvements to modeling, deployment, and the user interface. Note that the SignalR message format has been updated, which requires Indicium and the Universal UI to be upgraded to the same version.The Software Factory now supports AI-powered conversion of model code between database types, speeding up the process of adding a new database type to an existing model. This builds on the multi-RDBMS support introduced in Thinkwise Platform 2026.2.DB2 support continues to expand, with temporal tables, smoke tests, and error handling for handlers, subroutines, and procedures now supported.For file management, you can now store file references relative to the storage root, making it easier to relocate files. Several other quality-of-life improvements have been made, including error details on database connection failure, improvements to the Model Insight panel and overlay, and updated translations and messages for pop-ups.In the Intelligent Application Manager, administrators can now configure a maintenance pool user and check database status, allowing for better database server management.Indicium now offers a MCP endpoint, allowing MCP clients to connect to your Thinkwise application and perform read, write, and task operations with lookup resolution and translated error messages. Note that this is a beta version, and some features are not yet supported.Several improvements have been made to the user interface, including inline editing in HTML columns in grids, offline-available images and files, and subtitles for open document tabs. Help pop-ups are now supported in the Universal UI, allowing you to provide additional information to usersThis is a short-term support (STS) release of the Thinkwise Platform. STS release support expires as soon as a new release is made available. For example, support for version 2026.1.12 ends when version 2026.1.13 is released. See our Lifecycle policy for information about supported versions.Contents Before you upgrade Demo and download Updated Next.js from 16.2.6 to 16.2.11 Breaking Updated SignalR progress message format New and changed Models - Finalized branches set to read-only Models - AI-powered conversion of model code between database types Data - Support for temporal tables in DB2 Data - Domain element database value now supports 100 characters User interface - Add subtitles to open documents User interface - Support for help pop-ups in the Universal UI Business logic - Error handling for DB2 handlers, subroutines, and procedures Quality - Smoke tests now supported for DB2 Deployment - Error details on database connection failure Enrichment - Re-generate model updates for enrichment runs Integration & AI - Use relative paths for file references Processes - Software Factory now adheres to the extended property 'AllowProcessFlowsInLookupDialogs' Settings - Improved database server management MCP support added in Indicium Increased timeout for i-net Clear Reports 'ClearLocalCacheOnStartup' removed from Indicium Migration warning for classic data security settings Offline available images and files Support for input parameter 'Filter record when not found' Support for IN filter operator in the Filter form Improved 'Model insight' panel and overlay Updated translations and messages for pop-ups Inline editing for HTML columns in grids Filter pop-up available in cube panel fields Consistent column widths across pivot grid series Spacing of paging controls matches application theme Background color fills entire Scheduler resource cell Fixed Software Factory and Intelligent Application Manager Indicium Universal UI Data model changes Changes Software Factory Table changes Column changes Changes Intelligent Application Manager Table changes Column changes Before you upgradeFeatures for the Software Factory and the Intelligent Application Manager are only compatible with this STS version of the Thinkwise Platform. Indicium and Universal UI features are backwards compatible with previous Thinkwise Platform versions, unless otherwise noted.Demo and downloadTry a demo of the Thinkwise Platform here. Download the latest versions of our components here. Updated Next.js from 16.2.6 to 16.2.11change Universal UIWe have updated the Next.js framework from version 16.2.6 to 16.2.11 to fix several security vulnerabilities. The vulnerabilities are present in the server-side functionality of Next.js, which we do not use. Therefore, these vulnerabilities did not affect the security of the Thinkwise Platform. BreakingUpdated SignalR progress message formatIndicium Universal UIThe format of SignalR progress messages sent by Indicium has been updated to follow the new SignalR message structure. The Universal UI has been updated to handle this new format. This change only affects the underlying communication between Indicium and Universal UI and does not produce any visible changes in the interface.When upgrading the Universal UI to this version, Indicium must also be upgraded. If the versions do not match, tasks and mass updates will not work as expected.New and changedModels - Finalized branches set to read-onlychange Community idea Software FactoryYou can choose from several merge strategies when merging a branch in the Software Factory. If you select Finalize branch, cannot be merged again, the branch would not be able to be merged again, but it could still be modified by users in the Software Factory. The finalized branch is now set to read-only for all users in the Software Factory. This prevents any further development or accidental changes on the branch. Models - AI-powered conversion of model code between database typesnew Software FactoryYou can now convert model code and queries from one database type to another using generative AI. This speeds up adding a new database type to an existing model, building on the multi RDBMS support released in Thinkwise Platform 2026.2. These tasks become available when you have added two or more database types to your model.You must set up an AI provider in the Intelligent Application Manager to use generative AI for code conversion. For more information, see Generative AI for an application.Conversion is currently supported for SQL Server to DB2 for i. Conversions between other database types are experimental and may not produce the expected results. Always verify the converted code before using it in production or continuing development, as AI can make mistakes even for supported database type combinations.You can convert code in a single template or for all code in a model at once.To convert a single template, execute the task Convert template code (menu Business Logic > Functionality > Templates). Provide a source and target database type and a name for the new template. After conversion, assign the new template to program objects manually. For more information, see Assign the template.Convert template code task pop-upTo convert all code in a model at once, execute the task Convert code to RDBMS dialect (menu Models > Model overview > Branches > tab General settings > tab RDBMS types). In the task pop-up, select a Source RDBMS type and Target RDBMS type. Then, choose which logic concepts to convert by selecting the relevant checkboxes.The conversion runs as a mass conversion enrichment in the background. You can review the generated code while the task is running. Verify the generated code before using it in production or continuing development, as the code is AI-generated and may contain mistakes.The task runs only once per target database type to avoid conflicts from repeated conversions. To run it again for the same target, remove the tags it added to converted control procedures (for example, AUTO_CONVERTED_TO_ISERIES for DB2 or AUTO_CONVERTED_TO_SQLSERVER for SQL Server). For more control over individual results, use the task Convert template code instead. Convert code to RDBMS dialect task pop-upFor each logic concept, the conversion produces the following output:Prefilters get new query entries for the target database type. Control procedures get a new template for the target type. The template is assigned to the corresponding program objects where possible, and the control procedure is moved to review.Lastly, the enrichment Mass convert the code from a source RDBMS type to a target RDBMS type is now also available in the menu Enrichments > Model enrichments. Data - Support for temporal tables in DB2new Software Factory DB2You can now enable system versioning for DB2 tables, extending a feature previously available only for SQL Server. System versioning automatically tracks the history of data changes, making it easier to audit changes, ensure compliance, and recover previous data.DB2 does not have a Retention period.To use temporal tables in DB2, the pool user executing the upgrade script must have authorization for the QIBM_DB_GENCOL_OVERRIDE function in DB2. For more information, see Overriding system generation column values in the IBM documentation. To set up system versioning for a DB2 table, select the checkbox System versioning in menu Data > Data model > tab Tables > tab Form. Data - Domain element database value now supports 100 characterschange Software FactoryPreviously, domain element database values were limited to 25 characters. You can now enter up to 100 characters, the same length as the element ID. This allows for the database value to match the element ID exactly, if desired. User interface - Add subtitles to open documentsnew Community idea Software Factory Universal UIPreviously, open document tabs in the sidebar menu only displayed the document title, making it difficult to distinguish between multiple open instances of the same document.You can now add subtitles for open document tabs to show the active record context. To do this, enable Show subtitles for the menu in the Software Factory (menu User interface > Menus > tab Form > group Settings).Enabling subtitles shows the value of the active record for that document under the document title. For example, if three 'Customers' tabs are open, the subtitle shows the name of the selected customer for each tab.The subtitle is determined in the following order of precedence:The value of the lookup display column configured for that subject. The value of the last primary key column of that subject. If you are adding a new row, the subtitle shows 'new row'.If none of this data is available, no subtitle is shown. If a subtitle is too long to fit, it is truncated with an ellipsis (...).Open document tabs with subtitles showing the active record contextUser interface - Support for help pop-ups in the Universal UInew Software Factory Universal UIThe Help pop-up is now supported in the Universal UI, allowing you to provide additional information or guidance for users. Users can open the Help pop-up by selecting it from the profile menu or by pressing Alt + F1. The Help pop-up displays the help text for the open document. If no document is open, the general help pages are shown instead.To add help text, you have to add at least one page of text in the Software Factory (menu User interface > Help). For more information, see Help.Help pop-up in the Universal UI showing help text for the open documentBusiness logic - Error handling for DB2 handlers, subroutines, and procedureschange Software Factory DB2Error handling is now available for DB2 handlers, subroutines, and procedures. As a result, tsf_send_message is now included consistently. Quality - Smoke tests now supported for DB2new Software Factory DB2Smoke tests (menu Quality > Smoke tests) are now supported for DB2 models, in addition to SQL Server, Oracle, and PostgreSQL. Deployment - Error details on database connection failurenew Software FactoryAn error message is now displayed in a pop-up if the Software Factory fails to connect to the database during the creation step Execute source code (menu Deployment > Creation > tab Execute source code). Previously, the log appeared empty with no indication of what went wrong. The same issue occurred when generating a SQL control procedure, and no program objects were successfully generated. Enrichment - Re-generate model updates for enrichment runschange Software FactoryPreviously, once you generated model updates for an enrichment run, you could not run the enrichment again. To make any changes, you had to cancel the enrichment run and start over.You can now regenerate model updates as many times as needed and edit the parameters at any point. Once you update the parameters and execute the task Execute model updates, a pop-up is displayed with the following options:Cancel - Stop the execution and continue editing the parameters, or cancel the enrichment run entirely. Regenerate model updates - Discard the existing model updates and generate new ones based on the updated parameters. Continue - Execute the existing model updates as-is. To also get model updates based on the updated parameters, run Generate model updates manually afterward.The task Cancel enrichment run is now also available on the tab Run enrichment. After canceling, you are returned to the tab Select enrichment automatically.Pop-up with options when executing model updates for an enrichment runIntegration & AI - Use relative paths for file referencesnew Software Factory Intelligent Application ManagerYou can now store file references relative to the root of a file storage location, instead of storing the full path. Changing where files are stored is now easier, as you no longer need to update all existing file references when the storage root changes.You can use relative paths for all File storage types, except for Database.To enable relative paths, select the checkbox Use storage-relative paths:In the Software Factory, this setting is available in: menu Integration and AI > File storage locations > tab Form menu Maintenance > Runtime configurations > tab File storage locations In the Intelligent Application Manager (IAM), this setting is available in: menu Authorization > Applications > tab General settings > tab File storage locations New file storage locations use relative paths by default. Existing file storage locations continue to use absolute paths by default, so this does not affect existing file references.Enabling Use storage-relative paths on an existing file storage location does not convert existing file references. To migrate to relative paths, you must manually update the file references stored in your database. This setting is also applied to process actions that work with file references (menu Processes > Process flows > tab Process actions > tab Input). Processes - Software Factory now adheres to the extended property 'AllowProcessFlowsInLookupDialogs'change Software FactoryThe extended property AllowProcessFlowsInLookupDialogs controls whether process flows can be started from lookup pop-ups.The Software Factory now adheres to this extended property. This allows process flows in the Software Factory to be started from lookup pop-ups, such as downloading an icon from the Icon screen. Settings - Improved database server managementnew Intelligent Application Manager main administrator application administratorYou can now configure a maintenance pool user per database server. This is useful for administrative tasks, such as database provisioning, installation, and upgrades.Execute the task Set maintenance user credentials (menu Settings > Database servers) and enter the credentials for the maintenance pool user. If a maintenance user is set, the checkbox Custom maintenance user set is enabled.As part of this update, the menu item Servers has been moved from Advanced menu > Master data to Default menu > Settings. The screen has been renamed to Database servers to better reflect its purpose.Furthermore, main administrators and application administrators can now retrieve the status of the database by executing the task Check database status (menu Settings > Database servers > tab List/Form). A column has been added in the tab List to show the database status for each server.The following statuses are available:Ok - The database is reachable and contains a valid model. Ready to provision - The database server is reachable, but the database/schema does not yet exist. Ready to install - The database is present and accessible, but assumed empty; there is no model information stored in the database. Unreachable - The database or database server is not accessible for use by the Thinkwise Platform. Unverified - No check has been done yet.The model, named version, and creation date and time are only shown for databases that were installed or upgraded using Thinkwise Platform version 2023.1 or later. Renewed 'Database servers' screen with database status columnMCP support added in Indiciumnew IndiciumYou can now connect MCP clients to your Thinkwise application using the /mcp endpoint in Indicium. MCP clients can authenticate using OAuth (via Client Applications with delegated roles) or PAT authentication, depending on what the client supports.The following operations are supported:Reading data, including filtering, sorting, grouping, and aggregating. Inserting and updating data, including resolving lookups by their display value, applying default and layout logic, and returning translated error messages so the client can correct mistakes. Deleting data. Executing tasks — both unbound tasks and tasks bound to a specific record — with the same lookup resolution, layout logic, and error message support as data operations.The following is not yet supported:Uploading and downloading files. Reports. Process flows that include non-system actions. Process flows that start with a task, add row, update row, or delete row action, and then continue with only system actions work fine. Import and other bulk operations.We are releasing this as a beta version and look forward to hearing about your experiences as we continue to improve performance, reduce token usage, and add more capabilities.You can read more about MCP in our blog posts here:  Increased timeout for i-net Clear Reportschange IndiciumPreviously, report generation using i-net Clear Reports would time out after 100 seconds. The timeout has been increased to 5 minutes, allowing reports that take longer to generate to complete successfully. 'ClearLocalCacheOnStartup' removed from Indiciumchange IndiciumThe setting ClearLocalCacheOnStartup has been removed from the Indicium configuration.Previously, this setting controlled whether Indicium cleared its local file cache on startup. It was introduced to prevent multiple Indicium instances from deleting files that other instances still needed, which could cause issues in scaled deployments. An earlier release resolved those issues, making the setting unnecessary.Indicium now always clears the local file cache on startup. If your configuration includes ClearLocalCacheOnStartup in the FileCache section, you can remove it as Indicium no longer recognizes this setting. Migration warning for classic data security settingsnew IndiciumYou now receive a warning if your application is still using the deprecated DataProtectionSettings configuration in Indicium. The warning includes a link to the documentation to help you migrate to the new DataSecuritySettings configuration introduced in Thinkwise Platform 2026.1.12. DataProtectionSettings configuration will be removed in a future release. Offline available images and filesnew Universal UIUsers can now view images and files in offline-available subjects.When an offline subject loads, Universal UI saves the images and files to the browser's cache storage on the device. Images in grids, forms, card lists, and the preview panel are served from that cache. This allows them to remain visible even when the internet connection drops.This applies automatically to any subject marked as offline-available in the Software Factory. No additional configuration is needed.Ensure that users check their browser settings to prevent the cache from being cleared automatically when the browser is closed. Clearing the cache removes offline-saved images and files, making them unavailable without an internet connection. Support for input parameter 'Filter record when not found'new Universal UIThe input parameter Filter record when not found for the process action Go to row is now supported in the Universal UI.By default, if active filters prevent the process action Go to row from locating a row, the process flow is aborted. If the input parameter Filter record when not found is assigned, the Universal UI first attempts to find the row through searching. If the row cannot be found that way, it removes the active filter and filters for the row instead. This allows the process flow to continue as long as the row exists in the dataset. Support for IN filter operator in the Filter formnew Universal UIYou can now use the IN filter operator in the Filter form to filter a column by selecting multiple exact values at once. Previously, the filter field was disabled and read-only whenever the IN filter operator was active on a column.When the IN filter operator is active, a list appears in the Filter form, allowing users to select as many values as needed. This works together with other filtering methods, such as the column header filter and the Filter pop-up.You can configure the default Filter condition per subject in the Software Factory. For more information, see Add columns to Filter. Improved 'Model insight' panel and overlaychange Universal UIThe Model Insight panel and the Screen type overlay have been improved, allowing for better navigation and understanding of the screen hierarchy.The Model insight panel now has collapsible sections, including a new Path section. The Path section shows the screen hierarchy for the selected subject, including entity IDs and optional configuration IDs. The panel's layout and scrolling behavior have also been improved.Additionally, when the Screen type overlay is enabled, hovering over a screen component's label now displays a border around the corresponding component. If multiple overlays overlap, they no longer cover each other, making all information readable at the same time.Model insight panel with collapsible sections and improved screen type overlayUpdated translations and messages for pop-upschange Community idea Universal UIPop-up button labels and messages for deleting records or cancelling changes in the Universal UI have been updated. Previously, buttons were labeled 'Yes' and 'No' and contained a generic message.To improve clarity, the following changes have been made: When deleting a record, the pop-up now shows the name of the record that is about to be deleted. The buttons are now labeled 'Delete' and 'Cancel'.  Pop-up when deleting a single record  When deleting multiple records, the pop-up now shows the number of records that are about to be deleted. The buttons are now labeled 'Delete' and 'Cancel'.   Pop-up when deleting multiple records  When cancelling changes, the pop-up now mentions that unsaved changes will be lost. The buttons are now labeled 'Keep editing' and 'Discard changes'.    Pop-up when cancelling changesInline editing for HTML columns in gridsnew Universal UIYou can now edit HTML columns directly within grid cells, without opening a separate pop-up. This makes editing faster and more consistent with other column types.When a cell enters edit mode, the HTML toolbar is hidden. A pop-up button is always shown to open the full editor with a toolbar, regardless of the Show action button setting configured for that column. When the cell is not being edited, it continues to display as read-only. Filter pop-up available in cube panel fieldsnew Universal UIYou can directly apply filters to fields using the filter pop-up in the cube panel. Select the filter icon on a field in Categories, Series, or Values to open the standard filter pop-up for that field. If a filter is already active, the filter icon is permanently visible.The cube panel must be made available, and its screen component added to a screen type for it to be visible in an application.Additionally, the filter icon only appears for fields where filtering is permitted:Visible for filter should not be set to Never (menu User interface > Subjects > tab Default/Variant > tab data > tab Filter) Filter permissions should be enabled for the subject (menu User interface > Subjects > tab Default/Variant > tab Settings > group Permissions).Select the filter icon from a field in the cube panel to open the filter pop-upConsistent column widths across pivot grid serieschange Universal UIPreviously, resizing a value column in the pivot grid only changed that single column. Now, when you drag the edge of a value column header, all columns representing the same aggregation field across all series resize to match. For example, resizing the Revenue column in one region series also updates Revenue in every other series. Spacing of paging controls matches application themechange Universal UIPaging controls now adapt to the Comfortable or Compact mode set in the application theme. In Comfortable mode, the controls are larger and more spaced out. In Compact mode, they are smaller and more tightly spaced.Paging controls in Comfortable modePaging controls in Compact modeBackground color fills entire Scheduler resource cellchange Universal UIPreviously, when you added a background color to a Scheduler resource using conditional layout, it would only color the text area of the cell. Now, the background color fills the entire cell. FixedSoftware Factory and Intelligent Application ManagerIn the detail tab Validation messages (menu Quality > Validations), the correct data was not shown when the prefilter Hide messages was enabled. This has been fixed. The validation Role is not assigned to any objects checks whether roles in the model have rights (menu Quality > Validation). If a role does not have any rights, the validation informs you about it. This validation was missing checks for several role tables. Because of this, roles that actually contained rights were suggested for cleanup. This has been fixed. When configuring a tree component, you can link one or more parent columns to a column. The validation Column cannot have itself as validation column checked whether any of the specified parent columns referenced itself. This check was incorrect because the validation should only fail when all specified parent columns reference themselves. We have updated the validation logic accordingly and renamed the validation to All tree parent columns reference themselves. When the prefilter column subject shrinks, it displays a card list. Previously, this card list did not show any data. This has been fixed. It now shows Column, Filter condition, Filter value, and Filter value until. Due to the use of a new table variant, the process flow that selects the active model when you open the Model overview in the Software Factory did not trigger (menu Models > Model overview). The process action now uses the correct variant and selects the active model. In the Difference analysis result screen (menu Models > Difference analysis), no detail references to the source and target data were shown. This made it impossible to determine the differences. This has been fixed. Writing code files to a storage location may have a different destination in case a Model version name is set in the task Execute all creation steps. However, the cleaning step before writing code files to the storage location did not properly use this name, causing it to clean the folder with the branch name instead of the folder with the model version name. This has been fixed. The Software Factory offers a set of validations to ensure the _query tables have a value when needed. However, these validations would only return a result for multi-RDBMS models. This has been changed so they also validate single-RDBMS type models. Three query-references were missing ON DELETE CASCADE, causing a deletion of the parent record to be blocked by the existence of a query record. Whilst normally we do want to prevent such deletion, in these cases, the deletion is permitted. Now, you can remove Check constraints, Data sets, and Mock data columns and have the query data removed automatically. Granting a user log access would give the user more rights than they were supposed to have, such as access to the IAM application. This has been fixed. Due to an inefficient Where clause, the Cube view filter node interface view could inspect a larger dataset of Cube field rights for Custom cube views than needed. This has been optimized.IndiciumPreviously, the process action Generate report did not work correctly with report parameters that had Property as an input parameter. For example, when Property was set to Report file (non-file storage), it was ignored and you could not override the path. This has been fixed. In rare cases, the process flow connector HTTP connector could enter a corrupted state. When this happened, the following was logged to the Indicium error log: "Operations that change non-concurrent collections must have exclusive access". The result of the HTTP connector could then not be read, and the connector returned status code -1. To return to a valid state, you had to restart Indicium. This has been fixed. When a user double-clicked Submit on the two-factor authentication (2FA) login screen or the authenticator reset screen, an error could occur. This has been fixed. DB2 For DB2 databases, the Ends with filter condition could fail on fixed-length character columns, such as CHAR. This occurred because fixed-length types can include trailing padding characters that interfered with the condition. This has been fixed. Indicium now applies RTRIM when needed, so trailing padding does not affect the results. Prefilter conditions using the Not between operator mistakenly excluded NULL values from the results. For example, for my_column not between 1 and 3, NULL values should be included in the results because NULL is not between 1 and 3. This has been fixed.Universal UIIn a default editable grid, switching to a different record under certain circumstances did not make the selected record editable. Under these same circumstances, the Ctrl + A shortcut also did not select all records in the grid. Both issues are now fixed. When the grid summary row triggered an error, the error was returned in an unexpected format, which caused the client to stop working. This has been fixed. When you had scrolled down in a form and then selected Edit, the form scrolled back up. This has been fixed. When Edit in grid (but not Auto-edit) and Auto save were enabled and the screen type also contained a form, the grid did not respond to auto save when the Universal UI had not yet loaded the form. As a result, after a user changed a value directly in the grid, they could not navigate to another row without first selecting Save. This has been fixed. From Software Factory version 2026.2.12, an auto_save flag is available directly on the tab definition, so a form is no longer required to determine the auto-save context for a screen. Users can now change a value in the grid and navigate to another row without selecting Save first. In a subject with a Date column as its primary key, the active row selection was lost after a user saved a record, which caused an error. This only affected date columns. Numeric and other primary key types were not affected. This has been fixed. After saving, the application now keeps the saved record selected, the same as for subjects with other primary key types, and no error is shown. When a user typed quickly across multiple form fields on a slow or throttled network connection (for example, Slow 3G), typed input could be lost without any message. In one situation, a field briefly reverted to the old value while the change was still being saved. In another, characters typed while a change was still being saved were discarded. This has been fixed. A field no longer reverts to the old value while a change is being saved, and characters typed during that time are now kept. This applies to editable form fields that have optimistic updating enabled (text, numeric, and select fields). On certain pop-ups, pressing the Esc key while a field had its drop-down list open had unexpected side effects. In a lookup pop-up or modal document, it cancelled the editing session. In a task or report, it closed the pop-up immediately, and users lost their changes. This has been fixed. The Esc key now only closes the drop-down list and does nothing else. When you changed the active record in a subject, a default editable detail of that subject would get one of its fields focused. This could disrupt the keyboard navigation in the focused subject. This has been fixed. Hyperlinks in a lookup pop-up would sometimes disappear after you saved an edited record. This has been fixed. When the focus was on a multi-select checkbox and a user pressed a key, the application stopped working. This has been fixed. The SQL editor and Code editor controls did not scroll into view when cursor_to_col_id focused such a field. This has been fixed. Previously, in the Code editor and Code diff editor controls, comments and string literals were hard to read in dark mode because of the colors used. This has been improved. Selecting a value in a Combo control could mismatch the selected option when the database value of the option was a floating-point number that ended with zeros. This could occur, for example, in the Software Factory when you changed the Branch increment field (menu Maintenance > Configuration). This has been fixed. A process flow could stop responding when a Go to row action used the Context logic concept to hide the active detail tab and show another tab. This has been fixed. During record navigation in a process flow, the output parameters were not filled with the values of the new active record. This occurred only with the process flow actions Go to row, Go to first row, and Go to last row. As a result, the rest of the process flow could make incorrect assumptions about which record the user was on. This has been fixed. The Universal UI now first switches to the correct record and then informs the process flow about the change. If a process flow contained the action Start table task/report that triggered a task or report variant, the non-variant was executed and shown to the user instead. This has been fixed. The user interface now detects whether a variant is attached to the target subject and starts the correct instance. No extra task is shown on the subject after execution. When you moved between open documents, a pivot table in a cube view reloaded very slowly, line by line, on return. This has been fixed. Previously, when setting up conditional formatting for Scheduler time cells (menu User Interface > Schedulers > tab Default > tab Scheduler views > tab Cell colors) based on datetime values, you could not use the condition Equal to in combination with the Type of value set to Column. This has been fixed.For a hierarchical tree menu without extra group columns, a conditional layout applied to the tree Display column did not show. This has been fixed.In a hierarchical tree, double-clicking a row did not trigger a task that had Double click on record set (menu User Interface > Subjects > tab Default > tab Links > tab Tasks). This has been fixed. Model Insight would already show task and report information when you hovered over a task button, for example. However, the information was cleared too often if you moved the mouse from the target to the Model Insight panel, for example, when you tried to copy the task ID. This could also happen when you hovered over a tooltip, which caused flickering. These issues had one underlying cause, which has been fixed. In rare cases, a user could briefly see the wrong data. This happened if the user had offline task data that was not yet synchronized, waited until their login expired, and then logged in as a different user. This has been fixed. Now, when offline data still needs to be synchronized, and a user logs in with a different account, the Universal GUI shows a pop-up. The only option is to log off, with the instruction to log back in with the correct account. Fixed an issue where switching between menu types or applications would reopen start objects. Data model changesData model changes for the Software Factory and IAM meta-models are listed here. This overview can be used as a reference to fix dynamic control procedures, dynamic model code, or custom validations after an upgrade. Changes Software FactoryTable changesNo changes in this release.Column changesSF - Table SF - From column SF - To column Mandatory Default value enrichment_run - parmtrs_changed 1 0 menu - show_sub_titles 1 1 message_broker_mqtt will_payload_format will_payload_format 0 0 screen_component - component_action_bar_enabled 1 0  Changes Intelligent Application ManagerTable changesNo changes in this release. Column changesIAM - Table IAM - From column IAM - To column Mandatory Default value appl_db - maintenance_gui_appl_id 0 - appl_db - appl_db_status 1 4 appl_db - appl_db_model_id 0 - appl_db - appl_db_branch_id 0 - appl_db - branch_date_time 0 - appl_db - last_checked 0 - appl_db - extra_info 0 - menu - show_sub_titles 1 1 screen_type - max_width_value 0 - screen_type - max_height_value 0 - screen_type max_width_value - - - screen_type max_height_value - - - server - encrypted_user_name 0 - server - encrypted_password 0 -  

Related products:Software FactoryIntelligent Application ManagerUniversal UIIndicium Service Tier
Release notes Thinkwise Platform 2026.2.11

Release notes Thinkwise Platform 2026.2.11

Hi everyone, This release includes important security fixes and meaningful improvements across the platform.A cross-site scripting (XSS) vulnerability in the HTML editor has been resolved, and Indicium now exposes a security.txt file to support responsible disclosure. Note that SQL Server 2019 is no longer supported as of this release.The deployment process has been updated to streamline source code generation and execution. The Software Factory now writes separate Install and Upgrade folders, and code files are only shown once the deployment type is known.On the authorization side, administrators can now manage error log access for individual users without granting full administrator rights. Furthermore, administrators can delegate API access to client applications using roles, allowing for more granular control over their access.Several UI improvements make modeling more flexible and intuitive. The IN filter operator is now supported as default filter condition for alphanumeric and numeric fields. Tree views now support pagination, Clear cube view has been added to the action bar, and Model insight has been updated with more debug information and improved focus behavior. Startup time has been reduced through on-demand loading of libraries and components, and you can now navigate between screen components using keyboard shortcuts. This is a short-term support (STS) release of the Thinkwise Platform. STS release support expires as soon as a new release is made available. For example, support for version 2026.1.12 ends when version 2026.1.13 is released. See our Lifecycle policy for information about supported versions. ContentsBefore you upgrade Demo and download Breaking Cross-site scripting (XSS) security vulnerability End of Support for SQL Server 2019 Regenerate definitions and source code New and changed User Interface - Show or hide header and footer in modal screens User Interface - Updated default action order for action bars User Interface - Removed 'Values' tab from cube view sort settings User Interface - Set 'IN' as default filter operator Business logic - Updated column order in 'Functionality' Deployment - Updated source code generation and execution Authorization - Manage API access for client applications Authorization - Manage error log access for users Added 'security.txt' file for Indicium Updated libraries for office file handling Added pagination for tree views Added 'Clear cube view' to action bar Improved 'Model insight' panel and debug values Configure debounce time for lookups Improved datetime filtering Improved sort order in lookup and domain dropdowns Performance optimization for Universal UI Added keyboard shortcut for component navigation Fixed Software Factory and Intelligent Application Manager Indicium Universal UI Data model changes Changes Software Factory Table changes Column changes Changes Intelligent Application Manager Table changes Column changes  Before you upgradeFeatures for the Software Factory and the Intelligent Application Manager are only compatible with this STS version of the Thinkwise Platform. Indicium and Universal UI features are backwards compatible with previous Thinkwise Platform versions, unless otherwise noted.Demo and downloadTry a demo of the Thinkwise Platform here. Download the latest versions of our components here. BreakingCross-site scripting (XSS) security vulnerabilityCross-site scripting (XSS) security vulnerabilities in the HTML editor have been resolved. When an HTML control field was in edit mode and an attacker could influence the displayed data, a JavaScript payload could execute using the user's credentials.While Indicium's Content Security Policy (CSP) helped mitigate the risk, it is strongly recommended that you configure security headers for additional protection. End of Support for SQL Server 2019Support for SQL Server 2019 has ended. To continue using the Thinkwise Platform, upgrade to SQL Server 2022 or higher.For more information, see End of SQL Server 2019 support. Regenerate definitions and source codeAs a result of changes made to source code generation and execution, it is important to regenerate definitions and source code after upgrading to this version of the Thinkwise Platform. This ensures the deployment continues to work as expected. New and changedUser Interface - Show or hide header and footer in modal screensnew Community idea Software FactoryYou can now control whether to show the header or footer in a modal screen. This is useful if you want to use modal screens for custom dialogs, such as a wizard, where the header and footer are not needed.In menu User interface > Screen types, select a screen type and go to tab Form > group Modal size. Select Show header or Show footer to show the header or footer, or clear the checkboxes to hide them.Check the new blog for inspiration on using Wizards with both Tasks and Modal documents in your Applications!User Interface - Updated default action order for action barschange Software FactoryThe default order of the action buttons in an Action bar has been updated to show task, report, and cube view buttons first, followed by the CRUD buttons.Previously, the CRUD buttons were displayed first, then the task, report, and cube view buttons. This would result in the CRUD buttons being displayed in different positions in each screen.This change does not affect existing models, it only applies to new models or when the action bar is reset. The default order can still be modified in the menu Model overview > Branches > tab General settings > tab Default action bar. User Interface - Removed 'Values' tab from cube view sort settingschange Software FactoryThe sort settings for cube views (menu User Interface > Cubes > tab Cube views > tab Sort) have been updated.Cube views and charts now use the setting Show top x. Use this setting to limit the number of category rows displayed in a cube view or chart.Grand totals and sub-totals are always calculated using the full dataset, regardless of the Show top x setting.Additionally, you can now only select Absolute for the setting Type of show top x, which determines how the top rows are displayed. The Percentage option has been deprecated.Finally, the following changes have been made to the tab Cube views:The Values tab has been removed. The sort settings Show top x and Type of show top x have been moved to the tab Categories / Rows. User Interface - Set 'IN' as default filter operatornew Software FactoryYou can now set the IN filter operator as the default filter condition for Alphanumeric and Numeric fields in the Filter pop-up. Users can use this operator to filter data on multiple values at once. For example, users can now filter an order overview to show only orders with the status Pending, Processing, or Shipped.Default filter operators for all subjects can be set in the menu User interface > Subjects > tab Default settings > group Filter. Filter operators for columns of the subject can be set in the menu User interface > Subjects > tab Data > tab Filter. Business logic - Updated column order in 'Functionality'change Software FactoryThe order of the columns in menu Business logic > Functionality has been updated to improve usability. The column Code group is now displayed in front of the Control procedure column. This makes it easier to see which code group a control procedure belongs to. Deployment - Updated source code generation and executionchange Software FactoryWe have updated source code generation and execution to improve the deployment process.Source code generationPreviously, all code files were written to storage when generating source code, regardless of whether the deployment would be an install or an upgrade. You then had to decide afterwards which files to use. The Software Factory now writes separate Install and Upgrade folders. Each folder contains only the code files relevant to that deployment type.As part of this change, the file specifications of all code files in the Thinkwise base models have been updated. The path has been simplified from Source_code\Groups\[code_file_name].sql to [code_file_name].sql. The full path, including the appropriate Install or Upgrade folder, is now constructed dynamically during generation.In addition, code files with the Show at deployment setting disabled are no longer written to storage.Execute source codePreviously, all code files were shown immediately after generating source code. The deployment type was determined only after connecting to the database. Non-relevant files were then deselected and locked, and the create code file was always shown, even when it was not applicable.Now, code files are shown only after a database connection is established. At that point, the deployment type is already known, and only the relevant code files are displayed. The create code file is also no longer shown when an sf_model_info or sf_product_info table is detected, as this indicates an upgrade scenario.After upgrading to this version of the platform, generate definitions and source code before running the next deployment. Authorization - Manage API access for client applicationsnew Intelligent Application ManagerPreviously, for API access for a client application you could either grant No access or Full access. To give you more control, you can now delegate roles to client applications to limit their API access.The following prerequisites must be met to use access delegation for a client application:The user must be allowed to delegate access. To set this up, go to the menu Authorization > Users > tab Form and select the checkbox Allow access delegation. The application must be allowed to delegate access. To set this up, go to the menu Authorization > Applications > tab Form and select the checkbox Allow access delegation.You could already create roles in the Software Factory and assign them to user groups. Now you can use these roles to manage client application access as well.To make roles available for delegation, go to the menu Authorization > Applications > tab Authorization settings > tab Access delegation roles. This tab was previously named tab Personal access token roles and has been renamed. Select the checkbox Available for delegation for each role you want to make available. These roles can be assigned to both Personal Access Tokens (PATs) and client applications.To set up limited access for a client application, go to the menu Client apps > Client applications > tab Form > group Access. In the field API access, select Limited access from the dropdown.Once you have set up limited access, the tab Access delegation roles is added to the screen. In this screen, you can select for each role whether they are:Enabled - This role is available for delegation to the client application. When a client application requests access, the user can select which roles to delegate in the consent screen. Required - This role is required for delegation to the client application. The client application must request this role when requesting access. The user cannot deselect this role in the consent screen, but can still choose to deny access entirely.When a client application with limited access requests access, it has to request scopes. These should be requested in the format {application alias}/{role id}. The supported scopes are the roles that you marked available in Access delegation roles for the client application. These can be found at https://<base_url>/indicium/.well-known/openid-configuration.The scopes that are requested by the client application are shown to the user in the consent screen. Requests on scopes that have been marked as Required cannot be deselected.Users can allow or deny access to a client application using the consent screen.The following settings have also been renamed as part of this update:Default allow PAT is renamed to Default allow access delegation (menu Authorization > Tenants > tab Form). This allows users to manage access delegations by default within a tenant. Allow personal access token creation is renamed to Allow PAT management. This allows users to create, update, and delete PATs.Finally, the Create IAM user and Update IAM user process actions now also include Allow access delegation as an input field. If no value is set for this input field, the value of Allow PAT management is used to preserve the behavior of existing integrations. The OpenID user template has been updated as well to include this setting. Authorization - Manage error log access for usersnew Intelligent Application ManagerPreviously, access to the Error log was limited to main administrators. Users who needed access for troubleshooting had to be given full administrator rights, which also allowed access to all administrative features. This is not always desirable.Instead, you can now manage a user's access to the error log in menu Authorization > Users > tab Administrators > tab Log access. Select a Tenant (if applicable) and a User. To set an access period, select a Begins on and Ends on date.Manage error log access for users in the tab 'Log access'Added 'security.txt' file for Indiciumnew IndiciumIndicium now exposes a security.txt file. This file helps security researchers find the right contact for responsible disclosure of security vulnerabilities.The file is available at:<server>/<indicium>/security.txt <server>/<indicium>/.well-known/security.txtThe email address used in the security.txt file is taken from the field Contact for system issues field in IAM. If no email address is configured, the endpoint returns a 404 error. Updated libraries for office file handlingchange IndiciumThe libraries for reading and creating Excel, PowerPoint, Word, and PDF files have been updated to the latest version. Performance and overall quality has been improved for several components, including the Preview screen component, and Import and Export functionality. Added pagination for tree viewsnew Universal UITreeview screen components now support pagination. If a dataset contains more records than the configured page size, a pagination footer appears at the bottom of the tree view.Users can navigate between pages using the mouse or keyboard shortcuts.Alt + Page Down to go to the next page. Alt + Page Up to go to the previous page. Added 'Clear cube view' to action barnew Universal UIUsers can now use Clear cube view from the action bar to reset a pivot grid. This improves usability as users no longer have to remove each field and clear any cube view filters individually.Clear cube view is unavailable if the cube panel is disabled for the cube. Select Enable cube panel to make the action available in the action bar. For more information, see Create a cube  Improved 'Model insight' panel and debug valueschange Universal UIModel insight has been updated for a better debugging experience. The panel now displays more debug information, with values grouped into dedicated sections. You can hover over task and report buttons to see their details. To copy debug values, use the Copy to clipboard button or select and copy values manually. The checkbox Screen type overlay has been added, allowing you to enable or disable the overlay.Additionally, the focus of Model Insight has been improved. Selecting an action bar, detail tile, chart, pivot grid, pivot grid field list, resource scheduler, or a detail tab page now correctly updates the context in the panel.The keyboard shortcut to open Model Insight has also been changed from Alt + F1 to Alt + F12 (macOS: Option + F12). The updated 'Model insight' panel now shows more debug information Configure debounce time for lookupschange Universal UIYou can now configure the debounce time for the lookup controls Suggestions (contains) and Suggestions (starts with). To do this, add the following properties to the config.json file:{ "searchDebounceTime": 300, "searchDebounceTimeMobile": 600}The default debounce time is 300ms on desktop and 600ms on mobile devices.The settings also apply to the Search in the action bar. Improved datetime filteringchange Universal UIPreviously, entering a date in a Datetime filter automatically filled the time condition with 00:00:00. The time field is no longer filled automatically, making it easier to filter on an entire day. If you do not enter a time in a Datetime filter, it now behaves as a Date filter. To insert the current time, press Space while the time field is focused. Improved sort order in lookup and domain dropdownschange Universal UIWhen typing in a lookup or domain field, dropdown results are now grouped. Results whose label starts with the typed value appear first, followed by options that only contain it elsewhere in the label.Previously, matching options were returned in no particular order, mixing results that started with the typed text together with partial matches.The most relevant option now appears at the top of the list and is automatically highlighted, reducing the number of keystrokes required to make a selection. For example, searching for ro in a country field now shows Romania before Morocco. Performance optimization for Universal UIchange Universal UIPreviously, Universal UI loaded all libraries and components on startup, including those only needed after login or when using a specific feature. To improve the startup time of Universal UI, these libraries and components are now loaded on demand. Features such as drag-and-drop, maps, and the grid and tree screen components may load briefly on first use as their data is fetched in the background. Added keyboard shortcut for component navigationYou can now use keyboard shortcuts to navigate between screen components:F6 to cycle forward through components. Shift + F6 to cycle backwards. Tab to navigate into the individual parts of a focused component. FixedSoftware Factory and Intelligent Application ManagerDB2 When deploying to a DB2 iSeries database that still needed to be created, the code execution screen (menu Deployment > Creation > tab Execute source code) remained empty, and deployment could not be executed. This has been fixed. DB2 Unit test output was not returned reliably when the result included a message, such as a referential integrity error in the mock data. This has been fixed. DB2 Some templates had a leftover parameter that would not be replaced when generating the control procedure. This has been fixed. In a role configuration with rights to the source table and a detail reference but not the target table, the detail reference was incorrectly returned to Indicium as available. This caused an error when loading the subject. This has been fixed. When non-default runtime configurations were added with the same RDBMS type as the default, the RDBMS type would be emptied and caused issues downstream. This has been fixed. Some references from prog_object to child tables were missing their ON DELETE CASCADE. This could leave items where the parent record was removed This has been fixed. When managing procedures in SQL Server and/or DB2 models, the developer was unable to have solely output parameters due to a scoping issue in the Default and Layout logic of subroutine parameters. This has been fixed. When copying or renaming tables or domains, some fields were improperly inserted/updated. This has been fixed.IndiciumImage and file parameters in a staged task or report that were populated by the object's default procedure showed a broken link. Opening the file resulted in a 404 error, and image previews were not displayed. This has been fixed.Universal UIWhen dragging a record with a lookup display value, the dragged item showed the key value instead of the display value. This has been fixed. Filtering on a lookup display column with a data type other than VARCHAR now works as expected. Minimal platform version 2026.3 or STS 2026.2.11 is required for this. Grid column widths no longer resize when a task or report is opened after a value has been edited in a cell. In Firefox, dropdowns inside grid header filters remained open after closing the filter panel. This has been fixed. When a value in an active record was changed with a process flow, the Universal UI did not wait long enough for the data refresh. This could cause bad_request errors, empty input parameters, or the flow to stop. This has been fixed. When editing code in an external file, sessions could disconnect unexpectedly when you switched between records, changed pages, or switched between open documents. This has been fixed. In task dialogs opened via drag-drop, lookup values in the task parameters now show display values instead of key values. If a user executes an offline task without completing all mandatory fields, the task pop-up reappears so the user can complete the missing fields. However, after the task was reopened, the Execute button remained disabled and the user could not resubmit the task. This has been fixed. Refreshing the browser while in a zoomed detail no longer reopens it as an unfiltered main subject. Error details for network requests that failed with HTTP status '0', for example because the user was offline, are now displayed. On mobile devices, the date picker no longer requires a double tap to open. Fixed an issue where entering a date between 01-01-1753 and 01-01-1900 incorrectly displayed a red error border. When the same node key value appeared on multiple rows, the hierarchy tree did not correctly display all items and nesting. This happened in cases where an item existed under multiple parents or where a group node and a leaf node shared the same identifier. This has been fixed. On a tab panel that contains only detail tab pages, the first visible tab page was not activated and its content was not loaded when other tab pages were hidden by the context stored procedure on document open. This has been fixed. Fixed an issue where lookup values in a form could be edited by double-clicking in a lookup popup while the column type was set to Read-only. Note that solely setting a column to Read-only (menu User interface > Subjects > tab Components) does not offer security, because the lookup column can still be edited through the grid, Mass update, and the Indicium API. Fixed an issue where if you copied and pasted code into the HTML editor it would strip whitespace and new lines. Fixed an issue where selecting a field with a lookup control in Update always used Suggestions (contains) instead of the lookup control specified in the data model. Fixed an issue for Export, where opening the link to the file caused an '404 Not Found' error. Data model changesData model changes for the Software Factory and IAM meta-models are listed here. This overview can be used as a reference to fix dynamic control procedures, dynamic model code or custom validations after an upgrade. Changes Software FactoryTable changesSF - From table SF - To table code_file_code -  Column changesSF - Table SF - From column SF - To column Mandatory Default value execute_source_code - deployment_method 0 - file_storage - use_storage_relative_path 1 1 file_storage_configuration - use_storage_relative_path 0 1 message_broker_message_mqtt_input_parmtr pre_processing pre_processing 1 0 prog_object - selected_for_install 1 1 prog_object - selected_for_upgrade 1 1 prog_object selected - - - prog_object_archive - selected_for_install 1 1 prog_object_archive - selected_for_upgrade 1 1 prog_object_archive - code_file_id 0 - prog_object_archive - order_no 0 - prog_object_archive generated_by_control_proc_id - - - prog_object_type prog_object_prefix - - - prog_object_type prog_object_suffix - - - runtime_configuration rdbms_type rdbms_type 1 - screen_type - modal_show_header 1 1 screen_type - modal_show_footer 1 1 sf_configuration - skip_import_base_data_in_import_model 1 0 sf_configuration - skip_vrs_check_in_import_model 1 0  Changes Intelligent Application ManagerTable changesIAM - From table IAM - To table - openid_client_gui_appl_role - usr_log_access gui_appl_authorization_pat gui_appl_authorization_delegation  Column changesIAM - Table IAM - From column IAM - To column Mandatory Default value col - has_elemnt 0 - gui_appl allow_pat allow_delegation 1 0 iam_file_storage - use_storage_relative_path 0 - openid_client required_consent required_consent 1 1 openid_provider_usr_template - allow_access_delegation_claim_id 0 - openid_provider_usr_template - allow_access_delegation_static_value 0 0 ref - look_up_display_has_elemnt 0 - ref - transl_has_elemnt 0 - report_parmtr - has_elemnt 0 - report_ref - look_up_display_has_elemnt 0 - report_ref - transl_has_elemnt 0 - screen_type - modal_show_header 1 1 screen_type - modal_show_footer 1 1 sf_file_storage - use_storage_relative_path 0 - task_parmtr - has_elemnt 0 - task_ref - look_up_display_has_elemnt 0 - task_ref - transl_has_elemnt 0 - usr_general - allow_access_delegation 1 0  

Related products:Software FactoryIntelligent Application ManagerUniversal UIIndicium Service Tier
End of SQL Server 2019 support

End of SQL Server 2019 support

Hi all,Notice for everyone still using SQL Server 2019 (15.x). Mainstream support by Microsoft has ended July 2025. As per our lifecycle policy, official support for this version will be discontinued in a future release.As it stands, Thinkwise Platform LTS 2026.3 and STS 2026.2.11 will no longer officially support SQL Server 2019 and will require SQL Server 2022 or higher. Note that the current release of the Thinkwise Platform (version 2026.2) still supports SQL Server 2019.Impact on the platform databasesThe Software Factory (SF) and the Intelligent Application Manager (IAM) are planned to leverage T-SQL language features exclusive to SQL Server 2022 and up. The Deployment Center will prevent installation or upgrade of an SF or IAM to version 2026.2.11 and beyond when the SQL Server version is 2019 or lower, or the database compatibility level is equal to or below 150.Impact on product databasesSQL Server product databases running on SQL Server 2019 do not have to be upgraded directly on release of Thinkwise Platform 2026.2.11. However, runtime components with version number 2026.2.* and higher may start using SQL Server 2022 language features on a moment’s notice.Furthermore, Software Factory version 2026.2.11 may not be able to upgrade, deploy or test product databases using SQL Server 2019. To be able to continue development on the product, upgrading to SQL Server 2022+ will be required.The changes in SQL Server version support will be reflected in the lifecycle policy.It is forecasted that the end of support for SQL Server 2022 will be January 2028.

Related products:Software FactoryIntelligent Application ManagerUniversal UIIndicium Service TierUpcycler