Celonis Product Documentation

Studio is being upgraded to make it easier to create a Process Copilot by adding the ability to create a new Process Copilot directly from a View. This feature allows users to create a new Process Copilot specifically for the data in the current Studio View without any additional configuration required. This new option will streamline the creation of a Process Copilot and give users a starting point to build upon. Users can still make additional changes to this Process Copilot by customizing the configuration settings.

From any Studio View, users can select “Create Process Copilot” from the options menu and choose the type of Process Copilot to create. The Process Copilot is generated automatically and all the required configurations are completed based on the data in that Studio View.

Users can then start asking questions about their KPIs and attributes. For example, looking at the image above, users can ask questions such as “What’s my Net Order Value?” or “How are the Sales Orders broken down by Company Code?”. It is important to remember that this Process Copilot will only have access to the data from that Studio View and cannot answer questions about any of your data outside of that View.

For more information, see Create a Process Copilot from a Studio View.

In the Data Jobs area of the data pool you're using with objects and events, you can now see the logs for the data model loads for all your perspectives, as well as the logs for your transformations. Previously you had to go to the Data Loads tab in the Data Models area of the data pool to view the logs for perspective loads, and select each individual perspective. The logs for the perspectives are still in that location as well if you want to view them there.

You can see the logs for the perspectives together with the logs for the transformations in the object-centric process mining data jobs ocpm-data-job (for production) and test-ocpm-data-job (for development). The data model loads are also included in the execution time for the data job, which means the displayed execution time is likely to increase, but the total execution time across the data model loads and the transformations has not changed. This change lets us optimize performance for change-aware executions (see Executing data jobs). If you're using that limited availability feature, your total execution time across the data model loads and the transformations is likely to decrease.

In this release of the Planning Parameter Optimization app for Inventory Management, we've added tasks to update purchase lead times and production lead times. You can download the new version from the Celonis marketplace. Updating the object-centric Inventory Management Planning Parameter Optimization app has the instructions to update the app.

In this upgrade for the Payment Terms Harmonizer app for the Procurement process, we've added the Vendor Invoice and Accounting Documents objects, and the Renegotiate Contracts, Solve Mismatch, and Update Vendor Master Data tasks. With these you can include invoice data in your comparisons for a more complete picture, and easily take actions. Updating the Payment Terms Harmonizer app has the instructions to update.

We're making a range of improvements that you've requested, to enhance your experience of modeling and managing objects and events for object-centric process mining. Here are the latest changes:

When previewing your Studio Views using the interactive mode, any View preferences you configure are now kept when you re-enter View edit mode. View preferences are unique to each user and created by their interactions with filters, user specific variables, and components.

View preferences include, but aren't limited to, the following:

When editing a Studio View, you can see when View preferences are applied by clicking the View preference icon:

You can then click Restore default View to remove these preferences again.

For a video overview of these new features:

For more information about creating and editing Studio Views, head to: Views.

And to learn more about restoring to your default View, see: Restore default View.

For this release of the Accounts Receivable Starter Kit, we’ve added a Value Framing view to the app’s existing setup, validation, and process cockpit views. The Value Framing view picks out opportunities for improvement in your Accounts Receivable process, including labor productivity, working capital, and revenue. Each value opportunity has its own tab for you to explore detailed metrics and get deeper insights into its business impact. When you’ve validated the opportunity, you can input your own framed value assessment for the Identified Value overview. For the instructions to upgrade the Starter Kit, see Updating the object-centric Accounts Receivable Starter Kit.

For the latest version of the object-centric Procurement Starter Kit, which is built on the new Studio experience, we've upgraded the process execution model in the Process Cockpit to give you deeper insights into your procurement operations. The new model includes:

We've also added new views to monitor and analyze KPIs for on-time delivery and on-time in-full delivery, purchasing behaviors such as contract usage, and automation activities.

To upgrade, download version 2.8.0 of the object-centric Procurement Starter Kit from the Celonis Marketplace. If you want to migrate your existing setup, you can copy the Knowledge Model and Process Explorer from your previous version into the new Studio package.

We've changed how existing data is handled when changes are made on the Task Mining UI.

Previously, any changes you made to a label or task were applied automatically to incoming data only, with significant manual intervention required to apply them to existing data too.

After making changes, new list options on the Task Mining UI Run button now let you choose whether to process incoming data only or to re-process all data. Re-processing all data means existing and incoming data are processed in exactly the same way, giving consistent analysis results.

For more information, see Data processing types.

The process of working with multi-object Process Explorers is being improved with a global slider that allows users to add and remove nodes and edges in their process graph across multiple object types. The global slider provides users the ability to explore their process graph across multiple objects using a single control.

This new slider makes it easier for users to quickly explore their process by adding or removing elements across multiple object types simultaneously rather than updating the slider for each object type individually. Users will still be able to use the individual object type sliders to add and remove elements for those specific object types. The global slider works in unison with the individual object sliders, so if changes are made using the global slider, those changes are also reflected on the individual sliders. Adjustments made using the individual sliders will also be shown on the global slider.

The new global slider is displayed alongside the existing object type sliders and controls all available object types in the process graph. Moving the global slider up will add more elements to the graph from each object type, while moving the slider down will remove elements from each object type. When using the global slider, elements are added based on the global order of the object counts. When removing elements using the global slider, the elements and connections are removed based on the order in which they were added.

For more information on using Process Explorer controls, see Multi-object Process Explorer.

We've streamlined the process of adding Actions to both Studio components and Tasks. The interface is now more intuitive and consistent across our platform, so you'll have a familiar experience no matter what you're working on. For more information on Actions you can add to Celonis Platform, see Actions in Celonis Platform.

Psst...did you know you now can add Actions to Buttons in Studio, too? Check Actions in Buttons.

If your Oracle Fusion Cloud BICC instance uses UCM storage, you can now enable PGP encryption when connecting to the Celonis Platform. With PGP encryption enabled, all files written to UCM during an extraction will be encrypted by BICC. When the Celonis extractor downloads these files, it then automatically decrypts them.

Before enabling PGP encryption in the Celonis Platform, you must activate data encryption in your BICC external storage connection to UCM. You then use the encryption key and passphrase provided by your BICC instance when configuring your connection in the Celonis Platform.

For more information about connecting your Oracle Fusion Cloud BICC instance to the Celonis Platform, see: Oracle Fusion Cloud BICC.

The process for selecting the tools to be used by Process Copilots during configuration has been updated to allow users to select the specific tools they want to make available. Selecting the specific tools for a Process Copilot to use removes the possibility of users adding tools that are not necessary for their use case or selecting too many tools which can complicate the configuration and cause responses to be less accurate.

Each tool has its own method for configuration that is specific to that tool’s intended use case. Each tool utilizes different fields, data, settings and configuration options that must be set when adding this tool to a Process Copilot. Some tools have the option to create a custom configuration or to be configured dynamically based on the questions submitted to the Process Copilot. Other tools will need to be configured using the YAML Editor.

Once added to the Process Copilot configuration, tools can be enabled or disabled using the toggle switch.

For more information on configuring tools, see Tool Activation.

Extractor Builder is our Celonis Platform component that allows customers to connect to any source system exposing REST APIs. With this launch, we are introducing a new and improved guided user interface which simplifies and accelerates the data integration process.

The enhanced Extractor Builder now includes:

For more information, head to Enhanced Extractor Builder (Private Preview).

The Annotation Builder asset in Studio is adding a new feature that allows users to automatically run an Annotation Builder on new data each time the Data Model is reloaded. This feature is intended to simplify the annotation process in use cases where the Data Model is updated frequently by running the Annotation Builder automatically when new rows are added.

Users can activate this feature by clicking the Automate & Scheduling button on the Agent Builder screen and selecting the “Run AI Annotation Builder on each Data Model reload” option. Once enabled, this Annotation Builder will automatically annotate any new rows added when the Data Model is reloaded.

For more information, see Running your Annotation Builder.

You can now add both event explorer and throughput time explorer components to your Studio Views, giving you greater process visibility.

If you're currently using the JDBC extractor, our latest upgrade (3.6.0 onward) requires you to update to Java v.21 before starting the upgrade.

You can find access JDBC extractor 3.6.0 by clicking Admin & Settings - Download Portal.

For more information about the JDBC extractor, see: Updating the on-premise JDBC extractor.

When filtering a table or using an input dropdown in Studio or published Apps, you can now use the following enhanced features:

For more information about configuring tables in Studio, see: Tables.

And to learn more about configuring input dropdowns in Studio, see: Filter components.