Skip to main content

Hello everyone,

In this sprint, we changed the process flow behavior when this flow is marked as Deep linking allowed. Also, we made some logging improvements, and we added a session variable for the actual logged-in user.

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

We will keep you updated regularly about Indicium's progress.

About Indicium

Two types of the Thinkwise Indicium Application Tier are available:

  • Indicium Basic: for use with the Windows GUI and Mobile GUI. This basic version does not support, for example, 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 2022.2.14 here.

Contents of this release

 

Breaking

Process flows behavior when marked as Deep linking allowed

Process flows marked as Deep linking allowed were never intended to be started automatically by their start actions: a task or adding a record should never start the process flow.

These process flows were not started automatically in the Thinkwise Windows and Web GUIs, as intended.
However, Indicium was inconsistent in this matter and this has been corrected in this release. Deep links must be started via an API call to the process flow itself, which initiates the process flow start action in the GUI. While this was always the intent of the feature, this is a breaking change for Indicium, so please be aware of this change.

Indicium - New

Logging improvements

In this release, we have added more logging functionality to make troubleshooting easier.

  • When a default procedure sets a value for a lookup property that is not hidden from the user, and the value is outside of this user's mandatory lookup prefilters, Indicium would reject this value and set the lookup property to null. Since it was difficult to see why this was happening, we added an error log message for this.
  • All log messages related to process flows now also contain the application ID to which the process flow belongs. This is especially useful when troubleshooting scheduled system flows.

New session variable for the actual logged-in user

When simulating users, you can now use the tsf_original_login session variable to retrieve the user who initially logged in. In this release, you can use this session variable as follows:

  • On SQL Server: select SESSION_CONTEXT(N'tsf_original_login')
  • On Oracle: select sys_context('session_vars', 'tsf_original_login') from dual;

Indicium - Changed

Process flow behavior when canceled by the user

In a process flow, when the first action is a task or report, and the user cancels the popup dialog, until now, the process flow was not started. Indicium will now continue the process flow if the last process action was not successful (marked by a red arrow), and indicates that the result of the task is "User canceled".

Hello everyone,

We have released a hotfix for this version of Indicium Universal, which is available for download as version 2022.2.14.1.

This hotfix release fixes an issue that caused Indicium to cache and reuse various application-level settings (e.g. database server, database name, extended properties) between different applications of the same project and project version. This issue would only occur for users with identical role assignments in these different applications.

This issue was introduced in version 2022.2.12.0 of Indicium Universal. If you make use of multiple applications for the same project and project version and you are currently on 2022.2.12.x, 2022.2.13.x or 2022.2.14.0, then we recommend updating to version 2022.2.14.1 as soon as possible.

Our apologies for any inconvenience caused by this issue.

@Vincent Doppenberg Would the error in TCP 4848S also be explained by this bug, or do you think there's another reason for that one?

Hello Arie,

No, I don’t think that this issue is related, but I will look into your ticket.

Terms & ConditionsCookie settings