Indicium Universal 2021.1.12 hotfix release

Related products: Indicium Service Tier
Indicium Universal 2021.1.12 hotfix release

Hello everyone,

We have released version 2022.1.12 of Indicium Universal, which contains two hotfixes. If you are on platform version 2021.3 or above and you are not targeting a DB2 database server, then you can ignore this release and await our next feature release on Friday.

Task confirmation messages

This hotfix applies to platform versions 2021.2 and below. When a task was configured to have a confirmation message, an error would occur when attempting to execute the task from the Universal GUI. This error was caused due to a mismatch between supported versions for confirmation messages. The Universal GUI supported this feature on every platform version, whereas Indicium Universal only supported it from version 2021.3 onwards. Important: this hotfix also requires the latest SF and IAM hotfixes to be installed, otherwise it will not work.

Layout procedures on DB2

This hotfix only applies when Indicium’s appsettings.json is configured to use the iSeries mode, not the Core mode. It fixes an error regarding the procedure parameters that could occur when calling the layout procedure.

 

Version 2022.1.12 of Indicium Universal can be downloaded here. Our apologies for any inconvenience caused by these issues.

Layout procedures on DB2

This hotfix only applies when Indicium’s appsettings.json is configured to use the iSeries mode, not the Core mode. It fixes an error regarding the procedure parameters that could occur when calling the layout procedure.

@Vincent Doppenberg To clarify:

  • Do I understand it correctly that this particular issue also applies to Thinkwise Platform 2021.3 and up?
  • If so, since which Indicium version does this issue occur? Only in the latest 2022.1.11 version or more versions back?

Hi Arie,

The issue was present already present in multiple versions, it looks like it was already in 2021.2. The issue only occurred on tasks and reports with a layout and it would give an HTTP 500 instead of executing normally.


@Dick van den Brink Check, thanks for the clarification!