Product Updates

Extractor builder error handling in Data Integration (2024-06-12) When creating or editing your extractor builder error handling rules, you can now toggle on the ability to stop the extraction task and mark it as successful when a rule is matched. For example, when the Http Status equals 204 then this extraction task will be stopped and marked as successful in the logs.For more information, see: Extractor builder endpoints.

Enhancements to chart component in Studio (2024-06-11) We've made a number of enhancements to our chart component in Studio, improving the look and feel of your new Views. These updates include:Additional colors: Adding to blue, gray, and green, you can now also select from semantic colors: red, green, orange, and a transparent color option. Revert axis title: You can now revert your axis titles back to their default labels.Alternative chart types: Improved messaging when alternative chart types are better suited to the data you've selected. Display options for annotation lines: You can now select between name, value, or both for your chart annotation lines. Sorting categorical column charts: You can now sort categorical column charts, choosing between ascending or descending orders. For more information about creating and configuring the chart component, see: Charts.

Last Edited By and Last Edit columns in Data Integration (2024-06-11) We’ve added an additional column for each of the main components in Data Integration indicating the person that last edited this component and when the last edit has been made. For example when a user adjusts a transformation script or a data model, the change will be reflected in those two columns: For more information about integrating your data into the Celonis Platform, see Data Integration.

JDBC Extractor version 2.98.5 (2024-06-10) With the latest version of the JDBC extractor, we've added support for materialized views and snapshots when connecting to Google BigQuery. For more information about connecting to your Google BigQuery account, see Google BigQuery. This version of the JDBC extractor also includes the following fixes:Retry file upload on receiving HTTP status code 408 to overcome temporary CloudFlare issue.Optimized the way file upload works to improve performance and avoid connection timeout issues.Upgraded Snowflake JDBC driver to version 3.16.1 to fix issues with nested paths on Windows machines.Upgraded several third party libraries to fix vulnerabilities.For more information, see Connecting to a database.

See transformation status in the Objects and Events UI  (2024-06-07) You can now see and troubleshoot any issues with running your transformations while you're working in the Objects and Events interface, rather than the underlying data pool. In the Transformations tab for an object type or event type, we now show you the status of the base transformations (running, successful, canceled, failed) from the last time a data job was run. (If you haven't run a data model load yet, you'll see the status “Not executed”.) There's also a link for each type of transformation (Base, Change, Extension, Extension_Change) to take you to where the transformation task appears in the logs for the data job. Running transformations has the instructions to run transformations.

Duplicate Invoice Checker (object-centric) version 0.1.0 (2024-06-05) The object-centric version of our Duplicate Invoice Checker app for Accounts Payable is now powered by an AI Annotation. The AI Annotation with out-of-the-box search patterns provides a stable and scalable backend, powering the duplicate checking algorithm. The AI Annotation replaces both the Machine Learning Sensor and the Knowledge Model search pattern customization that are used in the case-centric version of the app. You can easily filter your invoices and configure and customize checking with the UI - no PQL or YAML coding is required. To get the object-centric Duplicate Invoice Checker app, look on the Celonis Marketplace, and to find out more from the documentation, see Duplicate Invoice Checker - object-centric.

Inventory Management Planning Parameter Optimization app (object-centric) version 2.0 (2024-06-04) We’ve renamed the object-centric Inventory Management Master Data Improvement app to the Inventory Management Planning Parameter Optimization app, and refactored the app’s Knowledge Model to revise the KPI IDs and records. The new version 2.0 is compatible with the Knowledge Models for the Material Allocation app and the Supply Chain Network Visibility app. The case-centric version of the app keeps the old name. The Inventory Management Planning Parameter Optimization app enables planners to identify materials with overstated or understated lead times, safety stock, or reorder points based on their consumption and replenishment patterns. The app provides recommendations and action flows to enable material planners and supply chain analysts to easily correct parameters in the source system. With this version of the app, we’ve added intelligent lead time parameter recommendations based on Machine Learning. Machine Learning assists you to remove bias from parameter recommendations, and returns a lead time closer to what your supplier is capable of, instead of being biased by occurrences such as purchase orders placed either at short notice or too much in advance. If you already have the Inventory Management Planning Parameter Optimization app installed, when you update to version 2.0 from version 1.5 or earlier, you’ll need to reapply any customizations you made to the KPIs in the Knowledge Model. Updating the object-centric Inventory Management Planning Parameter Optimization app has details of the changes we made, and instructions to upgrade your app. You can do this whenever you’re ready.

Supply Chain Network Visibility app (object-centric) version 1.0.0 (2024-06-04) We’ve renamed and extended our End-To-End Lead Times app to create the Supply Chain Network Visibility app. This object-centric app for Inventory Management identifies opportunities to reduce excess inventory and exceed service levels across your organization’s end-to-end supply chain network. You can use its views to visualize the upstream and downstream impact of materials on key performance indicators like supplier reliability and service levels, unlocking strategic, long-term opportunities to optimize your supply chain network. For the Supply Chain Network Visibility app, we’ve added:A value assessment dashboard to provide insights and recommend targeted actions to reduce excess and obsolete inventory, prevent excess replenishment, and improve service levels.A downstream network perspective for you to analyze the impact of raw materials on the downstream supply chain network, and their effects on the creation and delivery of finished goods and potential root causes like extended production lead times.Inventory projection to give you visibility into forward-looking KPIs like uncovered demand, excess supply, and days until stockout.A management dashboard to surface procurement, production, sales, and inventory metrics in an aggregated, accessible manner.The Supply Chain Network Visibility app is a premium app and requires an additional licensing fee. Talk to your Celonis account team to arrange this. For the app documentation, see Supply Chain Network Visibility app - object-centric.

Multi-sliders in Process Explorer (2024-05-29) 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 object or connection appears as a different slider and is color coded to match the objects in the process graph. For more information on using multi-sliders, see Multi-object Process Explorer. Moving a slider up will add the next most common event or connection for that specific object, while sliding down removes the least frequent event or connection that is currently displayed for that object. For example, you can adjust the slider for one object upwards to add the next most frequent event for that object to the graph while the remaining objects are not changed. However, if the event being added does not connect to the events currently displayed for this object, additional events will be added to connect the event being added. If the event being added is shared with other objects, it is only added for the object corresponding to the slider you adjusted. However, for the other objects, this event will display empty circles to indicate that it is not included. If a slider has been used to explore the current process, the colored square corresponding to that object will be highlighted with a blue border, even if the multi-slider is collapsed (see the middle object in the screenshot below). This indicates that events or connections have been added to the process flow currently shown.

JDBC Extractor version 2.97.1 (2024-05-29) Type casting between integer and float data types with Oracle databases With this version of the extractor, you can now configure type casting between Integer and Float data types when setting up your Oracle extraction tasks. To learn how to connect to JDBC databases, see: Connecting to a database. And for an overview of supported databases and their features (including Oracle), see: Supported database connections. 

Material Allocation app (object-centric) version 1.1.0 (2024-05-28) Compatibility changes to KPIsIn this version of the object-centric Material Allocation app, we’ve made some changes to KPI names in the Knowledge Model to maintain compatibility with the Knowledge Models for other Inventory Management apps. If you made customizations to the KPIs in an earlier version of the app, you’ll need to reapply these to the renamed KPIs. For the instructions to update the Material Allocation app, see Updating the object-centric Material Allocation app.

Improvements in the perspective builder (2024-05-28) We're upgrading the perspective builder to make it easier for analysts to build custom perspectives for processes. You'll see these changes in your user interface soon, on the Perspectives page in the Objects and Events UI. You can now click an object type in the perspective or the object list to select it. You’ll get an object details panel where you can view and edit the other object types that are related to it in the perspective. There’s also an Exclude button to exclude the object type. (Previously, when you clicked an object, you’d get the option to exclude it from the perspective.)When you select an object, we’ll put the focus on it by highlighting it and centering the graph on it, and collapsing multiple relationship lines between pairs of objects into a single line. By default, we'll also only show the objects adjacent to your selected object. You can change that setting in the display options.We've simplified the flow and reduced the number of clicks to add an object or choose a strategy for a relationship.You can now include and embed the same relationship, and we've made it clearer which is which.We’ve put in some new display options that make it easier to show only the things that are relevant to you. For the perspective builder documentation, see Creating custom perspectives and event logs.

Extract data from columns with localized values with SAP Ariba Extractor (2024-05-27) If you’re using SAP Ariba’s Master Data Retrieval API to extract data from master data tables, our extractor now gets data from columns with localized values (for example, Name_en, Description_en), which it couldn’t do before. We’ve added these columns to the column configuration in your existing extractions, so you don’t need to change them. You do need to update the metadata, either by running a full load of the data model, or by running a delta load with the option “Include metadata changes”. Scheduled delta loads that don’t have that option selected will fail until you’ve done that. The tables where you’ll get the additional columns are: Accounts, Account_types, Bankaccountidtype, Bankaccounttype, Bankidtype, Chargetype, Commoditycodes, Commonsuppliers, Costcenters, Countries, Currency, Generalledgers, Glindicator, Groups, Incoterms, Itemcategory, Languages, Localeids, Partitionedcommoditycodes, Paymentmethodtype, Paymentterms, Procurementunits, Taxcodes, Uoms, Users. For the extractor documentation, see SAP Ariba.

ServiceNow Extractor (2024-05-27) Configuration Option for the "Order-by" parameter The User Order-by Parameter in Request configuration option enables the use of the ordering parameter in all API requests for an extraction. Enabling this option ensures data integrity by preventing missing records and duplicates. However, it will also lead to a longer extraction time and an increased load on the source system. To help minimize this impact, we recommend that you apply partitioning to reduce both the peak impact and the duration of the system being occupied or increase the batch size, which increases the peak impact but decreases the duration of the system being occupied. 

Process Management (formerly Symbio) (week of 2024-05-27) Seamless navigation from the Celonis Platform to Process Management productsTeam admins can quickly and easily enable seamless access to Process Management products.Once enabled, users signed in to the Celonis Platform can navigate to Process Management products from the Celonis Platform Navigation bar.Users with analyst and admin permissions can access Process Designer. If also enabled, all users can access Process Navigator.For more information, see Enabling access to Process Management products. Note: Users must have a Process Designer or Process Navigator account to access Process Management products. 

Removal of package 'Created By' avatar from Studio (2024-05-27) Based on valuable customer feedback, we have decided to temporarily withhold the avatar feature indicating the ‘creator’ of package in Studio and Apps. This decision enables us to effectively address our customers’ needs. The feature will be re-evaluated and reintroduced in a manner that better meets the expectations of our users.

Procurement Starter Kit (object-centric) version 1.1.0 (2024-05-24) Deep dive into planning parameters and contract leakage In this version of the object-centric Procurement Starter Kit, we've extended the use cases in the Process Cockpit:The new Planning Parameters Deep Dive lets you identify discrepancies between procurement lead times and actual lead times, so you can see when you need to update your planning parameters. This view is also available in the Validation Cockpit.The Contract Usage Deep Dive now includes the Contract Leakage value opportunity, like the case-centric version of the Starter Kit does. For the Procurement Starter Kit documentation, see Procurement Starter Kit - object-centric.

Disable and re-enable Celonis catalog transformations in object-centric process mining (2024-05-22) You can now disable individual transformations installed from the Celonis catalog, and re-enable them again at any time. Use this function if you’ve installed a Celonis catalog process, but there are some of the Celonis object types and event types that you don’t need, or don’t have data for, or are building with data from a set of transformations for another source system. You can re-enable the transformation at any time if you do need it in the future. Previously, you would have needed to create a full overwrite for the transformation to produce an empty result set, so if you have any of these, you can get rid of them and disable those transformations instead. The toggles to disable and enable the Celonis catalog transformations are available in the listing on the Transformations page of the Objects and Events user interface. You’ll also get them if you view the transformations for an object type or event type in the Objects or Events pages. By default, your installed Celonis catalog transformations are all enabled. For the instructions to install the Celonis catalog transformations, see Quickstart: Extract and transform your data into objects and events.

Changes in the process of creating Action Flows (2024-05-16) We've added some new settings to the Action Flow creation flow. Now, when creating an Action Flow, in addition to providing the name and the description for your Action Flow, you also have to select the Automation type, and (optionally) define the number of consecutive errors, after which the Action Flow gets deactivated. There are two automation types to select from: automatic and manual. If the automation type is set to manual, the Action Flow has to be started manually and its scheduling will be set to On-demand. This scheduling type is necessary to start the Action Flow using an Action button or a Task. If the automation type is set to automatic, the Action Flow will be executed according to a set schedule. and it will be set to According to scheduling. Please note that adding a Trigger or a Webhook as the first module will automatically change the scheduling to Immediately. Apart from selecting the automation type, you can also define the number of consecutive errors after which the Action Flow is deactivated. Both settings can be changed after the Action Flow has been created. 

Multi-object event counts in Process Explorer (2024-05-15) The Process Explorer interface now shows the event counts broken out by object type, allowing for a more accurate count for shared events. This new feature shows the total count of the current metric for each object type next to the colored square corresponding to that object type in the process flow. Previously, the event count shown was across all objects and users were required to view the event details to see the individual event count for each object type.  This update also fixes the issue with event counts displaying as “No Data” that was caused by adjusting event names via PQL statements in one or more object types.

JDBC Extractor version 2.96.1 (2024-05-14) Extract from Google BigQuery external tablesWith this version of the extractor, if you’re extracting data from a Google BigQuery database, you can now get data from external tables, which reference data stored outside BigQuery, as well as from standard BigQuery tables. For the instructions to upgrade the JDBC Extractor, see Updating on-premise JDBC extractor.

Team-to-team copy of data pools and Studio packages in general availability for Premium Sandbox subscribers only Our team-to-team copy feature is now in general availability for Premium Sandbox Subscribers. Team admins can now bulk copy data pools and Studio packages between Celonis Platform teams. By creating and saving a copy run, you no longer need to manually recreate and reconfigure your data integration and Studio content in additional teams. When copying content between teams, the following conditions apply: Data pools: The latest released version of your data pool is copied where available. If your data pool exists in draft mode only, the draft will be copied. This excludes any data integration schedules you have configured in your data pool, however any time based schedules from the target team are reapplied to the new team. This means that the times for productive schedules aren't impacted.Packages: Packages with Action Flows can be copied but the Action Flows are not updated in your target team. For more information about the Team-to-team copy feature, see: Team-to-team copy. 

Oracle Fusion BICC Extractor (2024-05-13) Full support for timestamp columns (Limited Availability)The Oracle Fusion BICC Extractor now extracts time as well as date information from timestamp columns. New extractions will automatically load the additional data. To update data that's already been extracted, run a full load after 13 May, when the new version of the extractor will be on all clusters. For the extractor instructions, see Oracle Fusion Cloud BICC. The BICC Extractor is in Limited Availability status. To get access as an early adopter, ask your Celonis point of contact.

Accounts Payable Starter Kit, object-centric (version 1.1.0) and case-centric (version 1.3.0) (2024-05-10) New Paid On-Time formula, more KPIs and inefficiencies addedFor these new versions of the object-centric and case-centric Accounts Payable Starter Kit, we’ve rebuilt the ‘Paid On-Time’ formula and classification. The new method classifies invoices into Early, On-Time, and Late, and distinguishes between cash discount and non-cash discount invoices. The new calculation dynamically adjusts the due date per invoice line depending on the cash discount amount taken, removing the possibility of an invoice being flagged as an early payment due to a cash discount being taken.For Invoices with no cash discount taken, the latest payment term is used to calculate the invoice due date.For Cash Discount Invoices, the amount taken is compared against the Cash Discount available in the payment terms.When the cash discount taken is equal or less than the middle payment term cash discount amount, then the middle payment term is used as the due date for the On-Time Payment calculation.When the cash discount taken is greater than the middle payment term cash discount, then the earliest payment term is used to calculate the Invoice due date. We’ve also added new KPIs and inefficiencies to the Days Payable Outstanding use case tab:Maximum DPO based on Best terms KPIMaximum DPO based on PO terms KPIUnfavorable PT mismatch (Inv/PO) InefficiencyUnfavorable PT mismatch (Inv/MD) InefficiencyAvg. Days Paid Early (only in the object-centric kit)Avg. Days Paid Late (only in the object-centric kit) In the case-centric kit, we’ve added profile views to all inefficiencies, except Duplicate Invoices. The profile views include information about available pre-built applications that can be used to resolve the inefficiencies, as well as possible root causes for them.For the documentation for the object-centric kit see Open Credit Memo app - object-centric, and for the case-centric kit see Open Credit Memo app - case-centric. 

Open Credit Memo app (object-centric) version 1.1.0 (2024-05-10) Enhanced credit memo details view, and alternative value realizationThe object-centric Open Credit Memo app’s Credit Memo Details profile view now includes more actions and a redesigned vendor overview, which lets users choose to view documents by company code or by vendor name. We’ve also redesigned the Validation and Value assessment view for easier and faster configuration, including an alternative value realization method that doesn’t require the augmented credit memo status. For the instructions to upgrade the app, see Updating the object-centric Open Credit Memo app.