Release notes Indicium (2025.1.15)

Hello everyone,

In this release, we have updated the library that connects to OpenAI and Azure OpenAI. Note that you should switch to a supported chat model if you use an LLM completion process flow connector, as some legacy models are no longer supported.

You can read more about Indicium's features in the Indicium user manual.

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.1.15 here.

Contents

• Release notes Indicium (2025.1.15)
  • About Indicium
  • Breaking
    • Updated LLM connectors library
  • Minor fixes and tasks
  • Questions or suggestions?

Breaking

Updated LLM connectors library

change

We have updated the library that connects to OpenAI and Azure OpenAI, adding support for newer reasoning models like o3-mini.

In addition, the following completion models are considered legacy by OpenAI and Azure OpenAI and are no longer supported by the Thinkwise Platform:

• davinci-002
• babbage-002
• gpt-3.5-turbo-instruct 

Minor fixes and tasks

• When a badge was configured for a table task or report with parameters, the badge did not update correctly. This has been fixed.
• Indicium did not generate the correct query for a SUM aggregation on a bit column. In addition, if the SUM returns a too-large value for a tinyint, it would return an error. Both issues have been fixed.
• Previously, when the default procedure modified a value but only changed its casing, it did not notify the Universal UI to refresh the data. This behavior has now been corrected: the Universal GUI is properly updated when such changes occur.
• Using the Indicium API for clearing a file column did not work. This has been fixed. In a POST/PATCH request, a body with {"fileProperty": null} now properly clears the file.
• We have fixed an issue that caused the Move file process flow connector to not work for Azure File storage. The target file would have the same length, but be filled with NULL bytes.

Questions or suggestions?