What's new in Celonis Process Mining 4.7.1?

For Celonis Process Mining 4.7.1, we've focused on improved security and added some fixes for Celonis Processing Mining 4.7.

Release notes

Celonis Process Mining 4.7.1 - Release Notes.pdf

Bug fixes

Celonis Process Mining 4.7.1 - Bug Fixes.pdf

Important

You'll need to perform some steps before updating to Celonis Process Mining 4.7.1, including installing and running Celonis Process Mining 4.7. You'll find everything you need here.

Changes and improvements

Important changes

1. SAP HANA JDBC Driver

With Celonis Process Mining 4.7.1, we no longer distribute the SAP HANA JDBC driver (ngdbc.jar) with the application.

Warning

If you're currently connecting to a SAP HANA database, you'll need to follow the instructions in the Celonis Process Mining 4.7.1 - Update Guide 1.12 to deploy your SAP HANA JDBC driver. As each SAP HANA Support Stack brings its own version of the SAP HANA JDBC, this is required to ensure the full compatibility of the driver with the HANA version. If you don't do this, your SAP HANA connections will fail and your Data Models, for example, won't load.

How to deploy your own SAP HANA JDBC driver:

Get the suitable JDBC driver from your HANA Client or HANA studio installation (it can be downloaded from the SAP Marketplace). The file should be called ngdbc.jar.
Shut down the Celonis Process Mining application
Go to <installDir>/lib and paste the ngdbc.jar into the folder
Start the Celonis Process Mining Application

2. Custom writable root configuration

In the new version we slightly adapted the configuration of the filesystem.writableroot property:

The filesystem.writableroot is set to the installation directory in the installer script, and always overrides this property on upgrade. If the target or the subdirectory that points to the writableroot are manually changed, two writableroots are created during the update configuration can be lost by duplicate temporary files and Configuration Store backups. To prevent such a scenario, we've introduced a new property called filesystem.writableroot.allow_different_dir in the configuration files.

Important

For detailed information and required steps, follow the instructions in the Celonis Process Mining 4.7.1 - Update Guide.

Behavior with CPM 4.7.1

Application Startup

If writableroot does not point to the default directory and filesystem.writableroot.allow_different_dir=false, the application startup will fail.
If writableroot does not point to the default directory and filesystem.writableroot.allow_different_dir=true, the application startup will succeed with a warning.

Application Update

If writableroot does not point to the default directory and filesystem.writableroot.allow_different_dir=false, the application update will overwrite writableroot to point to the default directory. The customization has to be restored after the update.
If writableroot does not point to the default directory and filesystem.writableroot.allow_different_dir=true, the application update will preserve the custom writableroot.

CyberArk integration - Application Access Manager

With this integration, sensitive database credentials do not longer have to be entered in the Celonis frontend or the configurations files. The passwords can be retrieved from the CyberArk Secure Vault at runtime.

Find more information on the integration here and in the Celonis Process Mining 4.7.1 - Operation Guide 1.13.pdf.

Note

Requires an active and licensed CyberArk Privileged Access Security Solution .

Restriction of concurrent user sessions

With the release of this version, the amount of concurrent user sessions (authentication from different browsers/endpoints using the same credentials) can now be limited.

The setting is configured in the config-custom.properties file via the new property server.maximumSessions.

Improved bookmark concept

With Celonis Process Mining 4.7.1, we have reworked and improved the current bookmarks:

When loading a bookmark, there is now an option that allows users to choose if they only want to load selections or the whole state of the analysis
The icons were updated to ensure better visibility

Note: A bookmark saves the state of the analysis. The analysis state includes selections, variables, process explorer view, and states of components such as sorting in OLAP tables. Previously, when loading a saved bookmark, the whole analysis state was therefore reapplied. Now, users have the choice between applying the bookmark including the analysis state (default action) or only selections from the bookmark.

Improved Date Picker component

The Date Picker now has a new advanced setting that lets the Analyst decide, if the component should be filtered with selections.

Filtering the component also restricts the dates availble. If the component is not filtered with selections, all dates will still be available.

Scheduled trash bin housekeeping

We noticed that a lot of System Administrators never empty the Analysis trash bin. That can lead to various problems, including backup files constantly growing in size.

Therefore, we implemented a housekeeping mechanism to specify how long each Analysis should be preserved in the trash before being permanently deleted.

Note: The housekeeping option is disabled by default, but we strongly recommend enabling it.

Analysis draft housekeeping

To further reduce the overall footprint of the application, 4.7.1 enables you to configure housekeeping for Analysis drafts. So far, the full draft history is persisted and written to the backup files.

By inserting the three new properties in config-custom.properties and uncommenting them, you can now control:

If draft housekeeping should be enabled.
How many drafts should be kept at minimum, regardless of their age.
How long historical drafts should be preserved.

config-custom.properties

# Analysis Draft Housekeeping
# --------
# Indicates whether housekeeping is active for analysis drafts. Values other than 'false' are considered as 'true'.
# By default disabled.
# housekeeping.analysis.drafts.enabled=true

# How many drafts to be kept regardless if they are outdated or not. Must be a non-negative integer value.
# Zero means delete all historical drafts if all of them are outdated. The default value is 3.
# housekeeping.analysis.drafts.keepMin=3

# For how long historical drafts must be preserved. Must be a non-negative integer value.
# Zero means that any historical draft is eligible for immediate deletion (while respecting housekeeping.analysis.drafts.keepMin)
# The default value is 30.
# housekeeping.analysis.drafts.keepForDays=30

CPM