Important: the Process flow API of Indicium contains breaking changes in version 2025.3.14. To keep Process flows working, the versions of Indicium and Universal UI / Windows GUI 3-tier should be in sync.
Hello everyone,
In this release we have introduced a new health check for Redis, improved the reloading of settings, and fixed several issues. Note that this release includes a breaking change, so make sure to read the details below.
You can read more about Indicium's features in the Indicium user manual.
Do you have any questions or suggestions? Let us know in the Thinkwise Community!
About Indicium
Two types of the Thinkwise Indicium Application Tier are available:
- Indicium Basic (EoL): for use with the Windows GUI and Mobile GUI. This basic version does not support features such as system flows and OpenID.
- Indicium: for use with the Universal GUI and via APIs. This version uses the full range of Indicium functionality.
Download Indicium release 2025.3.14 here.
Contents
Breaking
Process flow API changed
breaking
We have made a change to the process flow API to support a new feature for process flows. This feature will be introduced in Thinkwise platform version 2026.1.
This change affects Indicium running against older platform versions. If your Indicium, Universal UI, or Windows GUI 3-tier is older than version 2025.3.14, you may encounter issues with process flows that have multiple starting points. To prevent possible issues, keep your Indicium and Universal UI or Windows GUI 3-tier on the same version and upgrade to the latest version.
Technical details of the API change
A process flow can be started with a POST call to the /process_flow_id endpoint, this has not changed. If the process flow runs into an action that needs to be handled by the client (such as an Open document or a Go to row action), it will respond with a Location header that contains a URL points to the pending process action. The client uses this URL to continue the process action via a POST on /continue. However, when you want to start a process flow via a UI action and the process flow has multiple starting actions, then it is the responsibility of the client to append the ID of the process action to the URL returned in the Location header to start the process flow. This is where the breaking change occurs.
For example, calling POST /process_flow_id on such a process flow will return:Location: /my_process_flow(<guid>).
Previously, the client would have to append the following to start the process flow:
/my_process_flow(<guid>)/my_process_action/continue/my_process_flow(<guid>)/my_process_flow.my_process_action/continue
New and changed
Added health check for Redis
new
Indicium now includes a health check for when Redis has been configured.
Health checks in Indicium can be accessed via the /health endpoint.
See also, Health check endpoint.
Reloading settings in the background
change
In the Indicium 2025.3.13 release, we ensured that Global, Web Domain and Client Application settings are reloaded automatically from IAM without requiring a restart of Indicium.
We have extended this functionality to include OpenID Connect Provider settings as well. Indicium will now reload OpenID Connect Provider settings automatically in a 1 minute interval. This means that adding, updating or removing an OpenID Connect provider in IAM will no longer require a restart of Indicium.
Resolved BOM handling issue when converting binary to text
change
An issue caused by incorrect handling of byte order marks (BOM) when converting binary data to text has been resolved. This issue would occur when mapping a binary output parameter of a process action (for example on a Read file connector) to a text process variable, such as (n)varchar. If the binary data contained a byte order mark (2-4 bytes at the beginning, indicating encoding), these bytes would also be converted to text, resulting in several unprintable characters at the start. With this change, if a byte order mark is present, Indicium will now use that encoding instead of the provided encoding input parameter.
'Open link' process action supports relative URLs
change
The Open Link process action now supports relative URLs as well (rooted by the Universal GUI that receives the process action), instead of only absolute URLs.
Minor fixes and tasks
- Fixed an issue where DevExpress reports using C# scripts failed to run when the
Reporting:DevExpress:Runtimewas set to useNETwith theReporting:DevExpress:UnsafeScriptsoption enabled. Windows machines default to usingNETFrameworkfor theReporting:DevExpress:Runtimeand were not impacted unless explicitly configured this way.
-
DB2: You can now send abort messages using
tsf_send_messagefrom a trigger when using a DB2 driver that requires DB2 Connect (settingDataProviders:DB2:ModetoCoreinstead ofiSeries).To use this feature, Thinkwise platform version 2025.3.11 or higher is required. If you are on a lower version, you can set the extended property
DB2UseNewMessageBuffertotrue.
