Product Updates

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.

Baseline Date Optimizer App (case-centric) version 1.0.0 (2024-05-02) Identify and resolve unfavorable baseline date mismatches (Limited Availability) Our new Baseline Date Optimizer app provides you with a step-by-step guide to identify areas with frequent baseline date mismatches that impact free cash flow, or cause loss of cash discount. The app can compare the invoice baseline date against multiple other dates from both the invoice receipt and the goods receipt. When you’ve chosen an optimization strategy using this information, the Action View shows a prioritized list of open invoices based on the value potential, making it easy to use the best baseline date. For the full documentation, see Baseline Date Optimizer app - case-centric. The Baseline Date Optimizer app is built for the case-centric version of the Accounts Payable business process. You can download the app from the Celonis Marketplace - it’s in Limited Availability status, so click Request Access to request the package. When we’ve approved your request, go back to Marketplace, and the button will say Get it now, so you can download the package. 

Object-centric process mining (2024-04-25)Filter the lists of object types and event types We've added filters to the Objects page and the Events page in the Objects and Events environment, so you can browse a list containing only the object types or event types you want to work with. You can filter the lists by selecting one or more of these tags: The Celonis catalog process (you'll just see the processes you have enabled)The namespace for the object type or event type (Celonis, custom, or an app-specific namespace)Master data objects or helper objects You can pick more than one tag from a category, and we'll show object types and event types matching any of them. If you apply filters from more than one category, we'll show the object types and event types that match a selected tag in all of those categories (for example, Celonis object types in the Accounts Payable or Accounts Receivable process).The filters you set stay in place when you move from the Objects page to the Events page and back, and when you reload the page. You can bookmark a filtered view or share it with other team members by copying the browser URL.  The object-centric data model explains filtering and other ways to explore your objects, events, and relationships.

Add attributes in the transformations editor (2024-04-18) You can now add one or more new attributes to an object type or event type while you’re creating the transformation for it. You can use this capability if you’re working with the SQL transformation and identify an attribute that would be useful to have, but didn’t get added in modeling. You can add attributes to a custom object type, a custom event type, or a Celonis object type. Select the Add attributes button in the preview pane in the SQL editor to open a new window. Click Add to add each new attribute, name it, and pick a data type. When you save your new attributes, we’ll update the object type or event type, and warn you if other transformations for it besides the one you’re editing might be affected by your changes. For the instructions to work with the SQL editor, see Creating custom transformations.

Transformation Hub: Change to value tracking set up (2024-04-18) The process for setting up value tracking in Transformation Hub has been changed to allow you to see how the selected filters impact the KPI values. The set up process has been changed from three steps to two by combining the existing "Filter Data" and "Set up Formula" steps. In this new version, you select a date column and filters on the same screen as where you select KPIs. So when you choose KPIs, Transformation Hub generates a preview of how your filter selections impact the KPI values. Previously, the effects of your filters on the KPIs were not shown which led to incorrect selections and no value being tracked.  For more information on the complete setup process, see Setting up value tracking.

Studio Enhancements are Generally Available! 🚀 After a successful Limited Availability phase with over 80 customers, many positive testimonials and the latest feature additions … We’re excited to announce that the Studio Enhancements are Generally Available! 🚀 You can now analyze your case and object centric data models and build sleek looking dashboards and applications on top of them with an intuitive, integrated and fast user experience! I would like to take this as an opportunity to thank our LA customers for their trust and helping us shape the first version of this product, as well as the huge team in Product and Engineering as well as our colleagues in Academy, Services and Value Engineering to make this happen. 🙏 Since this morning we are live with aUpgraded Studio experience 💅Updated navigation tools to find assets with an improved search functionality and the ability to pin the most important apps and restore them from trash.Better content management with guided creation flows and the ability to restore deleted assets from trash. ✨ Joyful View creation and editing - a step change in how users can build new apps! ✨Drag and drop interface to position components on Views with a flexible layout and multiple tabs. Components can be configured with an intuitive UI and easy-to-use chart templates.Filter bar integrated into any View that can be configured to filter on any data dimension.Actions integrated into tables to send emails, export content, and run action flows.Simplified, more intuitive interface with access to central knowledge definitions to build metrics.  🎯 And this is just the start - While we are going GA now, rest assured that we won’t stop here. You can expect many exciting features in the coming months as we will further improve the experience and move towards full feature parity and beyond compared to Analysis and legacy Views. We highly recommend to use the Studio and View Enhancements in new implementations where they already meet the needs to enjoy the new ease of use and flexibility. Want to learn more?📃 Visit the updated Studio and Views documentatio📽️ Watch our Analyst intro video 🎓 Take our Celonis Academy training track: Building Views in Studio.🗓️ Join our Studio team for a webinar series: Enhanced Studio Experience Series; Starting May 22🥜Follow the tag Studio to follow along of 30 days of knowledge nuggets about the new experience, starting tomorrow!

COALESCE validation change for custom transformations (2024-04-16) We've changed the way the SQL analyzer validates SQL statements that include the COALESCE() function. To ensure consistent behavior, all the operands for COALESCE should be of the same data type. If they aren't, COALESCE might return the result as a data type that you didn’t expect, causing downstream errors that are harder to troubleshoot.Previously, our SQL analyzer allowed mixed data types for COALESCE. From this week, it’ll return an error if you try to publish your object-centric data model with a statement like that in a custom transformation. The error message looks like this: Cannot infer return type for COALESCE; operand types: [....] Transformations that you already published won’t stop working, but you’ll see the errors when you next attempt to publish. In order to publish the transformations, you'll need to resolve these errors by changing each affected SQL statement to use the same data type for all the operands for COALESCE. For example, this statement mixes a column with the TIMESTAMP data type, and a timestamp represented using the STRING data type: COALESCE(timestamp_column, ‘2024-04-16’) You can fix this by giving the literal the correct data type: COALESCE(timestamp_column, timestamp‘2024-04-16’) For the instructions to work with custom transformations, see Creating custom transformations.   

Transformation Hub: Edit the framed value for an opportunity (2024-04-16) In Transformation Hub, you can now edit the framed value or the framed value link for a live opportunity. If you’ve started tracking the realized value, but you change your mind about the prospective value based on actual performance, resourcing changes, or a new insight, you can update the framed value to reflect your new expectations. For the feature documentation, see Transformation Hub.

Japanese characters in object types and event types (2024-04-10)When you create custom object types and event types, you can now use Japanese characters in the name of an object or event, and also in the names of its attributes. For the custom modeling instructions, see Creating custom object types and custom event types.

JDBC Extractor version 2.94.0 (2024-04-08) Delta loads now default to canceling if the metadata has changed For this version of the JDBC Extractor, we’ve fixed some issues with the recommended metadata change handling option while configuring delta extractions. With the default option (Option A), the delta load is canceled if the metadata from your source system changes compared to the already extracted data (for example, if new columns are added). You’ll need to do a full load or change the affected table manually.With the alternative option (Option B), the delta load runs with a warning message, but data for the new columns only appears in the newly loaded rows. Rows that aren’t in the delta load get null values in the new columns. Some users prefer this approach, but it does introduce a data inconsistency, and you should do a full load after getting this warning. For the instructions to update, see Installing and updating the on-premise JDBC extractor.

ServiceNow Extractor: Configuration Option for the "Order-by" parameter (2024-04-08) 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.  This option is disabled by default but can be enabled at the table level based on specific needs. This option can also be enabled via the extraction settings, which also enables it for all tables in the underlying extraction job.For the full extractor documentation, see ServiceNow Connection.

Use on-screen banners to alert users of updates (2024-04-04) As part of the Notifications section in Admin and Settings we have added a new feature that allow the admin of the team to create “in-product” notification banners. Once these notifications are created and published they become visible to all their users.This feature provides greater flexibility for admins when they want to communicate updates to their users. The updates might include: planned down-timedata load issuesgeneral business-related notifications We have also included a notification dashboard where admins can manage their published notifications. 

Any way to copy a data model from one data pool to another? For sure both DPs contains the same tables, we use them as development and production environments and we don't want to create again the new DM from scratch ;-)

New warning messages in the Data Model UI for Data Integration (2024-03-31) Previously, Data Integration concatenated all the warning messages that the PQL engine returned for the currently loaded Data Model into a single string, which made it hard to pick out individual messages. For better usability, we've separated these back out, and we now present the warning messages individually in the frontend. So from mid-March, you might spot some warning messages for your Data Models that you didn't know about before. If your Data Model was working before, it'll continue to work in the same way, so you don't need to take any action now. The warning messages might reference some problems in the Data Model that Celonis was handling automatically - for example, with the cardinality of relationships - and we'll continue to handle these. If you choose to action any of the mentioned changes, you might realize some improvements in your Data Model's load time. Ask your Celonis point of contact if you have concerns about anything in the messages, or want help to make the referenced changes.

Change the start position for a chart scroll bar (Limited Availability) (2024-03-28) In the new Studio experience, you can now select where users start from in the scroll bar for a chart. By default, the scroll position starts at the right for dates, and starts at the left for all other charts. You can override the default to make the scroll start at the right or the left (top or bottom for vertical charts).  For more information about the new Studio experience, see: new Studio experience (limited availability).

Recycling projects in Studio using trash can (Limited Availability) (2024-03-27) There's now a Trash feature in Studio, allowing you to declutter your Studio spaces and packages. After moving your space or package to the Trash, the items are kept for 180 days and then permanently deleted (unless manually recovered or permanently deleted prior to this).Click the Trash icon from your Studio spaces or package overview screens to view the items in your Trash:  To learn how to manage your existing Studio spaces, see: Spaces. And for more information about managing your packages, head to: Managing packages and permissions.