You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 18 Next »

With Celonis Process Mining 4.7.2, we are focussing on stability and bug fixes

Please find the official release note presentation as well as the bug fixes attached. Additionally, this article features a technical overview of the newly introduced features below.



Release Notes

Bug fixes



Updating to Celonis Process Mining 4.7.3

Please be aware that before updating to Celonis Process Mining 4.7.3, it is required to install and run version 4.7.2. 

For detailed information and further required steps, please refer to the Celonis 4.7.3 - Update Guide 1.14. All updated guides can be found here.

Not adhering to these instructions can lead to loss of configuration! These steps are not necessary in case of a fresh installation. Only application updates are affected.



Changes & Improvements




Important Changes

1. Deprecation note: Optimized load

With Celonis Process Mining 4.7.3, we are deprecating parts of the “optimized load” functionality (Data Model → Loading → Load column).

Remaining functionality:

The user can manually select which columns of a certain table are included/excluded from a data model load.

Deprecated functionality:

  • The application no longer tracks the access count and last access dates for columns
  • The “Load only used columns” functionality is no longer available. This functionality was used to automatically include columns that were not available but accessed by a user into the next load
PreviousNew




2. MS SQL Configuration Store - JDBC Driver

In case the application is configured to use the Celonis Configuration Store based on MS SQL in config-custom.properties, a manual  update has to be applied:

Validating the usage of MS SQL

  • Navigate to <installDir>/config-custom.properties
  • Check if this exact property exists within your config-custom.properties file. In case the property is commented (#) the manual update does not have to be applied:
database.dialect=org.hibernate.dialect.SQLServer2008Dialect

For detailed information and further required steps, please refer to the Celonis 4.7.2 - Update Guide 1.13. Not following this instruction will lead to all Amazon Athena connections failing

Updating the property

  1. Navigate to <installDir>/config-custom.properties
  2. Replace the old value org.hibernate.dialect.SQLServer2008Dialect of the property database.dialect with the following value:
de.celonis.pm.utils.engine.CPMSQLServer2012Dialect


3. Microsoft JDBC Driver for SQL Server Authentication Library for Windows


3. Microsoft JDBC Driver for SQL Server Authentication Library for Windows

We also removed the mssql-jdbc_auth-<version>.x<64/86>.dll (Microsoft JDBC Driver for SQL Server Authentication Library for Windows) from the embedded dependencies. In case the application is running on Windows and the SQL Server Authentication (indicated by integratedSecurity=true in the JDBC string) is used to connect to the Celonis Configuration Store or the Analytics Database, the library has to be deployed manually.

Please refer to the Celonis Update Guide 1.14 for more information. Not applying this configuration can lead to MS SQL connections failing.

Deploying the driver

  1. Stop the application
  2. Download the respective driver version based on your SQL Server version and compatibility from here. Please follow the Microsoft recommendations in case of any questions: here.
  3. Place the library in <installDir>\jre\bin
  4. Start the application




4. Updated log file structure & log rotation

With version 4.7.3, we revamped the full log file structure on the application server. In addition to that, we enabled log rotation by default for the main Celonis Frontend and Compute Compute service logs.

Please refer to the Celonis Update Guide 1.14 for more information.

WindowsLinux

Celonis CPM4 Frontend

    • <installation_directory>/logs/cpm_svc.err.log
      <installation_directory>/logs/cpm_svc.out.log
      <installation_directory>/logs/cpm_svc.wrapper.log
      Windows Service Wrapper logs (when starting Celonis CPM4 Frontend service)
    • <installDir>/logs/cpm-stdout.log
      Celonis CPM4 Frontend startup messages (before full application server start)
    • <installation_directory>/logs/cpm.log
      Celonis CPM4 Frontend general service log file for current date (today’s logs)
    • <installation_directory>/logs/cpm.<date>.log.gz
      Celonis CPM4 Frontend archive service log files, rotated daily by default

Celonis CPM4 Compute

    • <installation_directory>/compute/logs/cpm_svc.err.log
      <installation_directory>/compute/logs/cpm_svc.out.log
      <installation_directory>/compute/logs/cpm_svc.wrapper.log
      Windows Service Wrapper logs (when starting Celonis CPM4 compute service)
    • <installDir>/compute/logs/compute-stdout.log
      Celonis CPM4 compute startup messages (before full compute server loading)
    • <installation_directory>/compute/logs/compute.log
      Celonis CPM4 compute general service log file for current date (today’s logs)
    • <installation_directory>/compute/logs/compute.<date>.log.gz
      Celonis CPM4 compute archive service log files, rotated daily by default

Celonis CPM4 Frontend

    • <installDir>/logs/cpm-stdout.log
      Celonis CPM4 Frontend startup messages (before full application server loading)
    • <installDir>/logs/cpm.log
      Celonis CPM4 Frontend general service log file for current date (today’s logs)
    • <installation_directory>/logs/cpm.<date>.log.gz
      Celonis CPM4 Frontend archive service log files rotated, daily by default

Celonis CPM4 Compute

    • <installDir>/compute/logs/compute-stdout.log
      Celonis CPM4 compute startup messages (before full compute server loading)
    • <installation_directory>/compute/logs/compute.log
      Celonis CPM4 compute general service log file for current date (today’s logs)
    • <installation_directory>/compute/logs/compute.<date>.log.gz
      Celonis CPM4 compute archive service log files rotated, daily by default




5. Custom logging configuration

The custom logging configuration was updated with version 4.7.3. It was previously configured in  <installDir>config-custom.properties via the property logging.config=. This property is no longer supported. 

Please refer to the Celonis Update Guide 1.14 for more information. Not applying this update will lead to the application not picking up the previous custom logging configuration.

Applying custom logging configuration

  • Refer a custom logging config file using the JVM property -Dlogging.config in <installDir>/cpm.user.vmoptions
  • Refer a custom logging configuration in the file application.properties#logging.config residing in the same directory as the application jar.

Note

The logging library was changed from log4j2 to logback. Therefore, an update to the  logging.xml configuration format could be required. For more information, please refer to: https://logback.qos.ch/manual/configuration.html




Improved Conformance Checker

1. Custom dimension

The Conformance Checker component can now be configured to use a custom dimension in two places (requires being in edit mode):

  • During the setup when selecting “mine process model”
  • In the component settings


2. Improved violation list

The violation list is now paginated for better usability and performance.

Additionally, violations can now be added to the allowlist directly, without opening the detail screen.

1.

2.





  • No labels