release notes

Release notes Indicium (2021.3.18)

Related products: Indicium Service Tier
Release notes Indicium (2021.3.18)

Hello everyone,

In this sprint, we have improved our support for OData's $expand query options. It is now possible to include 1:N references. We also improved the performance of the Application Connector.

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

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

 

Table of contents

 

Indicium Universal

 

Improved support for OData's $expand query options

OData's $expand query option allows you to include related entities in the response within a single request. We already supported this for 1:1 references, such as look-ups, to fetch the display value. Now, we also support this for 1:N references. This is especially interesting for retrieving the detail records for each parent record.

To expand a detail within the context of a parent, the request should look like this:

<indicium_base_url>/<meta>/<application>/<parent_entity>?$expand=detail_<ref_id>

For example:

https://server/indicium/iam/appl/sales_order?$expand=detail_ref_sales_order_sales_order_line 

Most of the regular OData query options, such as $select and $filter, can be applied to the expanded detail as well. They can be added as a semicolon-separated list between parentheses.

For example:

https://server/indicium/iam/appl/sales_order?$expand=detail_ref_sales_order_sales_order_line($select=sales_order_id,sales_order_line_id;$filter=sales_order_line_cost gt 10)

 

Improved performance of the Application Connector

The performance of the Application Connector has been improved by loading only the relevant model information, instead of the entire application model.

 

Minor fixes and tasks

  • We fixed that a user could not give consent to OpenID offline access. Because of this, Indicium could not hand out refresh tokens when consent was required.
  • We fixed that ongoing process flows were aborted after a tsf_send_message (or raiserror) from a trigger or a stored procedure.
  • We fixed an issue that caused the process flow API to be case-sensitive. With this fix, the casing of the request URL is no longer relevant.