General

Authentication to the INUBIT REST API is now always carried out by default against the user management configured in INUBIT. If the authentication is to be carried out against the Process User Server configured in the INUBIT (e.g., for retrieving tasks), the parameter ?userType=processUser must be entered.

BPC WebApp Global dataIS Object has been removed successfully and cannot be accessed anymore.

In INUBIT, Keycloak can now be selected as the Process user server. This allows the INUBIT to access this identity provider directly to query the process users.

Wildcard filtration is now possible for Tasklist in BPC Portal and using REST calls.

The INUBIT product now supports Liferay 7.4 DXP/CE.

INUBIT uses a new license structure with XML signature verification.

A JMS Listener Connector can be configured via Partner Management.

Keycloak is supported as Process user server.

Content of XML repository files with different MD5 checksum can be compared between two different Process Engines.

External user management systems/identity provider are supported. For starters, Keycloak can be integrated instead of the internal user management. All user and role information is then obtained from Keycloak.

A new option in the variable mapping allows you to empty the output stream. This way required output data can be mapped in variables and emptied afterwards.

XPath 3.1 is supported.

INUBIT is now delivered with an XSLT processor only (previously there were four), namely Saxon 10 Enterprise Edition

For all Saxon 10 EE features refer to: https://www.saxonica.com/products/feature-matrix-10.xml

Authentication to the INUBIT REST API is now always carried out by default against the user management configured in INUBIT. If the authentication is to be carried out against the Process User Server configured in the INUBIT (e.g., for retrieving tasks), the parameter ?userType=processUser must be entered.

Wildcard filtration is now possible for Tasklist in BPC Portal and using REST calls.

REST endpoints are changed to match standards and to respond with JSON response.

A REST endpoint allows the deletion of libraries.

The REST endpoint healthcheck works without any authorization and authentication.

The REST API provides a new Ready endpoint. This can be used to manually set the availability of the INUBIT and thus communicate to third-party systems.