Release notes Thinkwise Platform 2026.1.15

Hello everyone,

A major highlight of this release is the new Custom components screen in the Software Factory. Custom components can now be uploaded as a .zip file and stored directly in the database, making them available in containerized deployments too. This removes the previous dependency on hosting custom components alongside the Universal UI, significantly broadening where and how custom components can be used.

In the Software Factory, you can now configure validations from base models. The Default enabled, Severity, and Allow approval indefinitely values can now be updated for validations that originate from a base model, giving you more control over the validation behavior in your work model without losing the connection to the base model.

This release also brings significant improvements to the Universal UI, with an expansion of the offline functionality. Users can now access subjects offline, including viewing tables and executing tasks. This provides more flexibility in how and when users can work in an application, even without an internet connection.

The Scheduler has also received notable updates. Activities and tooltips can now display formatted text, including bold titles, icons, bullet lists, and hyperlinks. Additionally, sliding pagination for Quarter and Month timescales now shows extra context at the start of the view.

This release includes several preparations for the upcoming Thinkwise Platform 2026.2 release. In the Software Factory, the data model has been updated in preparation for multiple RDBMS type support. The Slow query log now replaces data values with placeholders to prevent sensitive data from being written to the log. Check the breaking changes and data model changes to ensure a smooth upgrade.

 Contents

Before you upgrade

• Features 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 download

• Try a demo of the Thinkwise Platform here.
• Download the latest versions of our components here.

Breaking

Thinkwise Platform 2024.1 - End of Service Life

breaking Universal UI

As per our Lifecycle policy, support for by the Universal UI for Thinkwise Platform version 2024.1 has ended and will receive no further updates. Upgrade to Thinkwise Platform 2024.2 or higher.

Data model changes in preparation for multiple RDBMS types

breaking Software Factory

The Software Factory data model has been updated to prepare for multiple RDBMS type support. This feature is planned for the Thinkwise Platform 2026.2 release.

The following areas are impacted:

• Dynamic model: Query fields have moved from their original tables to _query-suffixed tables.

  Verify all Dynamic model code to ensure query fields are read from and written to the correct table.

  Example: A query previously written to tab_prefilter must now target tab_prefilter_query.

• Validations: Any validation that references a query field in a table must be updated to reference the _query-suffixed version of that table.

• Business Logic: Control procedures that use SQL assignments with the Delete or Fully controlled strategy and insert into any of the following tables must now include rdbms_type in the insert:

  - prog_object 
  - prog_object_parmtr 
  - prog_object_item 
  - prog_object_item_parmtr

  When using the Staged strategy, the Software Factory itself processes the data from the staging tables into the model, allowing the Software Factory to fill in the rdbms_type field for you.

  Use the following values for rdbms_type:

  Value	RDBMS type
  0	SQL Server
  1	DB2 iSeries
  3	Oracle
  4	PostgreSQL

'Slow query log' uses placeholders for data values

breaking Indicium

The Slow query log no longer stores data values in log entries for Thinkwise Platform 2026.1.14 and older. To prevent sensitive data from being written to the log, values are now replaced with ?. For example, filter values, inserted record values, and task parameter values are all logged as ?. The structure of the database statement remains intact, so you can replace the ? placeholders with actual values for troubleshooting.

You can control whether the Slow query log stores data values Thinkwise Platform 2026.1.15 onwards. You can do this by enabling or disabling the checkbox Include data in slow query log in the Intelligent application manager (menu Settings > Global settings > group Logging).

Re-enable offline availability with extended property

breaking Universal UI

As a result of making subjects and subject variants available offline, we have added an extended property to toggle this functionality. If you have set up offline availability, set the extended property AllowOfflineExperience to Yes to enable it. If you do not set this extended property, subjects will not be available offline after the upgrade.

Check process flows with 'Open document' action

breaking Universal UI

As a result of updating the behavior of the Open document action with Open as set to Floating, some existing process flows may now behave differently after this release.

Check all existing process flows that use the Open document action (menu User Interface > Process flows) with the input parameter Open as set to Floating to ensure they still behave as expected after the upgrade.

'Grid column width' now displays as configured

breaking Universal UI

Previously, the value entered in the field Grid column width did not match the width being displayed in the Universal UI. A default grid padding of 8px (or 16px in comfortable mode) was added to every column's width, which meant the configured width was not the actual width of the column. Now, columns have the same width as configured in the field Grid column width.

Read-only password fields now show action button

breaking Universal UI

Previously, the action button for password control fields was only shown in edit mode, regardless of the setting for Show action button (menu Data > Domains > tab Form). Now, password control fields adhere to this setting.

New and changed

User interface - Added 'Custom components' screen

new Software Factory Universal UI

Custom components let you extend your application with functionality specific to your organization that is not part of the standard Thinkwise component set. Previously, you could add custom components by placing them in a subdirectory of the Universal UI and referencing that location as a URL segment. In Thinkwise Cloud, this is not possible because running your own containers is not supported.

To address this, a Custom components screen (menu User interface > Custom components) has been added to the Software Factory. This screen acts as a repository where each custom component can be uploaded as a .zip file and stored in the database, similar to how icons are managed. For each custom component, you can provide:

• A Description.
• A Default entry point, which specifies the file inside the .zip file used to start the custom component (for example, index.html).

The Usage tab shows which tables and table variants use the custom component.

At table and table variant level, you can set the Custom component source to Model or External:

• Model — uses the new repository. Select a custom component via a lookup and specify the Entry point. If the selected custom component has a default entry point defined, it is applied automatically. This can be overridden. You can use {metasource} and {application} variables in the entry point to refer to different versions of the custom component.
• External — uses the existing URL-based approach. When you upgrade, sources for existing custom component references are automatically migrated to External.

At table variant level, you can override the table configuration. This includes whether a custom component is used, which source is applied, and which component is selected. This way, different variants of the same table can use different custom components without affecting each other.

Quality - Configure validations from base models

Community idea new Software Factory

You can now update the Default enabled, Severity, and Allow approval indefinitely values for validations that originate from a base model. You can update these values using the following tasks (menu Quality > Validations > tab Maintenance):

• Enable/disable validation
• Enable/disable allow approval indefinitely
• Update severity

Once you have manually updated a validation, the updated value is shown in the tab Validation configuration. You can filter on the prefilter Has different configuration to easily find validations that have been updated.

Custom values are set within the context of the current model and branch, and are not overwritten when the corresponding base model is generated or merged into the work model. They also remain in place when the full definition of the work model is generated. If you want to remove custom values for validations, you can Delete them in the tab Maintenance > tab Validation configuration.

As part of this update, a section of the Thinkwise guideline validations has been added to the Validations base model in the Software Factory. This includes validations for column names, domain names, primary key columns, references, table names, screen types, domain controls, icons, prefilters, tab containers, tasks, reports, and control procedures.

Added extended property 'MaxStageRowLimit'

new Indicium

Currently, there is a default limit of 5000 records for actions performed in Indicium, such as deleting records or executing tasks. The extended property MaxStageRowLimit has been added to allow you to increase this default limit. The property can be set with the following values:

• -1: Actions can be performed on an unlimited number of rows.
• > 5000: The limit is set to the configured number of records.
• Not set or < 5000: The default limit of 5000 records is enforced.

As part of this update, the error message shown when the limit is exceeded has also been improved. Instead of the generic validation_failed message, the error now indicates that the maximum allowed number of rows has been exceeded.

Updated email library

change Indicium

The email library used by Indicium has been updated to the latest version. Sending emails through the email connector and the Forgot your password link continues to work as before.

Subjects now available offline

new Universal UI

We have expanded the offline functionality in the Universal UI. Users can now access subjects offline, allowing for more flexibility in how and when they can work in an application.

Users can:

• View tables and table variants in a subject
• Execute table tasks
• Execute menu tasks

To set up offline availability, set the extended property AllowOfflineExperience to Yes.

To make a table or a table variant available offline, select the checkbox Offline available in the menu User Interface > Subjects > tab Default/Variants > tab Settings > tab Components > group Offline. See also, Offline availability and Offline available task for more information.

For offline available tasks, configure the following settings:

• The tasks cannot contain lookups.
• The tasks will check for mandatory fields but make no other validations.
• The tasks will not execute application logic for parameter input. This will be done later when the user is online again.
• The task control procedures should accept all input without throwing errors since a user cannot fix these when synchronizing afterward.
• All parameters filled through the task should set to Hidden.

If you use a task variant or table variant, configure the following settings:

• All prefilters must be set to Hidden.
• The following permissions should be disabled:
  • Add, copy, update, delete.
  • Grouping, sorting, and filtering.
  • Import and export.
• Table tasks, other than the offline available task, should be disabled.
• Reports should be disabled.
• Paging should be disabled.
• Lookups should be hidden (clear the checkbox Show look-up, see Use a column as a lookup.
• Drag-drop should be disabled (clear the checkbox Def. drag-drop enabled, see Enable drag-drop in a grid by default.
• The subject can not be used in a cube, map or Scheduler.

In an upcoming release, these settings will automatically be disabled when you create a subject variant.

Model insight now shows task and report names

new Universal UI

When selecting fields belonging to a task or report, Model insight now shows the task or report name in a dedicated field. This makes it easier to see which fields belong to a specific task or report. Additionally, parameters for tasks and reports are now labeled Parameter instead of Column.

Improved sliding pagination for the Scheduler

change Universal UI

Sliding pagination in a Scheduler provides a sliding window of time around the current date and time. Previously, only the Year timescale showed additional context at the start, with the Scheduler view showing a month before the current month. For Quarter and Month timescales, no extra context was shown at the start of the view.

We have now made additional context available for Quarter and Month timescales. The amount of context shown at the start depends on the highest timescale:

• Quarter or Month: an extra week is shown at the start of the view.
• Year: an extra month is shown at the start, followed by the full year or years.

As part of this update, we fixed an issue where adding a month to the start of the view caused the last month of the final year to be removed.

Add text formatting to Scheduler activities

change Universal UI

Previously, activities in a Scheduler were always displayed as a single line of plain text.

You can now add text formatting to activities and their tooltips in a Scheduler, as well as multiple lines of text. This allows for more flexibility in the content and appearance of activities in a Scheduler.

• To add formatting to an activity, select a domain with a Multiline or HTML control as the Title column of the activity (menu User interface > Schedulers > tab Tables).
• To add formatting to a tooltip, select a column with an HTML control as the Tooltip column of the activity (menu User interface > Schedulers > tab Default/Variants > group Activity linked columns).

See Set up a Scheduler for more information.

SELECT
  '<div
    class="activity-wrapper"
    style="max-height:200px; overflow:hidden;"
  >
    <style>.activity-wrapper h2 { margin: 0; }</style>' +
  t1.event_html +
  '</div>'

Improved behavior of 'Open document' action

change Universal UI

Previously, when a process flow used the Open document action with Open as set to Floating, the process flow stopped executing after opening the floating document.

The process flow now continues executing inside the floating document. This can be used, for example, to jump to a specific record or to filter the data.

When the process flow triggers the Close document action, the floating browser window closes and execution continues in the document behind.

Improved behavior of 'Favorites' and 'Start objects'

change Universal UI main administrator

We have improved the behavior of Favorites and Start objects to better reflect their different purposes.

Previously, you could configure Start objects for a user in IAM. These objects would automatically start when opening the application. We have renamed start objects for a user to Favorites and changed its behavior. Menu items marked as Favorite are no longer automatically started. Instead, the Favorites group is now expanded by default.

Administrators can still configure Start objects for user groups in IAM. These still work as before and start automatically on startup. To align with their behavior, these objects are no longer shown in Favorites.

Invalid date no longer automatically corrected

change Universal UI

Previously, when a user would type an invalid date in a date field (for example, 02-30-2026), the Universal UI would automatically correct this to a valid date (in this case, 03-02-2026). This could occur without the user noticing, potentially leading to incorrect dates being saved. Now, if the user enters an invalid date, the field is highlighted with a red border and an error message is shown to indicate that the date is invalid. The date must be corrected before the user can save the form.

Updated keyboard shortcut for column header filtering

change Universal UI

Pressing Ctrl + Enter now applies the filter and closes the filter popup when using Excel-style filters in a grid column header. Filters that already closed using Enter alone, such as date time filters, can still be applied with or without pressing Ctrl.

Fixed

Software Factory and Intelligent Application Manager

• DB2 In DB2 models, each code file previously started with a set schema and set path statement. These statements were always based on the database configured in the default runtime configuration, even when connecting through a different runtime configuration. As a result, code could unintentionally be executed against the wrong database. This has been fixed by removing the set schema and set path statements from the start of code files. The provision_db process action during installs and the application_connector process action during upgrades already set the correct schema and path, making these statements redundant.
• The task Update Active Directory group in IAM (menu Authorization > User groups) assigned the old language code for English to newly imported users from the active directory group. This has been fixed. New users will receive the en-US language code.
• When setting up a custom action bar, including and then excluding an action via edit-in-grid could clear mandatory fields. This prevented you from saving the record. This has been fixed.
• Previously, setting a tab page icon required uploading a file separately. You can now select it from the central repository in the Software Factory, similar to other places in the Software Factory where icons are used.
• The task Assign rights in Roles is now a primary action (menu Access control > Roles). 

Indicium

• If an expression field was set to Editable and Mandatory, the mandatory check was not performed. This has been fixed.

Universal UI

For grids:

• When filtering in a grid column header, translation objects of domain elements were not displayed correctly. This has been fixed.
• When filtering in a grid header that used a lookup with domain element translations, the translations were not displayed correctly. This has been fixed.
• Fixed an issue where switching rows in a grid while the form was in edit mode and Auto-save was enabled, the form would not update to display the data of the newly selected row.
• When switching between rows in a grid, the Universal UI would start loading data for a detail tab before context logic had finished executing. If the context logic caused the active tab to become hidden, the data request could be processed against an invalid context, resulting in data-type errors. This has been fixed.

For pivot grids:

• When all categories or rows in a pivot grid were expanded by default, the tree expanded slowly on screen. We have optimized the performance of pivot grids to fix this issue.
• Fixed an issue where the Universal UI could crash if you sorted on a date (part) in a pivot grid.

For Schedulers:

• Font size, strikethrough, and underline font styling are now applied to Scheduler activities. Scheduler activities containing HTML content will not apply these decorations or font sizes.
• Scheduler events now return to their original position, if a user attempts to drag items that have no update permissions.
• When a hierarchical Scheduler had an ID containing double quotes ("), expanding the corresponding level would cause the Scheduler to freeze. This has been fixed.

For process flows:

• Fixed an issue where a process flow would stop after using the Close all documents process flow action.
• The Change filters process action now no longer hangs when used in a process flow on a document that starts empty with filter.

Other fixes:

• Fixed an issue where resizing the browser window to a smaller size and then back to a larger size, could cause task popups containing a Code diff editor control to slowly grow back to their original size instead of resizing instantly.
• A task popup containing a Signature control could shrink in size after opening. This has been fixed.
• Improved the Treeview performance for large datasets.
• Model insight is now deactivated if the session expires or the user logs out.
• When a request to Indicium fails due to a URL path segment longer than 260 characters, an error message is now displayed:
  • For users: 'The request URL contains segments which are too long. Please contact your system administrator.'
  • For developers: 'The request URL contains segments which are possibly too long. The longest segment was [segment length].'
• Trailing whitespaces are now stripped from lookup values in Form. This aligns with the default display behavior of values in the Universal UI.
• The Maps component now adheres to the zoom limits defined per layer and overlay, so zooming in and out stays within the range intended for each map style. When a map opens or is navigated to via a process action, the zoom level is automatically adjusted to stay within the supported range for the active layer.
• If the data used for an Import contained a period ('.'), the data preview would not display the data correctly. This has been fixed.
• When uploading a file or image through a task that had a confirmation pop-up, a 422 error occurred and the file was not uploaded. This has been fixed.
• The Switch branch did not automatically execute in the Software Factory in the Universal UI. This has been fixed.

Data model changes

Data 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 Factory

Table changes

Column changes

Changes Intelligent Application Manager

Table changes

Column changes