April 2026 Release Notes

You can now add and configure a Performance Spectrum component for your Studio Views.

Previously available as a public preview, the Performance Spectrum adds a time-based perspective to your Views, revealing how tasks interact and evolve. It highlights variations, bottlenecks, and performance shifts that are often hidden in aggregations, giving you clearer insights into how your processes truly run.

In this example, the Performance Spectrum helps a government agency to visualize how individual fines move through a defined sequence over time. This helps them to identify bottlenecks and validate that specific process patterns (like batching) are adhered to and stay consistent over time (e.g. throughout the year).

To learn more about the Performance Spectrum, see: Performance Spectrum.

You can now configure an Instance Explorer component for your object-centric data in your Studio Views. The component, previously in public preview, lets you explore individual object instances, like Orders, Invoices, or Flights, and their events within the digital twin. You can see each object’s lifecycle and relationships without creating custom queries or tables.

The key features include:

The Instance Explorer component can be viewed using a graph or list view, with an example of the graph view displayed here:

To learn more about configuring and using the Instance Explorer component, see: Instance Explorer.

With this private preview release, you can now configure button components in Views to display a message when a user clicks a button.

You can add standard text formatting and URLs to the message text. The message text is accessible for screen readers and can be copied and pasted by the user.

In this example, a message has been added to the Read this button:

When the user clicks the Read this button, the message displays in the View:

For more information about buttons in Views, see Buttons.

And to read more about our private preview releases, see Feature release types.

We've extended Data Model name mapping to Knowledge Models so user language preferences are automatically applied in Views, for example when migrating Analyses to Views.

Previously, when an Analysis was migrated to a View, translations based on user language preferences were not available. This led to a poor user experience as the table and column names displayed in the View were potentially different from those in the original Analysis.

By extending support for name mapping, table and column names now automatically display in the default language selected by the user in the Studio package settings. This applies to all Views, including Views that were migrated from Analyses.

For more information, see Migrating translations from an Analysis to a View and Managing package settings.

And to read more about our public preview releases, see Feature release types.

We've added a Process Explorer preview to the Event Log builder. This allows you to visualize your process model in real-time during configuration, ensuring accuracy between the data model and the intended process flow. The preview includes auto-refresh capabilities and supports the visualization of dynamic events.

Previously, you had to save the Event Log and navigate to a separate View to verify your process flow. Now, you can spot mapping errors, like inverted timestamps or incorrect activity naming, instantly without leaving the builder.

To learn more about creating and configuring event logs, see: Event logs (object-centric).

The Agent Tools (MCP) asset is being upgraded with new tools that allow AI agents to interact with a process running in Orchestration Engine. These new tools are available in Studio and can be configured as part of your Process Copilots. These tools are configured for Process Copilots using the Tool Activation feature and can be either manually fixed by users or defined by the Agents at runtime.

These new tools include:

For more information, see Tool Activation.

We're adding Authorization Code as a new OAuth 2.0 grant type you can select when registering a new OAuth 2.0 clients in Celonis Platform. Authorization Code is a secure, server-side process for applications to obtain access tokens to authorized user data without exposing credentials.

For more information, see Registering your OAuth client in the Celonis Platform.

We've changed how enhanced variables in View input dropdowns update to better reflect behavior expected by users.

Enhanced variables in View input components let you centrally create and manage information that is referenced and reused across Studio components and assets.

Previously, an input dropdown using enhanced variables always displayed the last value selected, even if the value of the enhanced variable had been changed elsewhere in the app. This could lead to mismatches between the enhanced variable value displayed in the input dropdown and the actual value of the enhanced variable.

With this change, the input dropdown will now always display the current enhanced variable value. If the current enhanced variable value is not available as an option in the input dropdown, an information message will display in both the app and in Studio, indicating that the enhanced variable value has been inherited from elsewhere.

For more information about enhanced variables, see Using enhanced variables in Studio components.

We've extended visual mapping rules for colors and icons to the KPI card and Attribute list components in Views.

Previously, changing the colors used and creating and using visual icons wasn't supported for these components.

Extending this functionality to these components gives added flexibility around their use while providing a more consistent visual experience across Views.

In this example, a Primary Scale visual mapping has been selected for a KPI card and an up chevron icon added to the left of the KPI value.

For more information, see Managing Studio and component color themes and Icon mapping.

Users can now choose between using the strict or balanced model miner when mining a model. Both miner types analyze the process graph that is created from an event log and try to match the patterns of events within the process graph. They use different approaches where patterns of events can’t be matched. The strict miner takes into account every single variant in a model. In contrast, the balanced miner optimizes models for fitness, which can help when mining a model with many variants.

For more information, see Model miner types.

The Adherence Explorer is the new analysis experience for PAM. It's a Studio View component that enables users to analyze deviations in the context of a broader analysis (such as building a dashboard with the conformance rate of a model). It seamlessly interacts with other View components, including charts, tables and Process Explorer.

For more information, see Adherence Explorer.

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

For more information, see the documentation for Annotation Builder, Insight Explorer, and Control analyst access to Process Copilot assets.

Starting April 2026, upgrading to the latest on-prem JDBC JAR will require Java 25. This is not a breaking change, as customers who do not update their extractor to the latest JDBC version will not be affected. We will update this page with the exact release version once it is finalized. No immediate action is required, but upgrades should be planned in advance.

To learn more about the on-prem JDBC extractor, see: JDBC Extractor.