Hello everyone,
In this sprint, we have improved the logging and the import functionality. We have also solved some issues.
You can read the Indicium user manual to read about Indicium's features.
We will keep you updated regularly about Indicium's progress.
Breaking
Indicium Universal: Process procedure errors now stop the process flow
From now on, errors in process procedures will abort your process flow or system flow. Previously, the order from the model was used if something went wrong, but this could cause unintended effects when the process procedure did not work as expected.
Indicium Basic: Support for IAM/Software Factory 2019.2 expired
The support for reading application models from the Thinkwise Platform version 2019.2 has expired. Please update IAM and the Software Factory to at least version 2020.1 to use this version of Indicium.
Indicium Basic: Now requires the IIS module AspNetCoreModuleV2 to be installed
Install the latest ASP.NET Core Windows Hosting module that is linked here.
Indicium Universal
Updating rows when importing
When you tell Indicium not to insert rows and only update, it will throw an error for the rows it cannot update. So, you can download the failed records into a new Excel file.
To control this behavior, two new query string parameters have been added to the stage_import endpoint: add_new_rows and update_existing_rows. Their values can be set to true and false, but at least one of them must be true.
Improved logging
In this version of Indicium, we improved the logging, to make it easier to detect where an error occurred.
- In process flows and system flows, it is now clear which step caused the error.
- System flows with invalid actions are logged now.
- More explanation is available for errors that occurred when editing a resource.
Changes
- Indicium will no longer treat an SQL print message as a TSF message. In the near future, SQL print messages will be logged to Indicium Universal's Database Event Log.
Minor fixes and tasks
- We solved an issue that occurred when you used mandatory exclusive prefilter groups, and the table had an expression column. This issue could cause Indicium to crash and require a restart.
- On some occasions, Indicium would call the subroutine procedures with the wrong parameter order on DB2. This has been fixed.
- We solved an issue with the query for lookup references that contained an expression column in its target columns.
- When configuring an API alias for subroutine parameters, the API alias was not used correctly. This has been fixed.
- We fixed an issue that could cause failed queries for the combination of `select detail` references with `groupby' clauses. In particular, this could cause pivot grid and charts on detail subjects unable to load their data.