Celonis Product Documentation

When using the Celonis Platform, all events (such as augmented attribute updates, comments, and task updates) are automatically captured and recorded against rows in a data model table. You can now use the Activity history component to display these events in your new Studio Views, giving you increased visibility into your process data and strengthening your auditing options.

You can find the Activity history component in the Object-specific details group in View Edit Mode.

To learn how to add an Activity history to your new Studio View, see: Activity history.

When configuring your data connections using OAuth 2.0 for either client credentials or resource owner type, you can now choose to send the credentials using a Basic Auth Header or via the request body.

You can send the credentials using the request body by toggling the feature on when selecting your authentication method.

For more information about using the extractor builder and configuring your authentication methods, see Extractor builder.

You can now create and configure a bar and points chart in your enhanced Studio Views. With this chart type, you can compare values across different categories using two or more metrics. You can also compare metrics that have different scales by using the dual axis capability.

For more about our available chart types for your enhanced Studio Views, see: Available chart types.

And to learn how to create and configure your own charts, see: Charts.

Our new versions of the object-centric Starter Kits for the Accounts Payable, Accounts Receivable, Order Management, and Procurement processes are now built with the latest features in Studio, and take full advantage of the new Studio experience. We’ve made many upgrades to the Starter Kit content as well as to the user interfaces. Here are the highlights:

The object-centric Starter Kit versions that are built on the new Studio experience are available in the Celonis Marketplace as new packages. You won’t be able to download them as an update to your existing object-centric Starter Kit package - you’ll need to download and install them as a new installation. The new Starter Kit packages have the same names as the old packages, as they replace them, and we won’t be updating the old packages built with the legacy Studio components.

Within your Studio packages, you can now see which assets have been updated (yellow) or added (green) since the package was last published. You can also see which package assets are currently hidden.

You can also see which assets have been added, updated, or hidden when publishing the package:

When a published package asset is hidden, it isn't visible to App users. You can control asset visibility either by clicking Options - Hide / Unhide on the individual asset or by clicking Package Settings - Apps Perspective.

For more information about creating and managing Studio packages, see: Packages.

And to learn more about our available package asset types, see: Asset types.

As a full team admin, you can now set permission preferences for the variable admins in your Celonis Platform team.

The following preferences are enabled by default (and can be disabled by full team admin only when required):

When preferences are disabled, any existing users holding variable admin permissions will lose access to the relevant admin features.

For more information about variable admin permissions, see: Variable admin permissions.

In the Objects and Events user interface, you can now sort the lists of object types and event types by creation date or the date of the last edit, and in forward or reverse alphabetical order. Combine sorting with filtering by process, namespace, and metadata to quickly find the object type or event type you want to work with. For tips on exploring your objects and events, see The object-centric data model.

We’ve changed how assets are created in Process Adherence Manager (PAM). Previously, you created PAM assets using object-centric data models (also known as perspectives). From 2024-07-11, you create PAM assets based on knowledge models that are defined on top of object-centric data models. Changes you’ll notice are:

Re-creating assets involves reconstructing the target model for each asset and re-defining any preset filters. We envisage it will take less than 15 minutes to re-create each PAM asset. Find out how to re-create your assets here.

You can now make copies of a custom object type or event type, to speed up the process of modeling multiple similar objects or events. Find your original object type or event type in the list, and use the Duplicate option on the context menu (the three vertical dots) to duplicate it with a new name of your choice. The duplicate object type or event type has all the attributes of the original and all the tags that were assigned to it, and you can edit it as you want. We don't duplicate any of its relationships or its transformations. For the custom modeling instructions, see Creating custom object types and custom event types.

The PQL process function CALC_THROUGHPUT can now be used with object-centric data models. You can use the function to calculate the throughput time between events that are not directly connected to the same object type. For example, here's how to find the number of days taken between a sales order being received and its last item being shipped to a customer:

CALC_THROUGHPUT ( “o_celonis_SalesOrder”, FIRST_OCCURRENCE ["e_celonis_CreateSalesOrder"] TO LAST_OCCURRENCE ["e_celonis_CreateDeliveryItem"], DAYS ) 

For the function documentation, see CALC_THROUGHPUT.

We've fixed an issue where event logs for object-centric process mining might not be correctly ordered by timestamp for event types with long include paths. This could happen when the include path for an event (the path in the schema between an included event type and the lead object) spans at least two switches in join direction (1:N:1 or N:1:N). The issue might have occurred in any of your event logs, including autogenerated and custom event logs for perspectives, and event logs you set up outside the perspective builder using the PQL function CREATE EVENTLOG.

For affected event logs, this fix corrects the order of the events, but the results of any PQL operator that depends on the event log order might be different after the fix is rolled out in your region. The process operators such as VARIANT are the most likely to be affected but others can also have this dependency. If there's an affected event log in your data model, you'll see this warning when you work with the event log in the PQL editor for Views, or in the user interface for Studio Analysis:

CREATE_EVENTLOG: The order of <event_type> events in your event log with lead object <object_type>
changed. This order changed for <number> out of <number> lead object instance(s). Consequently,
the result of any PQL operator which depends on the event log order may have changed. 
Re-validate the results of any analysis that uses this event log. For more information,
refer to the release notes.

We’ll be applying the fix to groups of regions through this month. If you work with an event log after the end of this month and don’t see the warning, the event log isn’t affected, and you don’t need to take any action.

If you do see the warning, check where the affected event logs are used in your analysis, and re-validate the analysis, especially if important numbers and heavily-used metrics are impacted. Check components and assets such as Variant Explorer, Process Explorer, and Process Adherence Manager.