Thinkwise Platform 2026.2

This release strengthens the Manufacturing Execution System (MES) capabilities of the Thinkwise Platform with the introduction of MQTT broker capabilities. The MQTT protocol is the de facto Industry 4.0 standard for real-time interaction with machines and sensors, allowing customers to use the Thinkwise Platform for both ERP and MES capabilities in a single solution.

Flexibility in deployment options and database technologies is core to our proposition. In preparation for IAM support on Db2 and PostgreSQL, it is now possible to link multiple RDBMS types to a single Software Factory model. Customers can use this to deploy their application on different database platforms or to migrate to PostgreSQL, for which Enrichments support is planned in a later release. In addition, Custom components can now be uploaded directly in the Software Factory, simplifying their deployment, especially in container environments.

The Scheduler now offers improved configurability, including a new datetime condition type for cell colors, the ability to display day names and HTML support for activities.

Four new IAM user management process actions are now available to create and update users, and assign user groups in IAM directly from an end application. This allows you to manage IAM users without needing to access the IAM, which can be useful for scenarios such as onboarding new employees.

While not strictly related to this Platform release, we would like to highlight that the Universal UI now better supports Offline field service scenarios with the introduction of offline data and table tasks.

The Software Factory now also supports working in different branches across different browser tabs.

Contents

Fixed in Universal UI and Indicium (2026.2.10)

The Indicium and Universal UI 2026.2.10 fixes below are backwards compatible with previous Thinkwise Platform versions. Therefore, these fixes are not part of the release notes for Thinkwise Platform 2026.2.

Security fix for HTML control in Universal UI

Several cross-site scripting (XSS) vulnerabilities were identified in TinyMCE, the library that powers the HTML editor in Universal UI. This vulnerability affected subjects including an HTML control field that is in edit mode. An attacker would then have to be able to influence the data displayed in that HTML editor. We have applied the necessary patches to mitigate these vulnerabilities.

Indicium

• Fixed an issue where the Mass update endpoint did not work as expected in a specific context.

Universal UI

• In a process flow, logging in with the OAuth user login connector without a successor action now closes the pop-up when the login is successful.
• Previously, in a cube, any dimension or category field with the width set below the minimum of 50px caused the custom widths of all fields to be reset to their defaults. This has been fixed.
• In a cube view with a datetime domain as a row category and the timezone set to Show as stored, expanding a datetime row produced a 'Bad Request' error. This was caused by a missing timezone identifier in the request. This has been fixed.
• When auto-refresh with change detection was active, the staged resource of a detail was discarded on every refresh, even when there were no changes. This caused the detail to no longer be editable. This has been fixed.
• When a tsf_send_message was called in a Change detection control procedure, the message notification appeared twice. This has been fixed.
• When adding or copying a row in a default-editable grid, selecting a checkbox no longer saves the row immediately. The row now stays in add or copy mode until the user selects Save.
• When Model Insight was enabled, focus behavior in editable form controls was inconsistent. Controls could receive focus unexpectedly, receive focus twice, or be difficult to focus in the intended state. This has been fixed for radio buttons, signature controls, HTML controls, and form control wrappers, resulting in more predictable keyboard navigation while Model Insight is active.
• When using multiple detailed time scales at the same time (for example, Month + Day + Hour + Minute), the Scheduler could show collapsed hour headers and missing minute labels. This has been fixed. If the configuration exceeds the rendering limit, the Scheduler now automatically adjusts by widening or removing the finest time scale. A warning is shown in Developer mode.
• When Labels for lowest timescale is disabled and the second lowest timescale is hours with the lowest being minutes, minute timescale slots are now displayed as virtual slots. Virtual slots are not directly visible, but events can still be dropped, moved, and resized per minute. For more information, see Scheduler views and timescales.