Release notes Indicium 2023.1.16

Hello everyone,

In this sprint, we have fixed a couple of issues.

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: for use with the Universal GUI and via APIs. This version uses the full range of Indicium functionality.
  Download Indicium release 2023.1.16 here.

• Indicium Basic: for use with the Windows GUI and Mobile GUI. This basic version does not support, for example, system flows and OpenID.
  No 2023.1.16 release available.

Indicium - Changes

Minor fixes and tasks

• Previously, if an email address in an EML file was corrupt or contained an unexpected value, Indicium would not show an email preview.

  Indicium will now skip the corrupt or unexpected value and display the email preview regardless.

• Previously, when clearing the default value of a column during an add record action, the column would still be given the default value after saving the record.

  Indicium now correctly saves the resource with a null value for that column, if it has been cleared.

• Previously, if a Delete Row process action could not be executed, for example, if the row does not exist or if there are no rows to delete, a continue call was not possible.

  The reason for this is that the process actions would automatically continue when the edit or delete action was being executed on Indicium.

  Now, you can continue such a process action, but only with negative status codes, so that if something goes wrong, the process flow can continue with the fail path.

• In our last release notes, we listed the following fix:
  
  Indicium adds Server-Timing headers to the response to provide extra information on how long certain things take during the request. When importing, this could lead to a gateway error, depending on where Indicium is hosted and how many rows were imported due to a limit on response header data.
  To avoid this, if more than 20 Server-Timing values have been added, Indicium will now aggregate the entire duration for each Server-Timing category/key instead of adding separate entries per imported row.
  
  Due to an oversight, this fix was not included in the last release, but it has been included in this release.

Questions or suggestions?