January 2026 Release Notes

With this Private Preview release, you can now use View modules across different Studio packages.

Previously, you could only reuse modules within your own package. This new functionality gives increased flexibility by allowing View module reuse across packages. Published changes to the reused View Module can be updated as required.

For more information, see Reusing View modules across packages.

We've released an integration that allows you to pull data from LeanIX and use it within Process Designer. You can access this integration via the Celonis Marketplace.

For more information on how to set up the integration, refer to LeanIX - Celonis Process Management integration.

With this Private Preview release, you can now enable dimension switching in bar, column, line and area chart types, allowing users to dynamically adjust the data displayed.

Previously, users couldn't easily switch between visualizing data on, for example, weekly and monthly bases.

With dimension switching, users can now change the data perspective displayed using a simple dropdown in the chart.

In this example, the user can select whether to display the Sum data by Ship Mode, State or City.

To find out more, see Switching dimensions in charts.

And for more information about our private preview releases, see Feature release types.

The process for creating Process Copilots is being simplified by removing the need to specify between internal and external assets on the Create Process Copilot screen. Instead, all Process Copilots will have the option to be enabled for external use and you will be able to send both internal and external calls from the chat interface.

To make your Process Copilots externally available, you will enable the toggle switch in the new External Use section of the configuration screen to activate this asset for external API access. Once enabled, you can either copy the URL for the API or export the JSON code to use with your external tools. Any tools in this Process Copilot that are not available via API will be listed below the API URL field.

Any existing Process Copilots that were created to be external assets will be migrated to the new format automatically. All existing APIs will remain unchanged and the external API access for these assets will be enabled by default to ensure they continue to function.

For more information, see Creating Process Copilots.

The interface for the Relationships to objects tab in the Objects and Events module has been updated to provide a clearer overview of your object-to-object relationships. In this new interface, the Outgoing and Incoming tabs have been replaced with a single list that shows all your one-to-one relationships on one page.

In this new list, the positioning of the objects on the card is meant to reflect their positioning within the relationship. For example, all one-to-many relationships will display the 1-sided object on the left. For many-to-many relationships, the current object will be displayed on the left. If there is a join table in the relationship, it will be displayed between the two objects.

The list also uses the color of the chips to differentiate between the objects in the relationship. A dark chip will always be used for the current object and a light chip is displayed for the other objects. You can also click on a light chip to be taken to the page for that object.

For more information, see: Modeling objects and events.

We've made a couple of small usability enhancements to asset-to-asset dependencies in Studio.

You can now drag and drop the asset dependencies modal, giving you greater flexibility about how Studio is displayed. You can also filter dependencies by asset type.

For more information about asset-to-asset dependencies, see Asset-to-asset dependencies.

Insight Explorer is getting upgraded to use AI capabilities to detect process inefficiencies within your event logs. These AI-generated metrics can be selected from the new Metric Recommendations section on the Metrics tab of your Insight Explorer configuration, allowing you to select pre-configured metrics that don’t currently exist in your Knowledge Model. Just select an event log and AI will generate process inefficiency metrics based on the selected event log that can be added and analyzed in Insight Explorer.

To add one of the recommended metrics, click on the metric name to view the details and then click the Add to Insight Explorer button to add this metric to your configuration. Insights can then be generated to deep dive into those process inefficiencies.

For more information, see Configure Insight Explorer.

In order to reduce the perceived complexity and increase the understandability of the Multi Object Process Explorer (MOPE) graph, a number of improvements are being introduced to the process graph layout and performance, including:

The Tasks Inbox now includes Tasks triggered from Data Models (identifier-based), alongside existing record-based Task. This ensures that all tasks raised for users across Celonis Platform are accessible in one centralized location. For more information, see Inbox.

When creating or editing SQL transformation jobs, you can now use the enhanced, refreshed SQL editor by default. Previously available in our Objects and Events product area, this editor builds on the existing feature set while providing a more consistent experience across the platform.

In addition to searching existing statements, browsing tables from your data sources, and creating parameters, you can now open and work with multiple transformations at the same time:

While the enhanced SQL editor loads by default, you can also return to the previous experience by clicking Old SQL editor within a transformation:

To learn more about creating transformations, see: Extracting and transforming data.

You can now group Studio package assets by type, functionality, or custom criteria. You can also sort each group and create new asset types directly within it.

To learn more about managing your Studio package assets, see Managing packages and permissions.

With this public preview release, you can now copy your object-centric process mining (OCPM) data models (OCDM) and data pools between Celonis Platform teams using the Team-to-team copy feature. This feature also team admins to select the team to copy assets into (known as the target team), check and resolve asset dependencies, and run the copy.

When copying Objects and Events assets, the following applies:

For more information about the team-to-team copy feature, see: Team-to-team copy.

With this private preview release, admin users can now control which analysts can access and view and edit Annotation Builder and Process Copilot assets, adding an additional level of protection against unintended or negative consequences related to their use.

For more information, see Control analyst access to Annotation Builder assets and Control analyst access to Process Copilot assets.

And to learn more about our private and public preview releases, see Feature release types.

In addition to exporting a main View as a PDF, you can now export a linked View while in view mode, either in Studio or in a published app. This enhancement lets you create shareable, offline versions of your data outside the Celonis Platform. You can also select multiple tabs, add page numbers, and adjust the PDF scale and orientation.

To export your Studio View or linked View as a PDF while in view mode (in Studio or Apps), click Share - Export PDF:

To learn more about exporting your Studio Views, see: Exporting Views.

You can now quickly and easily split bar and column charts in Views across dimensions, letting you create stacked or grouped charts that adapt seamlessly to your data and provide accurate and meaningful data visualization.

Previously, creating stacked/grouped bar and column charts involved stacking/grouping multiple metrics and manually defining each stack or group in the bar or column chart individually. This required significant effort for larger data sets and was impractical when dealing with dynamic data as multiple metrics needed to be added and maintained.

This new feature lets you select which metrics are used to stack or group your data, set the ordering to ascending or descending and define how many stacks or groups are displayed (maximum of 20). You can also limit the number of data points displayed in the chart overall in the Data Settings section of the chart component which is useful when working with large data sets. In addition, you can choose the display colors for the different dimensions within each stack or group.

In this example, the bar chart displays multiple product sub-categories, with the stack length indicating the total sales for each product sub-category. Setting the Split by option to Ship Mode displays the number of items shipped by each shipping method for each product sub-category, as well as the average sales for each shipping method. Changing the colors used to display the different shipping methods aids visualization.

For more information, see Data dimensions and metrics.

We’ve replaced and upgraded the publishing workflow in Studio and Objects and Events with a new versioning and deployment system, giving you greater control over your content. Initially released in public preview, these features allow you to create and manage package and data models versions, track changes, deploy to development and production environments, and efficiently roll back to previous releases.

For a video overview of these features:

You can now use the PQL editor when creating and editing the following PQL-based Knowledge entities: Auto-generated attributes, calculated attributes, filters, and KPIs.

These improvements make working with PQL queries faster, clearer, and more powerful across the platform. They also bring the following benefits:

To learn more about creating Knowledge Models, see Knowledge Models.

And for an overview of the PQL editor, see PQL editor.

We've added a dedicated Data Labels panel that gives you flexible and granular control of data labels in charts. It also provides feature parity with the data label customization options available in Studio Analysis (maintenance mode only).

Previously, data labels could make charts in Views look cluttered and the data labels themselves could be difficult to read. With the flexibility and greater control introduced with the new Data Labels panel, you can now:

For detailed information about the settings available, see Chart data labels.

We've added a new smart input command. This lets you fetch information about the current user like their name, email address and role.

For more information, see Fetching current user information with smart inputs.

With this Private Preview release, you can now migrate bookmarked filters from Analyses to Views.

Previously, bookmarked filters used in Analyses had to be manually recreated from scratch in Views, resulting in additional work for users.

Admin and analyst users with edit permissions can now migrate bookmarked filters as required during the Analysis to View migration and select whether to migrate all bookmarked filters or shared bookmarked filters only.

Once migrated, the bookmarked filter type and owner are respected in the View and shared with the same users in the View as in the original Analysis.

For more information, see Migrating bookmarked filters to Views.

And for more information about our private preview releases, see Feature release types.

You can now define multiple dependency columns within Extractor Builder custom configurations, which enables more sophisticated data extractions from your source systems. By setting multiple columns in your dependency configuration, the Extractor Builder automatically generates placeholders for each that you can use in your endpoint configuration to reference its value. This allows you to inject multiple values into a single request for precise data retrieval tailored to more complex use cases.

Additionally, this enhancement provides the architectural flexibility required from advanced source systems and APIs that require multi-layered requests. By being able to handle multiple dependency values, platforms that require composite keys or multiple filtering parameters to access data can also now be supported. This helps ensure a more robust and scalable integration process that keeps pace with your data landscape.

For more information on custom Extractor Building configurations, see Extractor Builder.

You can now migrate your legacy Views using the new migration wizard. In addition to migrating individual View components, you can choose between a fast-track migration or a custom migration:

Legacy Views are views created using the pre–May 2024 Studio feature set (previously known as the general availability feature set). While you can still use Legacy Views in Studio, they're no longer being developed or enhanced. We therefore recommend migrating your Legacy Views to the current Views feature to take advantage of the latest updates and improvements.

To learn how to migrate your legacy Views to Views, see Migrating Legacy Views to Views.

PyCelonis has been updated to allow Machine Learning Workbench (MLWB) scripts to directly read from and write data to augmented attributes. Previously, interacting with augmented attributes required complex workarounds or was not supported directly. Changes made to data via ML/AI models are now directly and immediately reflected in frontend applications built in Celonis Studio and Views.

Data Scientists and Analysts can now build ML pipelines that directly drive operational applications. Instead of just analyzing data, their scripts can write predictions or classifications back to the data model that instantly update the Studio/Views interfaces used by business stakeholders.

Users must update their PyCelonis package to the latest version to access this capability. For more information, refer to the documentation: PyCelonis - PyCelonis.

We've made some changes to filters in Studio Views to help simplify and enhance their use.

Built-in (attribute and process) filters are now available in edit mode in addition to view and interactive modes. This lets you create and apply complex filters without writing PQL statements or switching between Studio modes. For more information, see Filtering Studio Views.

You can also now view the underlying PQL statements used to implement View filters in Edit mode. Copying and editing these PQL statements means you don't need to create your own filters from scratch. You can also save your filters to the Knowledge Model as global filters. To find out more, see Viewing and reusing filter PQL statements.

We've also made attribute filters more user friendly. You can select which attributes can be selected by business users, helping ensure only relevant options and data are displayed. For more information, see Attribute filters.

We've also improved syncing between process filters and View components. You'll get a notification if an event log is:

You can then review and edit your process filter settings if required. For more information, see Process filters.

We've also aligned container components with other components so they can be now excluded from filtering. For more information, see Containers / Conditional layouts.