July 2025 Release Notes

You can now add and configure a treemap component for your Studio Views. A treemap component is a type of data visualization that displays hierarchical (tree-structured) data as a set of nested rectangles. Each branch of the hierarchy is represented by a rectangle, which is subdivided into smaller rectangles representing sub-branches or leaves.

In this example, a treemap is used to display the most frequent flight connections between German airports. The darker the color, the higher the number of connections, with MUC to CGN being the most frequently flown during the time period.

For more information, head to: Treemap.

In addition to manually exporting your Views as PDFs, you can now schedule automated emails to be sent with the View report PDFs attached. These emails can be sent on a daily, weekly, or monthly basis, with the ability to customize the email and the PDF settings for each report.

You can schedule your Studio View reports within a View by clicking Share or export View - Schedule reports:

Once scheduled, your Studio View reports can be edited, permanently deleted, and activated / deactivated depending on its status:

For more information about scheduling View reports, see: View Reports.

We've created a visual event log builder for you to construct event logs for object-centric process mining perspectives. You don't need to write PQL statements - just choose a lead object and the events you want to include. You'll immediately get a visual preview of your event log, with an event log table, an edge table for connections, and a graph preview.

For more information, see: Event logs (object-centric).

You can now migrate your Analysis assets to Studio Views, allowing you to create dashboards and reports using our enhanced View editing experience. This includes both step-by-step (load scripts, saved formulas, variables, etc.) and full sheet migration options.

Celonis continues to maintain Analysis (by fixing bugs and ensuring that performance remains strong) but no further feature development will take place. As such, we recommend you migrate your Analysis assets to Studio Views.

For an overview of your migration options, see: Migrating Analysis to Views

You can now migrate select Legacy View components to your Views, allowing you to add and further configure the components using the latest View editor and features.

While in Legacy View edit mode, hovering over a supported component allows you to copy that component (and its configurations) and then paste it into a Studio View. This migration works best when copying between Legacy Views and Views that use the same Knowledge Model, removing the need for you to reconfigure the data.

To view the full list of supported components and an overview of current limitations, see: Migrating Legacy View components to Views.

The new PI Graph Versioning functionality allows you to manage your releases more effectively and improve the collaboration between different teams within the Celonis Platform. Versioning will provide greater control over your object-centric data model changes by allowing version creation, tracking, and targeted deployment all from within the Objects & Events module. From the Versions screen, you will also be able to track and manage changes between versions and rollback changes that have been released to production to a previous version.

This new Versioning functionality provides you with:

You can now add horizontal and vertical dividers to your Studio Views, allowing you to visually separate sections and improve your content hierarchy within your View.

In this example, horizontal dividers have been used to visually separate different View components:

To learn more about creating Views, see: Views.

You can now add a pivot table to your Studio Views, allowing you to summarize, analyze, and present large datasets without altering the original data.

In this example, a pivot table is used to display customer sales information based on regions. Each cell represents the average sales per customer in that region, with their customer and region subtotals displayed. Any cells with a positive value are then colored, making the table easier to read.

To learn more about pivot tables, see: Pivot table.

Any filters you set in a View can now also be copied into other Views within your Celonis Platform team, saving you from manually configuring them each time. Copied filters are saved on a clipboard for 10 minutes, with a prompt for you to apply the filter when you open subsequent Views.

To learn more about copying filters between Studio Views, see: Copying filters between Views.

As an alternative to importing a complete object type from a table in your source data, you can now use a source system table to extend a custom object type that you've started to model. If you're modeling iteratively, this is a good way to complete your initial objects after validating them with stakeholders.

You can select columns from the table to become attributes of the custom object type, and you can map columns to attributes that you already modeled. If you didn't create transformations yet for the object type, a SQL transformation script will be generated automatically that populates the attributes you imported or mapped. You can repeat the process with other source system tables to add more attributes to the object type, though the transformation script will only be generated once. For more information, see Importing object types and relationships from source data.

Celonis now performs automated scans to check your Knowledge Models for potential issues such as missing descriptions, schema changes, duplicate entries, outdated attributes, and other problems that could confuse the Large Language Models used in your AI tools such as Process Copilot. Resolving these issues will prevent your AI tools from analyzing inconsistent or incomplete data which can impact the quality of your outputs. Properly configuring your data will improve the accuracy of your responses and provide more reliable results.

The findings from these scans are displayed in the Knowledge Input section of the Process Copilot configuration screen. Each impacted knowledge item is displayed as a separate line with a description of the problem and a link to access the impacted item directly in the Knowledge Model. Hover over the warning or error icon in the Issues column to see the cause of the problem and then select the Click to edit link to open this knowledge item in the Knowledge Model.

For more information, see Knowledge Input in Process Copilots.

You can now rename the target table in the Celonis Platform when extracting data from a cloud based source system such as SAP Ariba, Salesforce, and Oracle Fusion Cloud.

When creating extraction tasks, select Rename name target in the Table Configuration settings and then specify the table name:

For more information about connecting to cloud based source systems, see: Cloud based data sources.

And for information about creating extraction tasks, see: Creating extraction tasks using the visual editor.

We've enhanced the text field inputs in Studio Views to suggest variables, translations, and JavaScript when inside the “${}“ syntax. When typing in supported text fields, smart inputs give you auto complete suggestions from existing queries in your package. You can then click on the suggestion or use the arrow keys and hit Enter to add it to your expression.

For example, a smart input is used in the tab name to display the current date:

This is configured using the following smart input:

${new Date().toDateString()}

For a video overview of smart inputs in Views:

Smart inputs are enabled for the following Studio features: Button label, Button variant, Color Mapping (View Components), component information, filter dropdown label, input box label, input dropdown label, tab Container, tab name, and View name.

For more information smart inputs, see: Smart inputs.

Process Explorer and Variant Explorer are being upgraded with the ability to add custom coloring to the activity and event nodes in the process graph. This new feature allows users to design and select custom color schemes that can be applied to the nodes in their process graph. For example, users can choose to color specific events or activities based on the department responsible or they can color any nodes they want to monitor in red as an alert. In the examples below, the nodes for the “happy path” have been set as green.

Case-centric Process Explorer	Multi-object Process Explorer

These custom color options can be applied in edit mode by selecting a mapping from the Coloring section on the Settings tab. The color mapping can be removed for the component by clicking the Reset to default link and restoring the default colors to each node.

To create a new mapping, click Add in the Event Coloring section and then use the Add Visual mapping window to assign colors to the relevant events or activities. Select an event or activity from the Categories dropdown and then click the colored square to the left to choose which color to assign to that node. Click the Add link to select more events or activities to assign colors to and then click Save when finished.

For more information, see Color mapping event nodes.

A new version of the Payment Terms Harmonizer app is available. This release includes the new Value Tracking view, located in the Value Journey folder, which enhances value framing. For more information, refer to:

We've added a new user interface that lets you group user activities captured in Task Mining and add business context to create semantically-meaningful Business Events. Adding these Business Events to process graphs provides clearer and more granular process visualizations, without overwhelming 'click-level' detail or writing complex SQL queries.

For more information, see Business Events.