Product Updates

Set variable admin permission preferences in Admin & Settings (2024-07-18) As a full team admin, you can now set permission preferences for the variable admins in your Celonis Platform team. These preferences are enabled by default: CSV downloads of audit logs, user groups, user login histories, and user permissions.Inviting users, creating groups, and creating application keys.Only a full team admin can disable preferences. 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.

Sort the lists of objects and events in your object-centric data model (2024-07-12) 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. 

Re-creation of current Process Adherence Manager assets required (2024-07-11) 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: PAM assets are consistent with Studio assets, including in Process Explorer in Views.Object types have been replaced by event logs so you’ll no longer see discrepancies with event logs used elsewhere in the Celonis Platform.More flexible modeling and analysis as event logs in object-centric data models use the PQL CREATE_EVENTLOG function.Global filters defined in knowledge models are automatically applied to PAM assets.We've removed charts and tables and Event-Object relation and Event property filters. ImportantAny PAM assets created before 2024-07-11 are available from 2024-07-11 as read-only assets only. After 2024-09-11, they’ll be irretrievably removed. To continue using them, you’ll need to re-create any PAM assets created before 2024-07-11 between 2024-07-11 and 2024-09-11. 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.

Duplicate custom object types and event types in your object-centric data model (2024-07-08) 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.

Calculate throughput time for object-centric data (2024-07-07) 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. 

Object-centric process mining: Possible changes to analysis results that depend on event log order (2024-07-06) 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.

Are you using an old version of the JDBC Extractor? (June 2024) From now on, we’ll only be providing fixes for the most recent version of the on-premise JDBC extractor. If you're running a JDBC extractor that's not the most recent version, and you raise a support ticket, we'll check whether the bug or issue still exists in the most recent version. If it does, we’ll fix it in that version. In any case, you'll need to upgrade to the most recent version to get the fix. Older versions of the JDBC extractor won't stop working - you can carry on using them until you need support, at which time you'll need to upgrade to get the bug fixes. We recommend you update the JDBC Extractor at least every quarter, even if you don't experience any issues, to get the latest capabilities and any fixes for security vulnerabilities. Updating the on-premise JDBC extractor tells you how to find the version numbers for the most recent version and your current version of the JDBC Extractor.

Find object-centric data model transformations with overwrites (2024-06-27) We’ve added a filter to the list of transformations so you can easily pick out Celonis-supplied transformations where you’ve made overwrites. An overwrite is a custom script that you create to replace part or all of the supplied Celonis transformation script for a Celonis catalog object type or event type. If you filter on transformations with overwrites, we’ll include both partially overwritten or completely overwritten Celonis-supplied transformations. You can find the Overwritten filter before the list of transformations in the Transformations page of the Objects and Events user interface. For the instructions to create custom transformations and to overwrite a Celonis script, see Creating custom transformations.

Reauthorize Google OAuth credentials for your Action Flows (2024-06-26) Action Flows using Google modules to handle OAuth 2.0 credentials provide enhanced security and compliance. To take advantage of this feature, existing Actions Flows that use Google connections must be updated to reauthorize your credentials. If your Celonis Platform is hosted in one of the realms listed below and you are currently leveraging an OAuth connection in your Actions Flows’ Google modules, then your connections will be affected. Impacted realms:Europe: bnpp, eu-1, eu-3, training, tryNorth America: ca-1, us-1, us-2, us-3 If you do not reauthorize your credentials, then your Action Flows which are using these connections will fail and you will receive an error notification email showing exactly which Action Flow is failing. To restore your connection, follow the steps provided here: Reauthorize Google OAuth credentials. 

JDBC Extractor version 2.99.0 (2024-06-19) With this latest release, we've added the capability for on-premise extractors to increase parallel executions up to 40 through local configurations. For more information about this, see: Configuring an on-premise extractor. The 2.99.0 release also includes the following upgrades and fixes:We've upgraded the Google BigQuery driver to the latest version (1.5.4.1008).We've fixed struct columns parsing in Oracle tables after an Oracle JDBC driver upgrade. For more information about installing and updating the on-premise JDBC extractor, see: Updating the on-premise JDBC extractor.

Object Link enabled for all object-centric process mining teams (2024-06-19) In teams where you have a license for object-centric process mining, we now enable Object Link by default - you don’t have to raise a support ticket. Object Link is available in the data model editor in your data pools, and you can use it to model graph structures and recursive links in your data. For the documentation, see Object Link.

Introduction of 200MB query limit for Knowledge Models in Studio (2024-06-19) We'll be introducing a capped response sizes of 200MB for queries sent through Knowledge Models (thus all queries made by Views) to ensure stable operations for all users. In the very rare case of sending a query that returns more than 200MB of data, you'll receive an error and no result will be displayed. To resolve this, you need to change the query to narrow down the result to fewer rows or columns. For further support with your queries, head to Celopeers.

Variant Explorer added to Studio Views (2024-06-19) The Variant Explorer is being added to Studio Views, allowing you to see the most common variants from your standard processes. The Variant Explorer will initially show the 10 most commonly occurring variants, how often they are happening and the average throughput time for each. You can also choose to view the variants outside of the top 10.  You can select how many variants you want to view to update your process graph and see how they impact your process flow. Once variants have been selected, you can select nodes and edges in the process graph to filter the view further for those specific variants. For more information, see Variant Explorer.

New Studio UI is replacing the legacy one (2024-06-17) We’ve given Studio and apps UI a new look. You can learn more about specific changes we've made in our release notes. To give you time to adjust, until June 17th, you can switch between your current Studio look and the new one. After that date, the enhanced Studio UI will be enabled on all instances by default and the legacy version will no longer be supported. If you're already using our enhanced Studio, we'd love to hear your thoughts. Drop us a comment.

Support for special characters and language-specific characters in object-centric data model transformations (2024-06-14) We’ve fixed an issue with our process for creating complete transformations from your scripts. Previously, if you used special characters and language-specific characters in your custom transformations and overwrites, the expanded transformation was marked with an incorrect character encoding which didn’t work. You can now go ahead and use special characters and language-specific characters in the SQL editor for transformation scripts, and we’ll support these in the transformations we create from them. Creating custom transformations has the instructions to write custom transformations.

Automatic synchronization of data connections between data pools in Data Integration (Limited Availability) (2024-06-13) In addition to manually synchronizing your data connections between data pools, you can now activate an automatic sync. This reacts to any changes in your main data connection, replicating those changes to data connections imported into other data pools. This feature is currently in limited availability but will be enabled for all teams in the coming weeks. For more information about sharing data between your data pools, see: Sharing data between data pools. 

Deletion is now in the context menu for object types and event types (2024-06-13) Instead of a Delete button on the details page for an object type or event type, you now delete them from the list, using the Delete option in the context menu (the three vertical dots next to the object type or event type’s name in the list.) We’ve moved the function because you shouldn’t need to delete an object type or event type very often. For the documentation, see Creating custom object types and custom event types.

POST requests in extractor builder in Data Integration (2024-06-12) In addition to GET requests, you can now configure POST requests when creating a custom extractor builder connection. This allows HTTP POST requests to be sent between your source system and the Celonis Platform. When selected, an additional BODY field is visible, allowing you to select between two HTTP standards:x-www-form-urlencoded (default): This enables you to select key-value pairs.Plain text: This provides you with a free text box to add your body in plain / raw format.For more information, see: Extractor builder endpoints.

Custom header support for OAuth 2.0 authentication in Data Integration (2024-06-12) You can now add custom headers to your OAuth 2.0 authentication requests when creating a connection between the Celonis Platform and your source system. By enabling this for your connection, you can add key-value pairs of headers to your authentication requests. When creating or customizing a data connection, select an OAuth authentication method and then enable Add custom header:For more information about creating connections between your source systems and the Celonis Platform, see: Extractor builder.For authentication methods, see: Extractor builder authentication methods.

Extractor builder error handling in Data Integration (2024-06-12) When creating or editing your extractor builder error handling rules, you can now toggle on the ability to stop the extraction task and mark it as successful when a rule is matched. For example, when the Http Status equals 204 then this extraction task will be stopped and marked as successful in the logs.For more information, see: Extractor builder endpoints.

Enhancements to chart component in Studio (2024-06-11) We've made a number of enhancements to our chart component in Studio, improving the look and feel of your new Views. These updates include:Additional colors: Adding to blue, gray, and green, you can now also select from semantic colors: red, green, orange, and a transparent color option. Revert axis title: You can now revert your axis titles back to their default labels.Alternative chart types: Improved messaging when alternative chart types are better suited to the data you've selected. Display options for annotation lines: You can now select between name, value, or both for your chart annotation lines. Sorting categorical column charts: You can now sort categorical column charts, choosing between ascending or descending orders. For more information about creating and configuring the chart component, see: Charts.

Last Edited By and Last Edit columns in Data Integration (2024-06-11) We’ve added an additional column for each of the main components in Data Integration indicating the person that last edited this component and when the last edit has been made. For example when a user adjusts a transformation script or a data model, the change will be reflected in those two columns: For more information about integrating your data into the Celonis Platform, see Data Integration.

JDBC Extractor version 2.98.5 (2024-06-10) With the latest version of the JDBC extractor, we've added support for materialized views and snapshots when connecting to Google BigQuery. For more information about connecting to your Google BigQuery account, see Google BigQuery. This version of the JDBC extractor also includes the following fixes:Retry file upload on receiving HTTP status code 408 to overcome temporary CloudFlare issue.Optimized the way file upload works to improve performance and avoid connection timeout issues.Upgraded Snowflake JDBC driver to version 3.16.1 to fix issues with nested paths on Windows machines.Upgraded several third party libraries to fix vulnerabilities.For more information, see Connecting to a database.

See transformation status in the Objects and Events UI  (2024-06-07) You can now see and troubleshoot any issues with running your transformations while you're working in the Objects and Events interface, rather than the underlying data pool. In the Transformations tab for an object type or event type, we now show you the status of the base transformations (running, successful, canceled, failed) from the last time a data job was run. (If you haven't run a data model load yet, you'll see the status “Not executed”.) There's also a link for each type of transformation (Base, Change, Extension, Extension_Change) to take you to where the transformation task appears in the logs for the data job. Running transformations has the instructions to run transformations.

Duplicate Invoice Checker (object-centric) version 0.1.0 (2024-06-05) The object-centric version of our Duplicate Invoice Checker app for Accounts Payable is now powered by an AI Annotation. The AI Annotation with out-of-the-box search patterns provides a stable and scalable backend, powering the duplicate checking algorithm. The AI Annotation replaces both the Machine Learning Sensor and the Knowledge Model search pattern customization that are used in the case-centric version of the app. You can easily filter your invoices and configure and customize checking with the UI - no PQL or YAML coding is required. To get the object-centric Duplicate Invoice Checker app, look on the Celonis Marketplace, and to find out more from the documentation, see Duplicate Invoice Checker - object-centric.