Product Updates

You can now convert one of your custom transformations into a transformation template. Choose a custom transformation from the list in the transformations editor. Either click it to view it and select Transformation actions > Convert to template, or just select Convert to template from the context menu (the three dots) in the listing. The original transformation becomes an instance of the new transformation template. You can rename, edit, and add to the template in the same way as a transformation template you created from scratch. For more on creating and managing transformation templates, see Creating transformation templates. 

You no longer have to connect all the object types in a perspective together. Previously, we didn't allow objects in a saved perspective if there wasn't a path of relationships between them and all the other objects, with the exceptions of the CurrencyConversion and QuantityConversion helper objects, and the master data object MaterialMasterPlant. Now, you can have a perspective that includes standalone objects, and distinct groups of objects that are connected to each other but not to other groups. When you save it, we'll give you a warning message to let you know there are object types that are not interconnected, but you can still save and use the perspective. For the instructions to create custom perspectives, see Creating custom perspectives and event logs.Allowing standalone objects and distinct groups means you can save a partly finished perspective to work more on later. It also means you can include standalone helper objects that are not in the Celonis catalog, such as a factory calendar table, workday or weekday calendar, and alternative quantity or currency conversion tables. You can set any object as the lead object in event logs, including the default event log, and you can include standalone or grouped objects in an extension to a Celonis catalog perspective.A main reason that we disallowed standalone objects and distinct groups previously was that with a single data pool for objects and events, you could only restrict data access through setting data permissions on a perspective. A disconnected object in the data model was a risk because it would not be subject to the same rules as the connected objects. This is still the case, but now if you require strict control of end users' access to data, you can use multiple data pools for objects and events. Give users access to a data pool where only the permitted data is shared with the object-centric data model. If you prefer to use a single data pool, and you are setting data permissions for a perspective that contains any standalone objects or distinct groups of objects, check your data permissions carefully. For more on this, see Data permissions for object-centric process mining.

You can now copy the conformance rate from Process Adherence Manager into your Studio View or use it as a KPI. This allows for better monitoring and reporting of your data. See Exploring deviations.  

The slider controls in Process Explorer use two multi-sliders to explore the events of individual objects and connections within your process. In these multi-sliders, each eventlog appears as a different slider and is color coded to match the objects in the process graph. Moving a slider up will add the next most common event or connection for that specific eventlog, while sliding down removes the least frequent event or connection that is currently displayed for that eventlog. For example, you can adjust the slider for one eventlog upwards to add the next most frequent event for that eventlog to the graph while the remaining eventlogs are not changed. However, if the event being added does not connect to the events currently displayed for this eventlog, additional events will be added to connect the event being added. If a slider has been used to explore the current process, the colored square corresponding to that eventlog will be highlighted with a blue border, even if the multi-slider is collapsed (see the middle eventlog in the screenshot below). This indicates that events or connections have been added to the process flow currently shown.  

Within the PQL editor, the Knowledge sidebar now shows the name of Records and Attributes as maintained in the Knowledge Model instead of their technical names in the Data Model. As a result, users can now centrally manage and maintain display names of the "Data" section in the Knowledge sidebar by editing the names of Records and Attributes. For more information about creating and managing Knowledge Models, see: Knowledge Models. 

Since August, you've been able to choose when to apply a new Celonis catalog update in your team (see August 2024 Release Notes). We've now added an Auto update toggle to the Objects and Events environment so you can choose to automatically upgrade your installed Celonis catalog object types, event types, relationships, transformations, and perspectives whenever a new version is available. Be aware that updates can include Celonis catalog items that you're already using in your object-centric data model, which might get behavior changes or new attributes. Automatic updates are off by default when you enable your first Celonis catalog process. If you decide to enable automatic updates, they'll apply to all Celonis catalog processes. We'll update all your Celonis catalog items whenever a new version is available, and we won't show notification messages about new versions. You can access the Release Notes from the Objects and Events catalog page to see what's changed in each Celonis catalog version. For more on managing Celonis catalog updates, see Updating Celonis object types and event types.

If you’ve enabled object-centric process mining for all the data pools in your Celonis team (see Multiple object-centric data models), the object-centric data and data models in a data pool don’t interact with the case-centric data and data models. We verify when you load a data model that it’s either all object-centric or all case-centric, and we’ve added a warning message that you’ll see if we think the load request is mixing case-centric and object-centric configurations. You shouldn’t see this when you manage your object-centric data models through the Objects and Events user interface as expected.

When selecting the OAuth 2 (JWT Bearer with Private Key) authentication method when configuring your Extractor Builder, you can now select from the following signature algorithm: HS256, HS384, HS512 PS256, PS384, PS512 RS256, RS384, RS512 For more information about authentication methods when connecting to your source systems, see: Extractor builder authentication methods.  

When you publish transformations for object-centric process mining, we create complete transformations, using your scripts as the core of them, to populate the tables in the Celonis database of objects and events. Previously, we set the data type for any attribute column containing a string to VARCHAR(255). Now, we can set the string length for each attribute column according to what’s in the source data that the transformation is handling - either the specified length for the column, or the database default length for VARCHAR columns. If you set a VARCHAR length in your original transformation script, for example using the CAST or LTRIM functions, we'll continue to use that.Optimizing the VARCHAR length means your transformations won’t fail due to overlength strings, and optimizes the performance of the Celonis database, which is very responsive to changes in string length. However, you should be aware that if the string columns in your source database are always or often set to a length greater than 255 characters, the performance of the Celonis database could potentially deteriorate rather than improve. This feature is currently in Limited Availability and will be released to all teams over the next few weeks. You’ll see the changes becoming effective after publishing in objects and events to change the generated transformations.

When you create event logs in the object-centric perspective editor, you can now break down event types into subsets using their attributes, meaning that you can give your analysis an extra level of granularity without creating multiple similar events. For example, you can select the delivery method attribute to create subtypes of the ReleaseDelivery event, so that you can analyze each specific delivery method separately. If you later add a new delivery method as an attribute value, you won't need to set up a new event for it - it'll just appear as a distinct path.You can select any number of attributes for any number of events in the event log, so you can create subsets of events based on combinations of attributes. We'll query the attributes in the order you place the events in the event log, followed by the order you place the attributes in the event type definition. If you need to change the ordering for different use cases, you can do that in the PQL query in Knowledge Models that use the event log.You can break down an existing custom event log by attributes, and still continue to use the event log as you do now. We'll create a new activity column for events and attributes ending in _ActivityDetails, and keep the existing column ending in _Activity alongside it for events only.With the new capability to add custom attributes to event types from the Celonis catalog (see Extend Celonis event types with attributes and relationships), you can use this feature with Celonis event types as well. Add the custom attributes to the Celonis event types, and create or edit custom event logs using them. Applications that don't know about the custom attributes will ignore them, so they won't affect your existing setup. For the instructions to model events, see Modeling objects and events.

We've updated user permissions for Advance Views in Studio, removing the ability for non-admins to edit existing Advance Views. This update enhances security and prevents unauthorized modifications by non-admin usersFor more information about Studio permissions, see: Managing Studio permissions.

You can now create and manage color themes on a global and package level within your Celonis Platform team, allowing you to add your brand colors to your Studio components. This includes selecting primary, secondary, context, and semantic colors using a color selector or by entering a HEX code. You can then use these colors for your chart, table colors, and with a KPI list when configuring your Studio View.For more information about Studio color themes, see: Managing Studio and component color themes.  

Limited availabilityThis functionality is currently in limited availability. If you’re interested in trying it out, get in touch with us through celopeers.com/s/support.Within your Knowledge Model, you can now see where your KPIs are being used and referenced. View usage: This displays the Studio Views where this KPI is being used, with a shortcut to open the View provided. This doesn't display where the KPI is used within an Analysis or if it's included as part of an extended Knowledge Base. Entity references: This displays where the KPI is referenced in other business entities, such as calculated attributes, filters, and variables. This doesn't display where the KPI is referenced in extended Knowledge Models. When deleting KPIs, you'll also be warned if deleting the KPI impacts existing Views or entities: For more information about creating and using KPIs in your Knowledge Model, see: KPIs. 

You can now extend the perspectives from the Celonis catalog with further objects, events, relationships, and event logs. In the perspectives editor, pick a Celonis perspective from one of our Celonis catalog processes that you've enabled, and choose Extend to create a custom extension for it. Your extension can use custom or Celonis catalog objects, events, and relationships. You can connect objects in your extension to the objects in the Celonis perspective by including or embedding them. Embedding (where you use a copy of the object type) is safer as there's no risk of creating a cycle in the Celonis perspective. You can also connect objects in your extension to other objects in the extension. You can add custom event logs that use objects in your extension as the lead object type. You can also change the default event log for the perspective to be one of these. We'll save your extension separately from the Celonis perspective, so you can view and use the original perspective with or without the extension, and you can create more than one custom extension for the same Celonis perspective. If you've already created a custom perspective to use instead of a Celonis perspective, consider adding your customizations as an extension to the Celonis perspective instead. Celonis perspectives get updated with the latest changes and fixes when you update your Celonis catalog version, so they'll continue to meet the requirements for the Celonis apps and features that use them. Using objects and events for process mining explains how to use perspectives.

With the new Studio experience, you can create and edit tabs within your Views. Published Views with tabs now have distinct URLs per tab, enabling you to directly link to them where needed.In this example, the button component has been configured in tab 1 that links directly to tab 2. The user is then directed to the next tab when clicking the button:  

In the SQL query editor where you create transformations, we've changed the color coding to match the editor used in Data Integration. Operators are now displayed in blue, double-quoted strings and base texts are in black, single-quoted strings are in red, and comments are in green. Also, if you get a validation error, the editor now underlines the section of your SQL where the error is present. For the instructions to write custom transformations, see Creating custom transformations.

You can now create your own tags to organize custom processes that you're modeling for object-centric process mining. When you create a custom object type or event type, you'll get the new "Custom processes" category in the tagging section. Type in a tag and then click it to create it. When you save your work, your tags are added to the Objects and Events user interface, where they can be used for filtering, and can be assigned to other custom object types or event types. You can use custom tags up to 41 characters long (including spaces). Tags need to be unique in the "Custom processes" category - note that they aren't case-sensitive. For the custom modeling instructions, see Creating custom object types and custom event types.

We've built the new version of the object-centric Duplicate Invoice Checker using the latest features in Studio, and you can easily customize the views with the new Studio experience's enhanced user interface. We've upgraded the app content too - here are the highlights: Improved duplicate value tracking Improved group validation flow Customizable group prioritization New filter-capable charts to quickly analyze group distribution across dimensions The object-centric Duplicate Invoice Checker that's built on the new Studio experience is available in the Celonis Marketplace as a new package. You won’t be able to download it as an update to your existing object-centric Duplicate Invoice Checker package - you’ll need to download and install it as a new installation (Installing the object-centric Duplicate Invoice Checker has the steps). The new package has the same name as the old package, as it's a replacement for it, and we won’t be updating the old package built with the legacy Studio components.For updates after version 1.0.0 of the package, we’ll clone the existing versions of your views, and add these to the package navigation along with the new versions of the views. (You can opt out of this by deselecting the “Duplicate copied assets before update” checkbox when you action the update.) Cloning the views means you won't lose the customizations you made to existing views, and you can copy them over to the new version of the views. Alternatively, you can discard any of the new views and revert to your existing versions.

You can add hosted images to your enhanced Studio Views, enabling you to add branding and visual enhancements to your content. You can also customize your image style by choosing the fit, background, alignment, labels, and alt text.When adding images to your Views, the following apply: Source: Images must be available on a public URL, meaning that they can be accessed without credentials or through specific environments. Formats: Images must be either JPEG, PNG, SVG, or GIF format. In this example, we've added the Celonis logo to our Process Cockpit app: For more information about adding images to your enhanced Studio Views, see: Images. 

An object-centric version of our Unshipped Orders app is now available to download from the Celonis Marketplace. The app lets you identify and manage deliveries that are still in your distribution centers waiting to be shipped past the planned delivery date - a situation that causes  unrealized revenue, blocked warehouse spaces, and declining customer satisfaction. For the object-centric version of the app, we’ve added a Value Framing view to help you calculate value opportunities.The object-centric Unshipped Orders app is built using the latest features in Studio, and you can take full advantage of the new Studio experience, including easy drag-and-drop customization of the view components. We’ve added an integrated filter bar, and used Studio’s new Task Management interface to handle the app’s tasks and actions. You can also access and display the history of comments and other updates to tasks by adding the Activity history component to views. For the app documentation, see Unshipped Orders app - object-centric.

Celonis Platform Tasks allow human involvement in the automation process. Use Tasks when your automation requires a user's approval, manual input, or a simple decision before being executed. When a predefined event triggers the creation of a Task, a user can act upon it by taking one of the proposed actions. These Task Actions, as we call them, are then automatically executed. For more information, see Tasks.

You can now write PQL queries that run based on the outcome of one or more data model conditions, such as the data type of a column or the existence of match list elements in comparison operators.Before your query is run, Static PQL dynamically checks some properties of your data model and modifies or cancels your PQL query depending on the outcome of these checks.This lets you define business applications that can be used with a range of different data models, helping drive standardization.For more information, see Static PQL functions.

You can now set up a template containing an SQL query, and use it to create the transformations for many similar object types or event types. Templates are especially useful if you are modeling multiple flavors of the same event (for example, delivery dispatch by different shipping methods), or if you are transforming data from multiple data sources to create the same objects or events.When you're creating a transformation for an object type or event type, you'll now get the choice to use one of your transformation templates. There's a new Templates tab in the Transformations area of the Objects and Events environment, where you can create, edit, rename, and delete your transformation templates. You can also see the transformation instances that you've created using each template. The list of transformations in the Transformations tab tells you if a transformation was created from a template, and you can access the template from there too.To get the best out of transformation templates, include local parameters in them for the parts that you expect to vary, such as the source system name. For each transformation instance that you create from a template, you can then just go to the list of local parameters in the transformation editor, and add the correct values for that transformation. The content from the template remains read-only, and it changes to match if you edit the template - so with one edit you can apply fixes or updates to all the transformations that use the template. If a transformation instance needs further customization, for example because a source system holds the data for an attribute in a different way, you can create a partial overwrite like you would for a Celonis catalog transformation. Partial overwrites stay in effect when the template changes.For the instructions to work with transformation templates, see Creating transformation templates.

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.

When you enable a process from the Celonis catalog, you can now choose to skip missing data from your source system. If you enable this feature for a data connection, we'll handle these issues: If your source system data is missing columns that the Celonis object types and event types require, we'll skip over them. Your objects and events will be created with null values in these fields. If your source system data has data types for required columns that don't match those expected by the Celonis object types and event types, we'll cast them to match the expected data types, and use that in your objects and events. You can activate the feature when you create a new connection or at any time afterwards. We’ve disabled it by default for your existing data connections, but you can activate it for them if you need it.Skipping missing data lets your transformations run with errors, so you can still create objects and events even if your data isn't ideal. It's important to know that applications consuming the objects and events can get unexpected problems from the missing data. We recommend that you only use this feature while you're validating the implementation of a process or app. Soon after that, you should go back and fix the issues in a pre-processing stage or during data extraction. You'll find ways to do this in Troubleshooting data extraction and pre-processing.