Product Updates

We've improved our augmented attribute creation flow, making it easier to select and configure different data types.Augmented attributes are a Knowledge Model (KM) asset that can be updated in real-time and without the Data Model reloading. By assigning an augmented attribute to a specific table in the Data Model, you can add additional information to the source system. This additional information can then be referenced in your Views, describing your business objects in further detail and generating additional process insights.To learn more about creating and using augmented attributes in your Studio content, see: Augmented attributes. 

Improved visualization of self-loops in Process Adherence Manager (2024-08-27) We've made it easier to identify self-loops in Process Adherence Manager. The arrow indicating a self-loop now displays in the same color as the event log it appears in. Where a self-loop occurs in more than one event log, an arrow displays for each affected event log in the color of that event log. Refining and editing your baseline model is also simplified as you can now add and delete individual self-loops, as well as replacing a self-loop with an event suggested by Process Adherence Manager. For more information about self-loops, see Working with the process model.

Custom authentication method using the extractor builder for Data Integration (2024-08-19) You can now configure a custom authentication method when creating a connection between your source system and the Celonis Platform using the extractor builder. The custom authentication type allows you to configure the authentication method based on your source system. This includes the following configurations:Request (optional): Configure an API request to an authentication endpoint with all details (Request Type, Request URL, Headers, Parameters etc.)Response (optional): Configure the location of an authentication token in the API response.Authentication header: Configure how the response token is used in the authentication header for all endpoint request and add additional headers on top. For more information about the extractor builder, see: Extractor builder. And for an overview of authentication methods, see: Extractor builder authentication methods. 

Analyst access added to Transformation Hub (2024-08-05) Users with an Admin role in a team can now give Analyst users within that team access to Transformation Hub using permissions. For information on assigning permissions, see Service-level user permissions.

Control Celonis catalog updates for object-centric process mining (2024-08-05) Previously, when we released a new version of the Celonis catalog with upgraded object types, event types, relationships, transformations, and perspectives, we applied the update automatically in your team. This includes Celonis catalog items in processes that you've already enabled and used in your object-centric data model, which might get behavior changes or new attributes. It's important to keep your Celonis catalog items up to date because downstream consumers such as our Business Apps are always based on the latest version of the object types and event types in the Celonis catalog. You also need to keep the SQL transformations up to date so that they are compatible with the current requirements for the object-centric data model - out of date transformations might result in errors when you try to save and publish your model. But there's always times when you're in the middle of something important and you don't want an update right now. From 31 July, you can choose when to apply a new Celonis catalog update in your team. When a new version of the catalog is available, we'll display an Update available link on the Objects and Events dashboard next to the current catalog version, and an Update button on the catalog view. Click the button to get a link to the release notes, and read what's changed in this update and in any previous updates that you skipped. Then select Update catalog if you want to go ahead with the update, or Cancel if you don't want to update now. You'll still have the option available to update when you're ready.

Activity history component added for new Studio Views (2024-07-29) When using the Celonis Platform, all events (such as augmented attribute updates, comments, and task updates) are automatically captured and recorded against rows in a data model table. You can now use the Activity history component to display these events in your new Studio Views, giving you increased visibility into your process data and strengthening your auditing options. You can find the Activity history component in the Object-specific details group in View Edit Mode. To learn how to add an Activity history to your new Studio View, see: Activity history. 

Changes to Action Flow notifications (2024-07-25) Action Flow notifications will now group all errors and warnings into a single message rather than sending individual emails for each error or warning. Notifications will include a link to each warning or error and the scenario history with the specific details. Notifications for errors are sent every 5 minutes, while notifications for the warnings are sent every 15 minutes. Note: Email notifications for deactivations will not be changed as part of this update.

Rename custom object types and event types in your object-centric data model (2024-07-24) You can now rename custom object types and event types after you've created them. Click the context menu (the three vertical dots) for the object type or event type in the listing, and select Rename.  When you rename an object type or event type: We'll automatically update the name in perspectives that use your renamed object type or event type.Object to object relationships and event to object relationships involving your renamed object type or event type will continue to work, but you should update the relationship name if it used the old name. We'll show you which relationships might be affected.You'll need to update transformations that reference the old name in SQL statements. We'll show you which transformations are affected.We'll delete the database table for the object type or event type and recreate it with the new name. If you already built objects or events, they'll be deleted. You'll need to run your transformations again (after updating them) to create the objects or events again. For the instructions to work with custom object types and event types, see Creating custom object types and custom event types.

Dynamic connections for Action Flows (2024-07-24) Dynamic connections allow you to enforce additional authentication of users with their personal credentials whenever they run an Action Flow. Dynamic connections allow you to apply individual user permissions from the respective systems to your automations. Additionally, by providing personal credentials when executing an Action Flow, the user name is recorded in the audit log, which improves traceability. You can enable dynamic connection for all Action Flows with execution scheduling set to “On demand”. For more information, see Dynamic connections.

Data Integration: Send OAuth 2.0 credentials as header or body (2024-07-24) When configuring your data connections using OAuth 2.0 for either client credentials or resource owner type, you can now choose to send the credentials using a Basic Auth Header or via the request body. You can send the credentials using the request body by toggling the feature on when selecting your authentication method. For more information about using the extractor builder and configuring your authentication methods, see: Extractor builder authentication methods. 

Bar and points chart component for Studio (2024-07-23) You can now create and configure a bar and points chart in your enhanced Studio Views. With this chart type, you can compare values across different categories using two or more metrics. You can also compare metrics that have different scales by using the dual axis capability.  For more about our available chart types for your enhanced Studio Views, see: Available chart types. And to learn how to create and configure your own charts, see: Charts.

Changes to Action Flows (2024-07-22) We've been very busy with Action Flows this month. Here are the changes we've made to improve your experience:Improved app search:Improved search speed and reliability.Improved UX:Recently used apps move to the top for a speedy build.Search results provide information about available modules for apps.The new right-hand bar offers all tools and functions ready to hand.The new "Apps in scenario" section provides easy access to previously used apps.New authentication type for SnowflakeWith the "key pair“ authentication type you can connect to Snowflake using the private key, username and account.New modules for Google Sheets Action Flows appWe’ve added two new modules to the Google Sheets Action Flow: Bulk Add Rows (advanced) and Bulk Update Rows (advanced). For more information, see Google Sheets.New app - watsonx.aiWe've added an Action Flow app for watsonx.ai - an AI app which lets you generate responses to a prompt using a variety of large language models. See watsonx.ai.

Enhanced content and the new Studio experience in object-centric Starter Kits (2024-07-19) Our new versions of the object-centric Starter Kits for the Accounts Payable, Accounts Receivable, Order Management, and Procurement processes are now built with the latest features in Studio, and take full advantage of the new Studio experience. We’ve made many upgrades to the Starter Kit content as well as to the user interfaces. Here are the highlights:You can easily adapt the Starter Kits to fit your needs with the new Studio experience.We’ve replaced the Validation Cockpit with a completely rebuilt Setup and Validation view, which is the easiest way for you to align the KPI definitions to what you are used to in your organization.In the Process Cockpit, the new Overview tab lets you see at a glance which use cases improve which business objectives. Other changes include a quick access to the settings and a case table on each tab.Each Starter Kit now comes with more use cases and more ways for you to find value opportunities in your process. Examples include Unshipped Orders and Time-to-Bill for Order Management, and Manual Credit Reviews for Accounts Receivable.We’ve used the latest features in Studio to build the Starter Kit views, including containers, scale-to-fit and scrollable view layouts, built-in filter bars, calculated attributes, enhanced variables, linked views, pie charts, and more.You can compare your key metrics with the new Benchmarking views.The new Value Framing view lets you validate and frame the value of every value opportunity in your process. It’s already in the Order Management Starter Kit, and it’s coming soon for the others. The object-centric Starter Kit versions that are built on the new Studio experience are available in the Celonis Marketplace as new packages. You won’t be able to download them as an update to your existing object-centric Starter Kit package - you’ll need to download and install them as a new installation. The new Starter Kit packages have the same names as the old packages, as they replace them, and we won’t be updating the old packages built with the legacy Studio components. Here's the Setup and Validation view:

Package asset statuses in Studio (2024-07-19) Within your Studio packages, you can now see which assets have been updated (yellow) or added (green) since the package was last published. You can also see which package assets are currently hidden.You can also see which assets have been added, updated, or hidden when publishing the package:When a published package asset is hidden, it isn't visible to App users. You can control asset visibility either by clicking Options - Hide / Unhide on the individual asset or by clicking Package Settings - Apps Perspective. For more information about creating and managing Studio packages, see: Packages. And to learn more about our available package asset types, see: Asset types.

Set variable admin permission preferences in Admin & Settings (2024-07-18) As a full team admin, you can now set permission preferences for the variable admins in your Celonis Platform team. These preferences are enabled by default: CSV downloads of audit logs, user groups, user login histories, and user permissions.Inviting users, creating groups, and creating application keys.Only a full team admin can disable preferences. When preferences are disabled, any existing users holding variable admin permissions will lose access to the relevant admin features.For more information about variable admin permissions, see: Variable admin permissions.

Sort the lists of objects and events in your object-centric data model (2024-07-12) In the Objects and Events user interface, you can now sort the lists of object types and event types by creation date or the date of the last edit, and in forward or reverse alphabetical order. Combine sorting with filtering by process, namespace, and metadata to quickly find the object type or event type you want to work with. For tips on exploring your objects and events, see The object-centric data model. 

Re-creation of current Process Adherence Manager assets required (2024-07-11) We’ve changed how assets are created in Process Adherence Manager (PAM). Previously, you created PAM assets using object-centric data models (also known as perspectives). From 2024-07-11, you create PAM assets based on knowledge models that are defined on top of object-centric data models. Changes you’ll notice are: PAM assets are consistent with Studio assets, including in Process Explorer in Views.Object types have been replaced by event logs so you’ll no longer see discrepancies with event logs used elsewhere in the Celonis Platform.More flexible modeling and analysis as event logs in object-centric data models use the PQL CREATE_EVENTLOG function.Global filters defined in knowledge models are automatically applied to PAM assets.We've removed charts and tables and Event-Object relation and Event property filters. ImportantAny PAM assets created before 2024-07-11 are available from 2024-07-11 as read-only assets only. After 2024-09-11, they’ll be irretrievably removed. To continue using them, you’ll need to re-create any PAM assets created before 2024-07-11 between 2024-07-11 and 2024-09-11. Re-creating assets involves reconstructing the target model for each asset and re-defining any preset filters. We envisage it will take less than 15 minutes to re-create each PAM asset. Find out how to re-create your assets here.

Duplicate custom object types and event types in your object-centric data model (2024-07-08) You can now make copies of a custom object type or event type, to speed up the process of modeling multiple similar objects or events. Find your original object type or event type in the list, and use the Duplicate option on the context menu (the three vertical dots) to duplicate it with a new name of your choice. The duplicate object type or event type has all the attributes of the original and all the tags that were assigned to it, and you can edit it as you want. We don't duplicate any of its relationships or its transformations. For the custom modeling instructions, see Creating custom object types and custom event types.

Calculate throughput time for object-centric data (2024-07-07) The PQL process function CALC_THROUGHPUT can now be used with object-centric data models. You can use the function to calculate the throughput time between events that are not directly connected to the same object type. For example, here's how to find the number of days taken between a sales order being received and its last item being shipped to a customer: CALC_THROUGHPUT ( “o_celonis_SalesOrder”, FIRST_OCCURRENCE ["e_celonis_CreateSalesOrder"] TO LAST_OCCURRENCE ["e_celonis_CreateDeliveryItem"], DAYS )  For the function documentation, see CALC_THROUGHPUT. 

Object-centric process mining: Possible changes to analysis results that depend on event log order (2024-07-06) We've fixed an issue where event logs for object-centric process mining might not be correctly ordered by timestamp for event types with long include paths. This could happen when the include path for an event (the path in the schema between an included event type and the lead object) spans at least two switches in join direction (1:N:1 or N:1:N). The issue might have occurred in any of your event logs, including autogenerated and custom event logs for perspectives, and event logs you set up outside the perspective builder using the PQL function CREATE EVENTLOG. For affected event logs, this fix corrects the order of the events, but the results of any PQL operator that depends on the event log order might be different after the fix is rolled out in your region. The process operators such as VARIANT are the most likely to be affected but others can also have this dependency. If there's an affected event log in your data model, you'll see this warning when you work with the event log in the PQL editor for Views, or in the user interface for Studio Analysis: CREATE_EVENTLOG: The order of <event_type> events in your event log with lead object <object_type>changed. This order changed for <number> out of <number> lead object instance(s). Consequently,the result of any PQL operator which depends on the event log order may have changed. Re-validate the results of any analysis that uses this event log. For more information,refer to the release notes. We’ll be applying the fix to groups of regions through this month. If you work with an event log after the end of this month and don’t see the warning, the event log isn’t affected, and you don’t need to take any action. If you do see the warning, check where the affected event logs are used in your analysis, and re-validate the analysis, especially if important numbers and heavily-used metrics are impacted. Check components and assets such as Variant Explorer, Process Explorer, and Process Adherence Manager.

Are you using an old version of the JDBC Extractor? (June 2024) From now on, we’ll only be providing fixes for the most recent version of the on-premise JDBC extractor. If you're running a JDBC extractor that's not the most recent version, and you raise a support ticket, we'll check whether the bug or issue still exists in the most recent version. If it does, we’ll fix it in that version. In any case, you'll need to upgrade to the most recent version to get the fix. Older versions of the JDBC extractor won't stop working - you can carry on using them until you need support, at which time you'll need to upgrade to get the bug fixes. We recommend you update the JDBC Extractor at least every quarter, even if you don't experience any issues, to get the latest capabilities and any fixes for security vulnerabilities. Updating the on-premise JDBC extractor tells you how to find the version numbers for the most recent version and your current version of the JDBC Extractor.

Find object-centric data model transformations with overwrites (2024-06-27) We’ve added a filter to the list of transformations so you can easily pick out Celonis-supplied transformations where you’ve made overwrites. An overwrite is a custom script that you create to replace part or all of the supplied Celonis transformation script for a Celonis catalog object type or event type. If you filter on transformations with overwrites, we’ll include both partially overwritten or completely overwritten Celonis-supplied transformations. You can find the Overwritten filter before the list of transformations in the Transformations page of the Objects and Events user interface. For the instructions to create custom transformations and to overwrite a Celonis script, see Creating custom transformations.

Reauthorize Google OAuth credentials for your Action Flows (2024-06-26) Action Flows using Google modules to handle OAuth 2.0 credentials provide enhanced security and compliance. To take advantage of this feature, existing Actions Flows that use Google connections must be updated to reauthorize your credentials. If your Celonis Platform is hosted in one of the realms listed below and you are currently leveraging an OAuth connection in your Actions Flows’ Google modules, then your connections will be affected. Impacted realms:Europe: bnpp, eu-1, eu-3, training, tryNorth America: ca-1, us-1, us-2, us-3 If you do not reauthorize your credentials, then your Action Flows which are using these connections will fail and you will receive an error notification email showing exactly which Action Flow is failing. To restore your connection, follow the steps provided here: Reauthorize Google OAuth credentials. 

JDBC Extractor version 2.99.0 (2024-06-19) With this latest release, we've added the capability for on-premise extractors to increase parallel executions up to 40 through local configurations. For more information about this, see: Configuring an on-premise extractor. The 2.99.0 release also includes the following upgrades and fixes:We've upgraded the Google BigQuery driver to the latest version (1.5.4.1008).We've fixed struct columns parsing in Oracle tables after an Oracle JDBC driver upgrade. For more information about installing and updating the on-premise JDBC extractor, see: Updating the on-premise JDBC extractor.

Object Link enabled for all object-centric process mining teams (2024-06-19) In teams where you have a license for object-centric process mining, we now enable Object Link by default - you don’t have to raise a support ticket. Object Link is available in the data model editor in your data pools, and you can use it to model graph structures and recursive links in your data. For the documentation, see Object Link.