Product Updates

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.

Inventory Management Planning Parameter Optimization app (object-centric) version 2.0 (2024-06-04) We’ve renamed the object-centric Inventory Management Master Data Improvement app to the Inventory Management Planning Parameter Optimization app, and refactored the app’s Knowledge Model to revise the KPI IDs and records. The new version 2.0 is compatible with the Knowledge Models for the Material Allocation app and the Supply Chain Network Visibility app. The case-centric version of the app keeps the old name. The Inventory Management Planning Parameter Optimization app enables planners to identify materials with overstated or understated lead times, safety stock, or reorder points based on their consumption and replenishment patterns. The app provides recommendations and action flows to enable material planners and supply chain analysts to easily correct parameters in the source system. With this version of the app, we’ve added intelligent lead time parameter recommendations based on Machine Learning. Machine Learning assists you to remove bias from parameter recommendations, and returns a lead time closer to what your supplier is capable of, instead of being biased by occurrences such as purchase orders placed either at short notice or too much in advance. If you already have the Inventory Management Planning Parameter Optimization app installed, when you update to version 2.0 from version 1.5 or earlier, you’ll need to reapply any customizations you made to the KPIs in the Knowledge Model. Updating the object-centric Inventory Management Planning Parameter Optimization app has details of the changes we made, and instructions to upgrade your app. You can do this whenever you’re ready.

Supply Chain Network Visibility app (object-centric) version 1.0.0 (2024-06-04) We’ve renamed and extended our End-To-End Lead Times app to create the Supply Chain Network Visibility app. This object-centric app for Inventory Management identifies opportunities to reduce excess inventory and exceed service levels across your organization’s end-to-end supply chain network. You can use its views to visualize the upstream and downstream impact of materials on key performance indicators like supplier reliability and service levels, unlocking strategic, long-term opportunities to optimize your supply chain network. For the Supply Chain Network Visibility app, we’ve added:A value assessment dashboard to provide insights and recommend targeted actions to reduce excess and obsolete inventory, prevent excess replenishment, and improve service levels.A downstream network perspective for you to analyze the impact of raw materials on the downstream supply chain network, and their effects on the creation and delivery of finished goods and potential root causes like extended production lead times.Inventory projection to give you visibility into forward-looking KPIs like uncovered demand, excess supply, and days until stockout.A management dashboard to surface procurement, production, sales, and inventory metrics in an aggregated, accessible manner.The Supply Chain Network Visibility app is a premium app and requires an additional licensing fee. Talk to your Celonis account team to arrange this. For the app documentation, see Supply Chain Network Visibility app - object-centric.

Multi-sliders in Process Explorer (2024-05-29) The slider controls in Process Explorer use two multi-sliders to explore the events of individual objects and connections within your process. In these multi-sliders, each object or connection appears as a different slider and is color coded to match the objects in the process graph. For more information on using multi-sliders, see Multi-object Process Explorer. Moving a slider up will add the next most common event or connection for that specific object, while sliding down removes the least frequent event or connection that is currently displayed for that object. For example, you can adjust the slider for one object upwards to add the next most frequent event for that object to the graph while the remaining objects are not changed. However, if the event being added does not connect to the events currently displayed for this object, additional events will be added to connect the event being added. If the event being added is shared with other objects, it is only added for the object corresponding to the slider you adjusted. However, for the other objects, this event will display empty circles to indicate that it is not included. If a slider has been used to explore the current process, the colored square corresponding to that object will be highlighted with a blue border, even if the multi-slider is collapsed (see the middle object in the screenshot below). This indicates that events or connections have been added to the process flow currently shown.

JDBC Extractor version 2.97.1 (2024-05-29) Type casting between integer and float data types with Oracle databases With this version of the extractor, you can now configure type casting between Integer and Float data types when setting up your Oracle extraction tasks. To learn how to connect to JDBC databases, see: Connecting to a database. And for an overview of supported databases and their features (including Oracle), see: Supported database connections.