2026 Release Notes

You can now filter and bookmark our release notes to quickly locate specific updates. The filtering panel gives you the following options:

You can clear individual filter categories using the All / None toggles, or clear all active filters at once using the Reset All button.

To learn more about our Celonis Platform release types, see: Feature release types.

We've added additional context to help you resolve validation errors when changing the Data Model used by a Knowledge Model.

Validation checks are run to ensure the Knowledge Model will still work correctly with the new Data Model.

Previously, if the validation checks failed, a single, generic error message displayed and the Data Model change was automatically blocked.

Now, more detailed error messages display in a scrollable list, allowing you to review and resolve the generated validation errors. You can also change the Data Model even where validation errors occur, allowing you to fix the errors later on.

To better control your automations, you can now define a limit on how many items a Data Model Trigger can handle. Whenever that limit is reached, depending on your settings, new items discovered in the Data Model are either ignored or they replace the low-priority items.

For more information, see Creating Triggers using Data Model.

We've made some changes to the Knowledge sidebar in the PQL editor to make it easier to work with the aggregation selector. We've also changed the edit button location for filters and variables in the PQL editor Knowledge sidebar to improve alignment with other entities.

Row-click action removed

Previously, clicking anywhere in an entity row in the Knowledge sidebar automatically added the entity's PQL expression to the currently-selected table column:

Now, you use the new insert button to add the PQL expression to a table column:

Metadata popover action changed

Previously, you accessed metadata popovers for an entity by clicking the info button:

Metadata popovers now appear automatically when you hover over an entity:

Edit buttons relocated for filters and variables

Previously, you edited filters and variables in the Knowledge sidebar using an inline edit button. This button has been removed and an edit button added instead to the metadata popover.

All other functionality and logic are unchanged.

For more information about the PQL editor, see PQL editor.

We’ve made the following usability improvements to the Process Explorer component in Studio:

For more information, see Show / Hide events in PE.

When you create a new version of a Studio package, you can now see exactly what's changed using two new tabs in the Create Version screen:

The Create Version screen also displays information about the versions being compared:

You can also view the exact changes between these versions by selecting changed in the Create Version screen:

For more information, see Versioning and deploying packages.

You can now securely and efficiently share process intelligence data from your Celonis Data Pools with external platforms in your data ecosystem using Outbound Data Sharing. This connection leverages the Delta Sharing open standard to transform Celonis into your organization’s central Intelligence Layer, providing third-party tools like Databricks with seamless access to process-contextualized data.

Optimized for the Object-Centric Process Mining (OCPM) framework, Outbound Data Sharing allows you to export your Object and Event tables to maintain semantic integrity across your entire data stack. By sharing these business-ready outputs, you can now power cross-platform use cases and advanced analytics. This ensures your process context remains consistent and actionable outside of the Celonis environment.

For more information, see Outbound Data Sharing.

To learn more about our private preview release, see: Feature release types.

The Celonis Assistant is an AI support assistant that offers a conversational chat interface to help configure your Celonis implementation in real-time. It is context-aware and has access to public documentation of the platform and latest product guidance. This assistant can provide suggestions on which Celonis products to use, suggest use cases and KPIs to analyze within your data, provide implementation guidance, and more.

As you begin your Celonis implementation, the Celonis Assistant offers guidance on how to get started, provides best practices for your configuration, and helps to troubleshoot any errors. As you prioritize which use cases you want to improve, the Celonis Assistant can identify prebuilt solutions that meet your needs or guide you as you build custom solutions on the Celonis Platform.

To use the Celonis Assistant, you will need to enable AI Settings and Azure OpenAI models for your team. The Celonis Assistant can then be accessed from the main Celonis menu by clicking the “Celonis Assistant” option.

For more information, see Celonis Assistant.Celonis Assistant

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

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.

We've made some changes so event log colors are now consistent across all Process Mining components and assets.

When a color is assigned to an event log in the Event Log Builder or visual editor, that color is now be used for that event log in all your Process Mining components, such as Process Explorer, Variant Explorer, Process Adherence Manager (PAM), Event Explorer, Case Explorer and Throughput Time (TPT) Explorer, as well as in any associated process filters.

If the assigned color is changed in the Event Log Builder or visual editor, the event log color will update automatically across all components.

We've also refreshed the color palette used for event logs so it's easier to distinguish between the colors available, while also improving the accessibility of colors used in Process Mining components.

Annotation Builder support for direct writebacks to the Process Intelligence Graph (PI Graph) is now available in Private Preview. Using this feature, you can write AI-generated annotations, such as risk scores, categorizations, and extracted entities, directly into your Object-Centric Process Mining (OCPM) data models as first-class attributes. Previously, enriching data with AI outputs at scale required manual workarounds or was constrained by the 200,000-row limit of Augmented Attributes. With this release, we have built an enterprise-grade pipeline that handles high-volume data enrichment automatically.

By persisting Annotation Builder results natively in the data model, your AI-enriched data is instantly reusable across multiple workspaces, downstream applications, AI Agents, and Action Flows. This eliminates complex data integration bottlenecks and ensures a single source of truth for your AI-generated insights.

This feature also includes:

To use this feature, you must have Data Integration permissions. Then when configuring a new Annotation Builder model, you will need to select your target OCPM entity in the setup wizard to enable native PI Graph writebacks.

For more information, see PI Graph Writebacks.

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

You can now use smart inputs in View modules to retrieve Knowledge Model metadata.

With this additional functionality, you can now write the metadata for any KPI attribute to the View module variable mapping. This lets you use KPI information directly from the Knowledge Model instead of hard coding inputs.

For more information, see the Object variable use case example.

Our Business Miner service has been removed from the platform and has already been replaced by our AI-driven Insight Explorer and Studio features.

With these advanced capabilities, you’ll benefit from:

To learn more about Insight Explorer, see: Insight Explorer

You can now filter root causes when analyzing deviations in Adherence Explorer. This allows users to see the impact of a particular deviation root cause on a KPI.

To learn more about Adherence Explorer, see: Adherence Explorer.

We've redesigned the Copy to modal for packages so it aligns with the Copy to modal for Studio assets, giving you a more consistent and intuitive experience.

We've also added 'lazy loading' where checks for unversioned changes are now made only after a package has been selected. This reduces loading times, improving system performance.

To learn more about creating and managing Studio packages and assets, see: Packages

We've released a new version of the Task Mining Client software. This version includes enhanced internal message handling. We've also removed legacy, unused decryption paths related to protected Windows data. There are no changes to your sign-in process or how your data is protected.

For more information, see the Task Mining install file 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.

PQL now supports two new functions for concatenating unique string values into a single result: STRING_AGG DISTINCT and PU_STRING_AGG_DISTINCT. These functions allow you to summarize multiple string entries into a single list of unique values.

Both functions support an optional ORDER BY clause to control the sequence of the concatenated results. Additionally, PU_STRING_AGG_DISTINCT supports an optional filter expression to refine which source rows are included in the aggregation.

For more information, see the STRING_AGG DISTINCT and PU_STRING_AGG_DISTINCT documentation.

PQL now supports the WITH clause, enabling you to define temporary table aliases and named expressions directly within queries. This allows you to encapsulate complex logic into reusable blocks, significantly improving the structure and maintainability of sophisticated PQL statements.

To provide flexibility in how you define your logic, the WITH clause supports two distinct declaration methods:

For example:

WITH [
  REGISTER "EventLog" AS CREATE_EVENTLOG ( "ObjectTable" ),
  EXTEND "EventLog" WITH "CustomAttribute" AS "EventLog"."Attribute" + 1 
] ( "Eventlog"."CustomAttribute" + 2 )

The declared names are strictly local to the immediate expression. They are not visible outside of it, and the same identifier can be redeclared with a different meaning in a separate expression without conflict.

For more information, see the WITH clause documentation.

Delta Sharing connections now support OIDC (OpenID Connect) Federation authentication. This allows you to connect your Celonis Platform pools to external Databricks shares without the need for static, long-lived bearer token files. This makes your Delta Sharing connections more secure and easier to manage.

For more information, see Delta Sharing.

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 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.

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.

When importing a BPMN model into Process Adherence Manager, PAM now also detects if a model has multiple start events, multiple end events or multiple incoming/outgoing edges, and repairs these automatically.

For more information, see Automatic repair.

The Transformation Hub in Views is a next-generation Business App designed to centralize how you track and report value across your Celonis initiatives. Built on a robust data model powered by KPI Snapshots, it offers a flexible environment to move from high-level summaries to granular details.

Key capabilities include:

For more information, see: Transformation Hub in Views.

You can now create and track KPI Snapshots from your Knowledge Model. KPI Snapshots allow users to capture KPI values at scheduled intervals, creating a record of KPI performance at any given point in time. Instead of recalculating KPIs dynamically against live data, KPI Snapshots store the calculated KPI results as historical data, enabling reliable trend analysis over time.

For example, if teams update payment terms to improve results, historical KPIs might look better than they actually were. KPI Snapshots preserve the true historical view, letting you compare performance before and after changes and measure the impact of initiatives over time.

The benefits of using KPI Snapshots include:

To learn more about creating and tracking KPI Snapshots, see: KPI Snapshots.

Managing a centralized pool of AI credits across multiple departments has historically been a challenge for Celonis administrators. Without the ability to subdivide global AI outputs, organizations faced risks of runaway consumption by a single use case, making internal capacity planning and budget forecasting difficult.

With this release, we have overhauled the AI Settings console to provide administrators with precise, proactive control over AI Output consumption. These enhancements ensure you can scale AI initiatives securely and predictably across your entire organization.

This release includes:

To manage your AI settings, see: AI Settings

Your filtering capabilities in Insight Explorer are getting an upgrade with temporary filters that allow you to perform a more in-depth analysis by applying a filter based on a specific insight. These temporary filters also allow for the use of your own custom attributes. Using these temporary filters, you can go deeper into a group of object instances within a particular insight and then generate additional insights based on that group. This provides the ability to drill down further on any of the insights generated by your Insight Explorer.

These filters can be applied by hovering on the filter for an insight and then clicking the filter icon on the right side. Clicking the Apply Filter button will create a filter based on the case cohort for this specific insight. This temporary filter can be removed at any time by clicking the filter icon again and clicking the Remove Filter button.

To learn more about Insight Explorer, see: Creating an Insight Explorer

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

Insight Explorer is being upgraded with a new option for the process attributes setting  that utilizes an AI agent to discover process inefficiencies that may impact the behavior of your KPIs. Identifying these inefficiencies will improve both the causality and quality of the insights being generated while also allowing for more complex process patterns in your insights, such as activity sequences or ping pong behaviors. Those process inefficiency attributes replace the basic process attributes.

To activate the process inefficiency attributes agent in your Insight Explorer, click the Advanced Settings button in the upper right corner. In the Advanced settings window, select the “Enhance with AI-detected inefficiencies” option under “Attribute recommendations” and then click the Update button.

Once this Insight Explorer is configured and deployed, the process inefficiencies will be generated and displayed alongside your standard attribute recommendations.

For more information, see Configuring an Insight Explorer.

Process Copilots can now generate structured responses by utilizing a fixed JSON schema that can be customized in the AI Instructions of your Process Copilot configuration. Generating structured responses instead of the text strings provides a more predictable and repeatable output for your integrations with Action Flows, Orchestration Engine, or external APIs. Using this new configuration, you can develop a schema that maps specific fields directly to your Action Flow, Orchestration Engine, or external system without manual parsing. These structured responses prevent the need for manually coding JSON responses while also avoiding the potential processing errors caused by the string responses in your downstream analytics.

These new schemas are created on the AI Instructions section of your Process Copilot configuration by enabling the Structured data output toggle. You can then manually enter your schema or click the icon in the right corner to ask the AI assistant to generate the schema Schema based on your description. Once you have finished configuring this Process Copilot, you can test the schema and verify how your responses are displayed using the Integrations tab.

For more information, see AI Instructions.

You can now define and execute authenticated API calls to external web services directly within your Process Orchestration steps.

This new capability allows you to collect relevant data from external services and seamlessly inject it back into your orchestration workflow, making your automated processes more flexible and integrated with systems outside of Celonis.

For more information, see Adding cloud functions to Process Orchestration steps.

You can now use Process Copilot capabilities directly in your Process Orchestration steps, bringing conversation AI into your automated end-to-end workflows.

This integration allows you to use Process Copilot's ability to converse with your Celonis data within any orchestration step. You can analyze data by asking natural language questions, build graphs, search for insights, or view process flows, making your automated business processes more dynamic and data-driven.

For more information, see Adding Process Copilot to Process Orchestration steps.

We have enhanced the Send Email action in Views. In addition to using your personal email address, you can now send messages using the Celonis service address (noreply@celonismail.com).

For more information, see Adding Actions to Studio components.

We've made some performance improvements in Views. The content in your View will no longer reload when you enter and exit View edit mode, giving you a more seamless user experience.

In the Extractor Builder, you can now use the new Filtering Method configuration to define specific filter rules for endpoints, similar to the existing pagination setup. By selecting specific methods based on your source API, you now have more granular control over your data queries, such as using individual query parameters for standard requests or the request body for POST endpoints.

For more information on configuring filtering methods for endpoints, see Configuring endpoints.

With this Public Preview release, we've made some changes to how you interact with Knowledge Models, making them easier and more intuitive to use.

We’ve updated the Knowledge Model asset editor. By replacing the current left-hand vertical navigation with a new horizontal tabbed navigation, we've improved screen real estate use.

Within the Knowledge Model asset editor, you can also now show/hide table columns including short display name, internal note, unit and format. We've also introduced advanced filtering at column level:

You can also now access the new PQL editor from directly within a Knowledge Model using the three dot button:

For more information about working with Knowledge Models, see Knowledge Models.

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

The metrics available for the Multi-Object Process Explorer are being expanded with the new Event Count tab which allows you to see how often an event occurs for a specific object. This new tab is available by clicking on any event in your Process Explorer graph to view the event node details.

This tab includes an expandable section for each object and includes the count metrics for this event, including the average number of times it occurs, the maximum number of times it occurred, and the total number of occurrences for this object. Each section also includes a graph showing the frequency with which every number of occurrences happens for this object, such as how often this event occurred four times or how often it occurred twice. This information is similar to the metrics shown on the “Event count” tab in the Event Explorer metrics.

Along with this change, the average times per object metric is being removed from the Occurrence tab in the node details.

For more information, see Event node details.

Process Copilots are being updated to include a new option that allows you to switch between sources (External API and Celonis Asset) in order to test both the internal and external integrations of your Process Copilots from the chat interface. This update is designed to give you full control over how you test and validate your Process Copilots during the development process and allows you to simulate different execution surfaces in order to ensure that your configuration delivers accurate reasoning.

On the Integrations panel, you can select to use the External API option to test conversations triggered from third-party applications such as Microsoft Teams and then switch to Celonis Assets to verify task executions triggered from your Action Flows or Orchestration Engine. The results of the tests from either integration will be logged and can be viewed from the Monitoring page.

As part our recent updates to versioning and deploying packages, we added a badge to the user interface which displayed the version and deployment status of packages and other Studio assets. We've now discovered an issue with this status badge so have removed it, meaning the status badge will no longer display.

For more information about versioning and deploying assets, see Versioning and deploying packages.

We've added an object and event filters in the event log builder. These filters allow you to select specific events or objects to include or exclude in your event log. By reducing the amount of data materialized in the log, this results in faster performance and more efficient analysis of process mining data.

This improvement is especially useful for large datasets, where unnecessary events or objects can slow down analysis. You now have more control over the granularity of the data included in your logs, enabling cleaner and more focused insights.

To learn more about creating event logs in the Knowledge Model, see: Event logs (object-centric).

We've made some changes to improve the consistency of filters across Views in the Celonis Platform.

Previously, some Views filters were applied and saved automatically as soon as values were selected, with the filtered output updated each time an individual value was selected or removed. For other Views filters, the filter was applied and saved only when confirmed via an Apply button.

We've now aligned all Views filters so filters are only applied and saved when the Apply button is selected. A Cancel button also allows the filter selection to be easily discarded.

For more information about Studio filters, see Filtering Studio Views.

We have expanded the PyCelonis DataModel with a dedicated Augmentation API. You can now programmatically manage the entire lifecycle of an augmented attribute directly from your Jupyter notebooks:

Previously, injecting machine learning predictions or custom Python calculations back into the data model required routing the data through a complete data integration pipeline and triggering a data load. With this release, you can now close the loop, writing results straight from a Pandas DataFrame in MLWB into your operational data model in real-time.

Ensure your PyCelonis library is updated to the latest version to access the new Augmentation API. For detailed code examples and syntax, please refer to the PyCelonis documentation and the Augmented Attributes user guide.

You can now track your team's Celonis Compute Units (CCUs) usage from your data pool overview screen. Celonis Compute Units are a standardized metric used to quantify the compute capacity required on the Celonis Platform when using the new ETL Engine.

When monitoring and tracking your CCU usage, the following details apply:

To learn how to track your CCU usage, see: Tracking CCU usage.

And to learn more about these metrics, see our terms and conditions: Celonis - Terms and Conditions - Services.

With this public preview release, you can now configure an Instance Explorer component for your object-centric data in your Studio Views. The component 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.

And to learn more about your public and private product releases, see: Feature release types.

The new Celonis Assistant is an AI-enabled support assistant that guides you in the use of your Celonis products in real-time. The Celonis Assistant can offer best practices, suggest products, provide assistance with troubleshooting or guide you to build custom solutions on the Celonis Platform.

The Celonis Assistant can be accessed from the main menu on the Celonis Platform and opens a chat window allowing you to ask questions. Using this chat functionality, the Celonis Assistant can offer help with product specifications, best practices, product updates, troubleshooting, use cases, success stories, suggested solutions and more. As you explore the various processes available for you to implement, the Celonis Assistant can provide suggestions about KPIs to track or specific use cases to analyze, and share implementation success stories.

To use the Celonis Assistant, you will need to enable AI Settings and Azure OpenAI models for your team. For more information, see AI Settings.

And to learn more about our Private Preview releases, see: Feature release types.

With this public preview release, you can now assign custom alias names to objects and events within your perspectives. Using aliases allows you to simplify the naming conventions and shorten the more complicated technical table names when creating PQL statements. Once an alias has been assigned, you can use both the original name and the alias when creating your queries.

To enable the use of aliases when viewing your perspectives, click Options - Enable display names:

To learn more about creating and using perspectives in Objects and Events, see: Perspectives.

And to learn more about our public preview releases, see: Private/Public Preview features.

The architecture of your Process Copilots has been upgraded to unlock deeper thinking capabilities and provide more reliable data handling. This overhaul will remove technical bottlenecks and allow your Process Copilots to deliver more accurate responses and process even more complex workflows with ease.

Dimension switching enables faster, more flexible self-service analysis, allowing users to explore multiple data perspectives within a single chart for quicker insights and a better experience.

Users can now dynamically adjust the data in bar, column, line, and area charts by enabling dimension switching.

Previously, users couldn't easily switch between visualizing data on a weekly and a monthly basis.

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.

You can now migrate your full Analysis assets and settings to Studio Views with the migration wizard, enabling you to create dashboards and reports using our enhanced View editing experience.

While Celonis continues to maintain Analysis (by fixing bugs and ensuring performance remains strong), no further feature development will take place. We therefore recommend you migrate your Analysis assets to Studio Views.

For more information, see Full analysis to Views migration.

When importing a BPMN model into Process Adherence Manager, PAM now also detects if a model has multiple start events, multiple end events or multiple incoming/outgoing edges, and repairs these automatically.

For more information, see Automatic repair.

You can now import translations from a Data Model to a Studio package.

Translations in an Analysis use Data Model name mappings. In Views, translations are saved in the package settings. To migrate translations, the name mappings can now be imported to the package settings.

When migrating an Analysis to a View, the translation syntax is automatically updated during the migration and uses the translation keys from the package, with no changes required in the Analysis or View. Users can then select their preferred language from the View Translations menu.

For more information about migrating Analyses, see Migrating Analysis to Views and for information specific to this functionality, see Migrating translations from an Analysis to a View.

The new Synchronization tab introduces object-centric performance metrics in the Multi-Object Process Explorer component, which allow you to view the range of event lead times, execution times, and synchronization times for all objects in a process. These new metrics include:

These metrics are computed for all shared events in the process and can be viewed on the Synchronization tab by clicking the event node in the process graph. The Synchronization tab shows the range of times for each metric and how frequently each time value occurred across the events in this process. In addition, these metrics also provide the average, median and trimmed median values.

These metrics are available out-of-the-box and can help to identify critical bottlenecks in your processes such as:

For more information, see Event node details.

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.

Data engineers and analysts can now create event types directly from raw source data. This enhancement streamlines event modeling by automatically generating the SQL transformations that map event types and relationships to the data. It also enables bulk event creation and configuring event-to-object relationships.

Using the import wizard, an event will follow the raw data if it fits one of the three supported structures:

To learn more about creating events from tables, see: Events.

You can now easily copy Task Types across your Celonis Platform instance to a different team, space, and package. See Copying Tasks Types.

We’ve added a Task Type Status column to the Task Management screen to help you monitor the health of your Tasks. The column displays the current status and flags errors in two categories: errors (critical errors) and warnings (operational issues). For more information, see Troubleshooting Task Types.

Action Flows are being upgraded with a new module that can be used to trigger your existing Process Copilots. This new “Call Process Copilot” module is used to create custom messages that are passed in real-time to your Process Copilot assets. Adding this module removes the need to create workaround solutions using custom code in order to connect your Action Flows to your Process Copilots.

The module can be configured by selecting your connection and the Process Copilot you want to connect to from this Action Flow. You can then create the custom message you want to send using both plain text and Action Flow variables. When the Action Flow is executed, the responses from the Process Copilot are displayed automatically and include the response, the reasoning, and the conversation ID. These calls can also be tracked on the Process Copilot Monitoring screen.

For more information, see Call from Action Flows.

You can now manually control the display order of attributes for your objects and events, which were previously ordered alphabetically. After updating the attribute order and deploying your changes to development or production, the new order will be reflected in both your transformation jobs and the Knowledge Model.

While attribute ordering doesn't impact processing logic, it improves readability, usability, and governance by allowing you to present your data in a logical and consistent structure.

To learn more about creating and managing objects and events, see: Objects.

You can use annotation lines in charts to indicate thresholds and targets. Annotation lines are displayed by default for the primary axis of your chart. If your chart has both primary and secondary axes, you can now toggle annotation lines between these axes using the Annotation line settings panel:

The annotation lines will track correctly against the scales used for each axis, ensuring they are always contextually accurate.

For more information, see Chart annotation lines.

We've released a new version of the Task Mining Client software. This version includes general improvements.

In addition, we’ve added the remote suspension of Task Mining data capture for Private Preview customers only.

For more information, see the Task Mining install file release notes.

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

With this public preview release, you can now add a Performance Spectrum component to your Studio Views.

Traditional process explorers show aggregated views that can overlook real process dynamics. The Performance Spectrum adds a time-based perspective, 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 understand more about this use case and to learn how to configure and use the Performance Spectrum, see: Performance Spectrum

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

For source systems where uniqueness is defined by multiple attributes, Objects and Events now supports composite primary keys. Composite primary keys allow you to define a primary key using more than one attribute directly in the data model. This removes the need to manually concatenate attributes in transformation logic and helps improve query performance.

Previously, all object and event types in the object-centric data model required a single ID attribute with a String data type. This attribute served as the PK, uniquely identifying each row and enabling joins across objects and events. For source systems with composite PK (multiple columns), users had to manually concatenate these columns into a single ID using SQL transformations.

You can now define the PK for objects and events in one of two ways:

For more information, including a step-by-step guide to defining composite primary keys, see: Composite primary keys.

The Agent Tools (MCP) feature is a new Studio Asset that enables AI agents to securely access and interact with Celonis data and insights using the Model Context Protocol (MCP). The Agent Tools asset provides ready-to-use tools that can be used by AI agents to search for relevant information, retrieve real-time process context, trigger actions in external systems, and write decisions back to the Celonis Platform.

Agent Tools can be created as new assets in Studio and then configured with the tools you want to make available to AI agents through the MCP. These tools can include data retrieval functions, insight generators, knowledge model queries, and more. Once the new asset is published, it will generate a unique URL that serves as an endpoint that can be connected to by other MCP clients.

For more information, refer to Agent Tools (MCP) in the Celonis Developer Center.

We've updated the Process Cockpit to be more intuitive and user friendly.

UI Changes

Performance enhancements

For more information, refer to Activating and configuring live data and Process Cockpit.

This release focuses on "under-the-hood" excellence and highly requested fixes for escalated customers:

UI updates:

Our Business Miner service has been removed from the platform and has already been replaced by our AI-driven Insight Explorer and Studio features.

With these advanced capabilities, you’ll benefit from:

As a result of the removal of this service, the Business Miner navigation item has been removed from the navigation bar and no users can access the service. As our Quickstarts feature rely on the use of Business Miner features, we have also removed these from the platform.

To get started with Insight Explorer, see: Insight Explorer.

Following the deprecation of the Business Miner service, the associated data integration Quickstarts have been removed from the platform. As these Quickstarts were only used to establish initial connections to source systems, this change does not affect existing workflows - any connections created with a Quickstart will continue to function as before.

To learn how to connect your source system to the Celonis Platform using our Extractor Builder options, see: Connecting data sources

You can now create a “router” Process Copilot in Studio and use it to choose the correct tool for your specified task. To take advantage of this router Process Copilot, you can build a series of focused Process Copilots with specific skills or for a defined scope and then surface them as tools to the router. Then your users can interact with the router and use it to perform any of the tasks provided by the associated tools.

For example, you can build one Process Copilot per domain or one Process Copilot for each task. This allows each Process Copilot to keep its focus narrow and maintain high quality. You can then expose each of these focused Process Copilots as individual tools to the router Process Copilot. The router can then search these tools to find the Process Copilot that best fits the needs of each request.

When creating the Process Copilots to be used as tools, it is important to provide clear and accurate descriptions to help the router identify its functionality. Each of the Process Copilots being surfaced as tools must be published in the same Space as the router.

With this private preview release, the colors assigned to event logs will remain consistent across all your process mining components and assets. This means that the color assigned in the Event Log Builder or visual editor will be used for that event log in all of your process mining components, such as Process Explorer, Variant Explorer, Process Adherence Manager (PAM), Event Explorer, Case Explorer, Throughput Time (TPT) Explorer and any associated process filters. If the assigned color is changed in the Event Log Builder or visual editor, the change will be updated automatically across all components.

As part of this release, the color palette used for event log colors has been refreshed to make the available colors easier to distinguish from one another and improve the accessibility of the colors used in the process mining components.

To learn more about our Private Preview releases, see: Feature release types.

The new Synchronization tab introduces object-centric performance metrics in the Event Explorer component, which allow you to analyze the arrival times of various objects at specific interaction points in the process. These new metrics include:

These metrics are computed for all shared events in the process and can be viewed on the Synchronization tab in the Event Explorer by clicking the arrow to the right of the Event logs column. The Synchronization tab shows the range of times for each metric and how frequently each time value occurred across the events in this process.

These metrics are available out-of-the-box and can help to identify critical bottlenecks in your processes such as:

For more information, see Event Explorer Component.

You can now choose the color theme used in the Celonis Platform, allowing you to adjust the user interface colors and contrast to suit your needs.

You can select the following preset themes from your user profile management screen:

• System: Uses the browser preferred theme settings.

• Light (default): Classic, clean light-themed interface.

• Dark: Optimized for low light and reduced eye strain.

• High Contrast: Designed for maximum readability and accessibility.

You can also switch between light and dark color themes from Studio Package settings:

With the addition of the dark mode platform theme, we've also expanded Studio color themes to support dark mode-specific color options. This means you can ensure your custom brand color themes remain readable even when users have dark mode enabled.

The dark mode colors match light mode by default. Users can manually override these colors to provide better contrast or visibility against dark backgrounds. This customization specifically applies to Custom Brand Color Themes; Celonis default themes already include automatic translation for dark mode support.

For more information about choosing the theme for your Celonis Platform experience, see Managing your user profile. And to find out more about colors in Studio Views, see Color themes.

We've fixed an issue with the incorrect labeling of some applications in Task Mining.

Previously, Microsoft applications such as Microsoft Outlook were sometimes automatically and incorrectly labeled as Microsoft Teams, potentially giving an inaccurate view of the amount of time users spend using Microsoft Teams.

With this fix, all Microsoft applications will now be labeled correctly during Task Mining. This fix will be automatically applied to all current Task Mining projects and may result in changes to your Workforce Productivity app data for those Task Mining projects.

For more information, see Task Mining default Labels: Microsoft Office. And to find out more about the Workforce Productivity app, see Working with Task Mining data.

Our Business Miner service is being deprecated and has already been replaced by our AI-driven Insight Explorer and Studio features.

With these advanced capabilities, you’ll benefit from:

To prepare for this deprecation, the Business Miner navigation item has been moved down a level and an in-platform notification informs your users of the forthcoming deprecation. As our Quickstarts feature rely on the use of Business Miner features, we have also removed these from the platform.

And to get started with Insight Explorer, see: Insight Explorer

Teams using Celonis core-process catalog v3.0.0 or higher now benefit from two enhancements to both automatic and manual catalog update workflows.

To learn more about updating your catalog version, see: Core process catalog.

When scheduling and managing your View Reports, you can now choose between creating a personal connection, where the report is linked to an individual user in the team, or a technical connection.

A technical connection allows you to link a report or report trigger to a team account instead of an individual user in the Celonis Platform. By assigning View permissions to this connection, the report or trigger remains accessible and active even if the original creator leaves the team or loses Celonis Platform access.

In this example, the report is configured for a technical connection:

To create a technical connection, a team admin must create a reporting application in the Admin & Settings area. For more information, see: Technical connection for View reports.

And to learn more about scheduling and managing View reports, see: View Reports.

With this Private Preview release, you can now import translations from a Data Model to a Studio package.

Translations in an Analysis use Data Model name mappings. In Views, translations are saved in the package settings. To migrate translations, the name mappings can now be imported to the package settings.

When migrating an Analysis to a View, the translation syntax is automatically updated during the migration and uses the translation keys from the package, with no changes required in the Analysis or View. Users can then select their preferred language from the View Translations menu.

For more information about migrating Analyses, see Migrating Analysis to Views and for information specific to this functionality, see Migrating translations from an Analysis to a View.

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

We’re introducing OAuth 2.0 as a connection method for all Celonis Action Flow modules. This industry-standard framework allows applications to interact securely on your behalf without sharing sensitive credentials. You can find OAuth as a connection type in Action Flow modules. This connection type requires a Celonis Admin to create an OAuth client first to obtain client ID and client secret (basic type). See Adding OAuth client to Celonis Platform.

Annotation Builder, our AI-enhanced Studio asset for processing and labeling data, can now be used as a starting step for Process Orchestrations. This allows you to automatically trigger subsequent orchestration steps based on the specific findings and labels generated within Annotation Builder.

For more information, see Annotation Builder and Orchestration Engine.

We’re introducing a refreshed permissions management experience that improves how administrators view and manage access across the platform.

This release includes:

While this update focuses on improving clarity, consistency, and usability for administrators, the underlying permission model remains unchanged:

To learn more about managing your user permissions, see: Managing permissions.

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.

With this Private Preview release, you can now generate Insights from within Views.

Previously, users generated Insights about their data in Insight Explorer before exporting them to Views. Now users can create Insights directly within Views containing KPI list or card components and apply the resulting Insight filters directly to their View.

For more information, see Generating Insights in a View.

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

We’ve refreshed several View components with visual and functional updates to improve the look, feel, and usability of your dashboards and applications. These changes reduce wasted space, standardize the UI, and add new customization options for greater information density.

The highlights include:

Previously, Celonis limited string values in Cloud Extractors to a maximum of 80 characters. Based on customer feedback, this character limit has been increased. Cloud Extractors now support string values of up to 8 KB, with an increase to 65 KB planned in the coming weeks.

Important: Celonis dynamically determines column widths based on actual data to optimize performance and avoid unnecessary processing overhead. However, manually created tables, especially VARCHAR columns defined during the transformation phase, may require manual adjustment if incoming values exceed the existing column size.

If column widths are not updated, you may encounter transformation errors such as:

String of 82 octets is too long for type Varchar(80)

For extraction task best practice, see: VARCHAR optimization.

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.

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.

Dimension switching enables faster, more flexible self-service analysis, allowing users to explore multiple data perspectives within a single chart for quicker insights and a better experience.

Users can now dynamically adjust the data in bar, column, line, and area charts by enabling dimension switching.

Previously, users couldn't easily switch between visualizing data on a weekly and a monthly basis.

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.

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.

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 Configuring an 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 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.

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.