Product Updates

Workforce Productivity (powered by Task Mining) (2023-10-30) Everyone can scale projects up to 2500 concurrent users and 6 months of data (General Availability) After our successful Limited Availability phase, we’re giving all customers of Workforce Productivity (powered by Task Mining) the capability to create projects with up to 2500 concurrent users, and analyze on average 6 months of historical data. Selected regions will see the new capability immediately, and everyone will get it on 30 October. Subject to licensing, you’ll benefit from the new user limit whenever you create a new project. You’ll also see that the package’s new delta architecture processes incoming data ready for analysis typically within 1 to 3 hours. Our new views simplify all the analysis features available in the previous version of the package. You’ll also get the Team Insights view which lets you calculate metrics for a subset of defined users, such as teams, regions, or roles. Because your existing projects are built on the older data model, we can’t migrate them automatically. You won’t see the new user limit, views, and processing speed for existing projects. If you want to upgrade and scale up an existing project, you’ll need to set it up again as a new project and manually adapt the views and analysis to work with the new schema. If you’d like to do this, get in touch with your Celonis point of contact. The 6-month average time for historical data analysis is based on the maximum permitted number of users sending a typical amount of Task Mining events daily. The actual limit is 1.6 billion events, so if you have fewer users in your project or they send fewer events than expected, you can analyze the data for a proportionally longer timeframe. We might also be able to help you in certain scenarios to roll out beyond the upper limit of 2500 concurrent users. Realm-specific limits on the number of concurrent users might affect your maximum scalability. To learn more about Workforce Productivity (powered by Task Mining), see Task Mining. 

Updates to SAP Ariba Extractor (2023-10-18) Extract EventSummaryFact table with Sourcing API We’ve added support for extracting the EventSummaryFact table through the Sourcing API. This table provides additional events and timestamps for use cases in the sourcing domain. If you have a connection to the Sourcing API, you’ll see the table in the extraction configuration, and you don’t need to make any changes. See SAP Ariba Connection for the Ariba Extractor documentation. Supported API Endpoints and available Tables lists the tables and columns that you can extract.

Bulk copy Studio packages and data pools between your EMS teams - Limited Availability (2023-10-12) With our new team-to-team copy feature you can pick packages and data pools to copy from one EMS team to another. The feature can check for any missing dependencies on other items that you didn't select for copying, and add them automatically. When you've set up a batch copy, you can rerun it whenever you want - we keep a log of both successful and failed runs and track progress while the copy is running. For data pools, the team-to-team copy feature doesn’t copy over your extracted and transformed data, just the configuration for the data pool - so you can use it to transfer a sandbox setup to a production team. You can read more at Copying multiple assets between EMS teams. Note that packages with Action Flows can’t be copied. The team-to-team copy feature is in Limited Availability status. If you want to try it out, ask your Celonis EMS contact.

Process Sphere version 0.8 (2023-10-11) Process Sphere's new user journey enables you to create a target model by mining a selection of "healthy" variants from the as-is behaviors shown in your data, and editing them into a to-be model that describes how your process should behave. You can then explore how the actual behaviors in your data deviate from the desired behavior in your target model. Process Sphere calculates what the impact of each deviation is - especially on the throughput time - and how often it occurs. You can filter your data at the mining, modeling, and exploration stages to limit the scope if you want to. We've enhanced Process Sphere's performance so the number of object types and event log entries is no longer limited, though the row limit for the underlying data still applies. For instructions and all the details, see the Process Sphere documentation.

Translate your apps into multiple languages in Studio (2023-10-09) Use our new localization feature to provide multi-language support for your apps. You'll find a Translations tab in the package settings - go there and click Enable Translations to activate the feature for that package. You can pick the app's default language and activate any of the nine supported languages. Then work with your translations in a CSV file or directly in Studio. For Knowledge Models and Views, we capture all attributes that you haven't yet translated and flag them for you. There's also a preview button so you can view translated assets in the alternate languages. When you've published the package, end users see the app in the language set in their EMS profile. See Translating Studio Apps. for more information. 

Upcoming changes to Skill availability (September 2023) From October 5, 2023, some less-used Actions for Skills that you can build using Action Flows will no longer be available in teams by default. They'll still work in your existing apps, you just can't use them in new ones. We encourage you to use Action Flows going forward. The items that won’t be available by default are the Webhook sensor, and the following Actions: Automation Anywhere (Agent), Blueprism (Agent), Coupa, Create Alert (Celonis), Update New Attribute (Celonis), Reload Data Model (Celonis), Firestart (Agent), Gmail, Gsheet, Gcalendar, Happyfox, Jira cloud, Jira (Agent), LeverX (Agent), Microsoft PA, Microsoft Teams, Oracle (Agent), Office 365, Salesforce, Salesforce (Sandbox), ServiceNow, Slack, SOAP, SAP (Agent), Trello, UiPath, UiPath (Agent), Workato, Webhook. Also, all the older and deprecated apps and actions that have already been de-listed won’t be available by default. If you can't move to Action Flows right now, or there's a particular Action in this list that you rely on, contact the support team at celopeers.com/s/support. We’ll also be enabling some Sensors and Actions for Skills by default for all teams. The Machine Learning Sensor, Manual Sensor, and Smart Sensor will be available by default, and the following Actions: the Execution Output, Filter, Loop, and Router system actions, and the Celonis actions Create PDF Report, Create Task, Email by Celonis, Email (SMTP), Execute Action Flow, Execute ML Notebook, Execute Process Automation Skill, Get Assignee, Get Task(s), Query Data Model, Update Augmented Attribute, Update Task(s), Write Data to Table, and Write Data To Table (Continuous Data Push API).

Migrate now from Process Analytics to Studio Analysis (September 2023) Studio Analysis is replacing Process Analytics. If you’re still using Process Analytics, migrate your analyses to Studio Analysis by September 30, 2023 as explained in Migration Steps. We’re removing access to Process Analytics on or after October 31, 2023. You’re likely to have Process Analytics on your EMS team if you became a Celonis customer in April 2021 or earlier. If you don't have Process Analytics on your EMS team, or if you are on Celonis 4, no action is required. To check, look for the Process Analytics icon in the navigation bar. Process Analytics and Studio Analysis have the exact same look and feel, so you can resume working with your analyses in Studio without any additional training. Studio also has the latest capabilities and user experiences in app-building and automation. See Process Analytics vs. Studio for a feature comparison and tips for Process Analytics users.

Open Credit Memo App for Accounts Payable version 1.0.1 (2023-09-26) In-app validation, configuration, and value framingThe Open Credit Memo app has a new Validation and Value Assessment view, to help you understand and validate the business logic step by step, and frame the use case’s value before you set up the app. We’ve also added two new quick filters to the Open Credit Memos tab, “Relevant Credit Memos” and “Irrelevant Credit Memos,” to filter the Action View using the scope that you define during the validation process. There’s some smaller enhancements and fixes too. When you update the app, you might see fewer credit memos than you expect, because we’ve pre-set a scope filter for you. If you want to see the full scope, go to the Settings view and remove all the restrictions. Use the validation process in the new view to define an appropriate scope filter for your business needs. For the app documentation, see Open Credit Memo App Installation.

SAP Ariba Extractor (2023-09-25) Enhancements to Catalog Content APIWe’ve added support for extracting the SupplierPartID and IsPreferredItem columns from the CatalogsItems table that’s available through the Catalog Content API. The Extractor also now automatically avoids requests for items from the CatalogsItems table where the supplier ID is unspecified, which can lead to extraction failures. See SAP Ariba Connection for the Ariba Extractor documentation. Supported API Endpoints and available Tables lists the tables and columns that you can filter.

SAP S/4HANA Process Connectors version 4.0 (2023-09-25) Data Model improvements and added featuresWe’ve upgraded the SAP S/4HANA Process Connectors for Accounts Payable, Accounts Receivable, Purchase to Pay, and Order to Cash, to match the capability of the SAP ECC Process Connectors. The new 4.0 versions of the SAP S/4HANA Process Connectors come with improved Data Models, and they now include the Delta Transformations, Delta Data Model Load, and Replication Cockpit features. You can download the connectors from the Marketplace, and you can get the reference documentation for them using these links: Accounts Payable - SAP S/4HANA Accounts Payable Process Connector Documentation (docx)Accounts Receivable - SAP S/4HANA Accounts Receivable Process Connector Documentation (docx)Purchase to Pay - SAP S/4HANA Purchase to Pay Process Connector Documentation (docx)Order to Cash - SAP S/4HANA Order to Cash Process Connector Documentation (docx) 

JDBC Extractor version 2.86.0 (2023-09-22) Conversion, metadata, and filtering improvements We’ve enabled STRING to DATETIME conversion for BigQuery and Trino.For Oracle, we’ve improved the query for the INFORMATION_SCHEMA metadata source.The Extractor now recognizes quotes in the filter statement.We’ve made some security improvements and fixes. Your Java version must be at least Java 17 for this version of the JDBC Extractor. If you haven’t upgraded yet, follow the steps in How do I update an on-premise extractor?

Recovery codes for your Celonis ID (2023-09-21) We’ve introduced recovery codes that serve as a backup authentication method for your Celonis ID, in case you lose access to the devices you use for two-factor authentication. You can only generate recovery codes when you're logged into your Celonis EMS account, so as a safety measure you should generate them as soon as you can, because you wouldn’t be able to after losing your second authentication factor. For instructions to generate recovery codes, see Recovery codes.

SAP ECC Purchase Requisitions Process Connector (2023-09-18) Merged with SAP ECC Purchase to Pay Process Connector version 4.0Because the SAP ECC Data Model for Purchase Requisitions was nearly always used alongside the Data Model for Purchase to Pay, we’ve merged it into version 4.0 of the SAP ECC Purchase to Pay Process Connector. We’ve added the Delta Transformation and Replication Cockpit features to it, and used staging tables for a performance enhancement. (There are also some minor changes to the Purchase to Pay Data Model to improve the purchase requisition and contract recommendation information.) The standalone SAP ECC Purchase Requisitions Process Connector is now deprecated, and we won’t make any future updates to it. From now on, for new installations that need a process connector for Purchase Requisitions, install version 4.0 of the SAP ECC Purchase to Pay Process Connector instead of the standalone SAP ECC Purchase Requisitions Process Connector.

Views (2023-09-14) Save bookmarks for ViewsYou can now save bookmarks with your preferences for a View (including filters, selections, and component states), and share them with your team. Use the bookmark icon in the top right area of a View to create, share, access, and manage your bookmarks. 

Triggers (2023-09-13)Enhancements to Trigger subscriber management in Knowledge ModelThe Trigger overview page in a Knowledge Model now shows you how many subscribers each Trigger has. You can click on that field to add a new subscriber for the Trigger - either an Action Flow or (in Limited Availability) Task Type - directly from the overview page. See Triggers for their documentation.

Intelligence API version 1.14.0 (2023-09-11) New filter operandsYou can now use the operands IS, IN, CONTAINS, STARTSWITH, and ENDSWITH in filter expressions. For the filter documentation, see Intelligence API Features - Filtering.

Object-centric process mining (2023-09-08) Terminology change: “projections” to “event logs”Following feedback from our early adopters of object-centric process mining, we’re discontinuing the term “projections” for the case-centric event logs that you can create from perspectives. We’ll use the familiar term “event logs” instead from now on, so it’s easier to identify them as what you need to use with case-centric apps and views. The revised concept topic explaining perspectives and event logs is at Perspectives.

JDBC Extractor version 2.85.0 (2023-09-01) Changes for Snowflake, BigQuery, and Microsoft Windows users The JDBC Extractor now escapes wildcards in Snowflake metadata calls to improve load.We’ve made some internal upgrades to the JDBC Extractor’s libraries. If you’re linking the BigQuery driver, you’ll need to exclude all SLF4J jar files from the driver package.On Microsoft Windows, we’ve changed the JDBC Extractor’s dependency from the Microsoft Visual C++ 2010 Redistributable Package to the Microsoft Visual C++ 2015-2019 Redistributable Package (x64). Install that package when you install this version of the JDBC Extractor. Your Java version must be at least Java 17 for this version of the JDBC Extractor. If you haven’t upgraded yet, follow the steps in How do I update an on-premise extractor?

Wildcards no longer require a backslash in PQL (2023-08-30) When you’re searching columns in the OLAP table or during attribute selection, and using the % (percent) and _ (underscore) characters as wildcards, you no longer need to use a backslash to escape them. If you search for text that contains the % or _ characters, you now need to prefix them with a backslash to use them literally. See ​LIKE​​ for the function documentation.

Upcoming changes to Skill availability (August 2023) From October 2, 2023, Skills that have an equivalent Action Flow module won't be available in teams by default. They'll still work in your existing apps, you just can't use them in new ones. We encourage you to use Action Flows going forward. The Skills that won’t be available by default are the Webhook sensor, and the following actions: Automation Anywhere (Agent), Blueprism (Agent), Coupa, Create Alert (Celonis), Update New Attribute (Celonis), Reload Data Model (Celonis), Firestart (Agent), Gmail, Gsheet, Gcalendar, Happyfox, Jira cloud, Jira (Agent), LeverX (Agent), Microsoft PA, Microsoft Teams, Oracle (Agent), Office 365, Salesforce, Salesforce (Sandbox), ServiceNow, Slack, SOAP, Email (SMTP), SAP (Agent), Trello, UiPath, UiPath (Agent), Workato, Webhook. Also, all the older and deprecated apps and actions that have already been de-listed won’t be available by default. If you can't move to Action Flows right now, or there's a particular Skill in this list that you rely on, contact the support team at celopeers.com/s/support.

Migrate now from Process Analytics to Studio Analysis (August 2023) Studio Analysis is replacing Process Analytics. If you’re still using Process Analytics, migrate your analyses to Studio Analysis by September 30, 2023 as explained in Migration Steps. We’re removing access to Process Analytics on or after October 31, 2023. You’re likely to have Process Analytics on your EMS team if you became a Celonis customer in April 2021 or earlier. If you don't have Process Analytics on your EMS team, or if you are on Celonis 4, no action is required. To check, look for the Process Analytics icon in the navigation bar. Process Analytics and Studio Analysis have the exact same look and feel, so you can resume working with your analyses in Studio without any additional training. Studio also has the latest capabilities and user experiences in app-building and automation. See Process Analytics vs. Studio for a feature comparison and tips for Process Analytics users. Process Analytics End of Life has full details and FAQs for your migration.

Task Mining Desktop Application version 2.13.0 (2023-08-31) Choose custom patterns for data redaction You can now configure the Task Mining Desktop Application to redact personally identifiable information (PII) before data is sent to Celonis EMS. Previously, you needed to either skip the whole data point, or create a custom SQL transformation to redact the data in Celonis EMS after it had been sent. Now, you can use the desktop Configuration Editor to set up regular expressions to identify and mask sensitive content such as credit card numbers or email addresses. You can choose which data columns each regular expression is applied to, and what the data is replaced with before it’s sent. See Data redaction for all the details.

Autosave indicator in Analysis (2023-08-30)When you’re editing an Analysis, all your edits are automatically saved. We’ve added an autosave indicator so it’s easier for you to see when the save is happening (a loading icon), if it failed (an error icon), and if it succeeded (a success icon). You can hover over the success icon to see the time of the last successful autosave. You can also now choose to save the Analysis manually, which adds a new version to the version history (see Autosave indicator, but you don’t have to do this - we’ll still save automatically.

Content-CLI (2023-08-24) Attention: YAML migration affecting Content-CLI exportIn this release of Content-CLI we’re changing some of the configurations for the YAML and JSON parsers used to export packages and assets. For each of your assets and packages, the next time you use Content-CLI to export it and push it to Github or another version control system, the file comparison (diff) will show the changes resulting from the migration. For JSON content, the content will be pretty-printed.For YAML content, multiline strings will have escaped characters unless you’ve used block scalar format with an indicator for the literal style (|) or the folded style (>). When you’re writing a multiline PQL query or another multiline string, we recommend using literal style for the best experience in the YAML editor, and using newlines in visual editors. Here’s an example of literal style: pql: | AVG(CASE WHEN "ACTIVITY_TABLE"."USER_TYPE" = 'A' THEN 0 ELSE 1 END)  

Network Explorer 0.8 (2023-08-21) Explore and visualize the dimensions of object to object relationshipsNetwork Explorer is a powerful visualization method to examine how objects are related across your business. Choose different dimensions to explore your object to object relationships by country, plant, material, distribution, or any other arbitrary dimension, and choose the KPI to display for each object. Network Explorer provides the visualization for the End-To-End Lead Times App for object-centric process mining, and supports advanced use cases such as material margins or carbon footprint calculations.  This new version of Network Explorer has been redesigned to offer dimension selection and drill-down capabilities for nodes. Network Explorer was formerly known as Network Explorer (Signal Link) or Signal Link Explorer. For the documentation, see Network Explorer.