Update Notes

This pages gives an overview over update notes.

For more important notes please see: Breaking Changes or Deprecations.

The OMN Accelerator [ACC] has been further developed and the Accelerator profiles contain more preconfigured features. But there are some limitations:

For further details see What is new in OMN Accelerator 5.12.0.

OMN Core API extensions

With OMN 5.12 the Core API is extended and improved.

Glossary API:

retrieve and export/import was already available with 5.11)

DAM Asset management:

  • Get (internal process) status of one or more Assets (XR-671)

  • Linking assets to products (XR-665)

Asset Derivatives

  • Retrieve Variation types (XR-829)

  • Upload as Variation (XR-792)

PIM

create and update Products is currently limited to the Admin user role. For details see → OMN-10635

PEO

Common

  • Core EPI endpoints now support (a compact) JSON request/response body format (XR-816)

  • Exception logging improved: Exceptions handled by RestApiExceptionHandler are logged to the files now (XR-956)

  • Send Messages (to a user) (XR-603)

For details about Core API endpoints → OMN Core API

The new (html5 based) configuration client [CC] has been further developed. The most important changes/expansions are described below:

  • Workflow configuration and file system administration functions must be fully configured in the new CC and were deactivated in the old Client. File system configuration especially because of object storage (S3) support.

  • Helios file system will not be supported in the CC!

  • Special workflow FSDetails need to be configured in 5.12 in the old configuration client.

  • The new CC allows you to run configs for plugins. Importing is currently not possible in the new CC. And for certain plugins only possible in the old configuration client.

  • Change histories are only created for configurations in the new CC (cp. Changes in the old config client are not tracked in history [OUCC-584])

  • Version tab is disabled for object storage [OUCC-839]

For further details see Main Features - Configuration Client.

Since OMN 5.12 the new database versions Oracle 19 and PostgreSQl 15 (beside MSSQL) are supported.

PostgreSQL is mainly introduced as 3rd database type to save license fees (compared to other DBs) and to avoid license issues in the Cloud.

For the migration of existing Oracle or MSSQL databases to PostgreSQL we offer a migration tool → Migration to PostgreSQL 15 [OMN-9906].

For details follow the corresponding links below:

Some Postgre triggers and procedures are missing for updating table PIM2_CLASSIFICATION_PATH_NAME. (OMN-10677) Please ensure to update directly to 5.12.1, so this will not affect your PIM2.

In context of the (Camunda) workflow Engine we did several optimizations:

We updated used libraries to newer versions.

This might also influence/affect custom code. Please check whether these changes affect your custom code (if you have any).

Welcome to the AI Chat!

Write a prompt to get started...