STUDIO Global sliders in multi-object Process Explorers 

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.
 

STUDIO New tool editors in Process Copilot

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.

Note

Users will still be able customize the tools used by their Process Copilots by configuring the tools in YAML.

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.
 

STUDIO Annotation Builder Automation and Scheduling 

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.
 

STUDIO Event explorer and throughput time explorer components added to Views 

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

• Event explorer component: This component displays event logs from your Knowledge Model (KM), giving your app users the ability to click on available events and view further details
  To learn more about the event explorer component, see: Event explorer.
  
• Throughput time explorer component: The throughput time (TPT) explorer component allows you to select starting (from) and finishing (to) events in that process and understand the duration between them. If you can identify areas where there are backlogs, bottlenecks, or slowdowns, you can then address these and improve efficiency. Quicker throughput times increase return on investment (ROI) and profitability.
  For more information about the throughput time explorer component, see: TPT explorer.
  
   

STUDIO Enhanced dropdowns in View filters

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

• Shortcuts to allow you to quickly filter to included or excluded values in your Views or within your filtering list.
• Type a string in the search bar to quickly filter in bulk by including or excluding values that match the query.
• Range filtering for number dimensions values to allow you to filter your View by more precise numerical values.

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

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

DATA INTEGRATION PGP encryption enabled for Oracle Fusion Cloud BICC 

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.

DATA INTEGRATION Extractor Builder - Improved user experience - PRIVATE PREVIEW

During a Private Preview, only customers who have agreed to our Private Preview usage agreements can access this feature. Additionally, the features documented here are subject to change and / or cancellation, so they may not be available to all users in future.

If you would like to use this feature, create a Support ticket at Celopeers.com.

For more information about our Private Preview releases, including the level of Support offered with them, see: Feature release types.

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:

• Improved navigation: Visual overview screen and new menu bar allowing for quicker navigation between the configuration pages.
• Integrated data connection setup: Allowing the creating of a data connection as part of the process directly in Extractor Builder.
• Simplified authentication configuration: Simplified process to select and configure the right authentication method by providing examples and in-product documentation.
• Extraction tests and previews: Directly validate and test the extraction for an endpoint and retrieve a preview of your data.

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

DATA INTEGRATION JDBC extractor 3.6.0 requires Java 21 

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.
 

TASK MINING Re-processing of existing data when labels and tasks are updated 

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.
 

AUTOMATION Keeping Action editors consistent 

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.