Upcoming changes
This section lists planned feature releases as well as advance notices about updates that may impact existing functionality.
We recommend checking here regularly to stay ahead of any changes that could affect your setup.
The feature listed below is planned for release in the coming months. This information is provided to give you an early look at what’s coming. Release timelines may change, but we aim to keep them as accurate and up to date as possible, with regular updates.
July 6, 2006
NEW STUDIO Context displayed for temporary View filters
We’re changing how temporary filters work in Views so additional context is displayed, supporting the discovery and validation of correlations and aiding hypothesis generation and cohort comparison use cases.
Previously, when a temporary View filter was applied, all data that didn't meet the filter criteria was immediately removed from the data displayed and chart scales were automatically updated. This could make it difficult to understand the context of the filtered data within the wider data set and identify systemic issues and correlations.
Now when a temporary filter is applied, the filtered and non-filtered data will both be displayed. Toggling the temporary filter on and off and changing the filter selections lets you compare the data before and after filtering, helping you identify where the behavior of the filtered subset of data deviates from or aligns with the wider data set.
Once you confirm the temporary filter options, only the filtered data will be displayed and any chart scales will automatically update.
In this example, the filtered and unfiltered data are both displayed in the KPI list and bar chart, with the grayed-out sections of the bars in the bar chart giving a visual representation of the unfiltered data set.
July 1, 2026
IMPROVED PROCESS DESIGNER Additional language support, UI improvements, bugfixes
We've added support for Spanish, French, Italian and Japanese in Process Designer. Note that this update will not affect any existing language configurations in your Process Designer instance.
In addition, we've made some quality-of-life UI improvements. These include:
The Help section now has direct links to Celonis Community and Celonis Academy.
Process manuals now use the official Celonis logo, for a consistent experience.
The homepage Chart widget now has an increased character limit.
The Admin section now displays Process Designer instance information for deployment tracking.
 |
This update also includes bug fixes for the following:
Fixed an issue with sequence number placements in process manuals
Fixed an issue with the mass data Excel export option
Fixed an issue with sub-processes not inheriting permissions
Fixed an issue with Matrix graphics in Process Navigator
Fixed an issue with sorting Corona objects in the Detail view
Fixed an issue with displaying the correct process name across Process Designer and Process Navigator
Fixed an issue that prevented users in Viewer mode from seeing the scope filter for a sub-process
Expired process versions can be seen again in the release history in Viewer mode
The consolidate function works again
PDFs can be generated again
The Canvas app lane assignments, disappearing navigation icons and empty diagram issues have been resolved
For more information, see: Translation service or Enabling Canvas app.
June 18, 2026
IMPROVED STUDIO Live reasoning traces for Process Copilots coming soon
As your Process Copilot works through a query, you can now follow its thinking and decision-making step-by-step as it unfolds. The new live reasoning traces show which tools are being called by the Process Copilot, what data is retrieved, and how it arrives at the final answer provided. This level of insight provides builders and end users full transparency into how the Process Copilot reaches its conclusions, making it easier to debug and refine your Process Copilot's behavior.
The following updates introduce changes that may not be fully compatible with previous versions.
We’re providing this information ahead of time to help you prepare and make any necessary adjustments before the updates roll out.
May 1, 2026 to December 31, 2026
BREAKING TASK MINING Deprecating API keys in the Task Mining Client software
Important
You must take action if you’re using version 2.16 or earlier of the Task Mining Client software and/or want to continue using Task Mining projects that were created using version 2.16 or earlier of the Task Mining Client software. No action is required for later versions of the Task Mining Client software.
What's changing
We’re removing support for API keys and moving to industry-standard OAuth authentication across the Celonis Platform. This will provide enhanced security, improved integration performance and better scalability and maintainability for upcoming releases.
Action required
May 1, 2026
From May 1, 2026, you won't be able to create new Task Mining projects for versions 2.16 and earlier of the Task Mining Client software. To create new Task Mining projects and to continue to access your existing Task Mining projects, you must update your Task Mining Client software. We recommend using the latest version available.
December 31, 2026
From December 31, 2026, Task Mining projects created using versions 2.16 and earlier of the Task Mining Client software will be permanently disabled.
June 30 to December 15, 2026
BREAKING ADMIN Decommissioning API and application keys: Action required
Important
These changes impact all current users of Celonis public APIs.
If you don’t use APIs or application keys in your applications or in third-party systems for these APIs, these changes will not affect you and no action is required.
Why we’re making these changes
We’re moving away from using API and application keys to the OAuth 2.0 authorization standard to provide a more secure, streamlined and efficient developer journey.
Users currently generate long-term API keys or application keys in the Celonis Platform. These keys are then embedded in applications and allow data to be requested or pushed using Celonis APIs. As these keys typically have a long life, cannot be rotated and their scope cannot be limited, any application with an embedded API or application key can access almost all Celonis APIs.
With OAuth 2.0, scoping means OAuth-enabled clients can access permitted APIs only. This follows the security principle of least privilege so an OAuth client only has the privileges required to perform a certain task.
Timeline
The deprecation of APIs and app keys will happen in phases:
By June 30th 2026, the creation of new app/user keys will be blocked.
Existing app/ users keys will remain valid and may be used.
By mid-December 2026, the use of app/user keys for external integrations (any request coming from outside the Celonis infrastructure) will be blocked.
The use of keys for internal integrations will continue working.
Action required
Given the mentioned timeline, prepare your existing infrastructure in the following way:
Identify any systems and/or applications that use API or application keys.
Migrate these systems and/or applications to OAuth 2.0.
Additional points to consider:
If you were part of the beta program of the Platform Adoption Monitoring App and you're still using AppKeys, you must migrate to OAuth 2.0.
If you use the Celonis User Adoption dashboards, which extract Platform Adoption data through Action Flow, you must migrate to the new Celonis Platform Adoption Monitoring App.
If you build your own Platform Adoption Extractor using the Celonis Platform Adoption Template and you selected AppKey as the authentication method, you must migrate to OAuth.
If you use Celonis Platform Adoption Monitoring App V1.3, no action is required. This version already uses OAuth.
The Platform adoption statistics under Admin & Settings will continue to work. No action is required.
For information on enabling OAuth 2.0 on the Celonis Platform, see Using an OAuth 2.0 token in Celonis.
Note
We're aiming to move to OAuth 2.0 for all Celonis use cases. If you're using other Celonis APIs that already support OAuth 2.0, you can move to OAuth 2.0 for these APIs too. The OAth 2.0 support for Action Flows and on-premise clients is already available.
December 31, 2026
BREAKING DATA INTEGRATION Deprecating SAP on-prem extractor: Action required before December 31, 2026
Note
This announcement was updated on April 16, 2026
OPE will remain active for existing customers beyond December 2026. Please note that support for existing OPE-based data pipelines will be discontinued at that time.
Celonis is transitioning away from the legacy SAP On-Premise Extractor(OPE), with full deprecation scheduled for the end of December 2026. After this date, Celonis will no longer provide support or maintenance for OPE-based data pipelines.
Important
To ensure your data flow remains fully supported and aligned with our latest standards, we encourage all customers to migrate to the modern On-Premise Client (OPC) by the end of December 2026.
This change is driven by a necessary update to our authentication security model. The outdated key-based authentication mechanism used in OPE is being replaced by the industry-standard OAuth protocol in OPC. To align with modern security requirements and maintain data pipelines, the entire legacy OPE framework will be shut down by the end of 2026. We recommend migrating your SAP Extractors to the OPC framework during this window to remain on a supported platform.
We recognize that some customers rely on specific OPE features which are not yet available in the OPC. These features are currently under development and we plan to deploy them in 2026. We will communicate the exact release dates for these features in our Release Notes.
The following OPE features are currently not yet fully supported by the OPC:
Extraction via PI/PO
Extraction from legacy SAP versions 4.6 and 5.0
Column value filter functionality
Calculated columns