Skip to main content

The Celonis Studio is live!

We recently launched the Execution Management System and with it three Celonis-developed Execution Apps and three partner-developed Execution Apps (you can check them out in our EMS Store). But there are potentially hundreds more Execution Applications and Instruments still waiting to be developed. Thats why we have brought all the powerful analytics and automation capabilities of the Execution Management System platform together into the user-friendly Celonis Studio, a low-code development environment that we released in beta mid of October 2020. The Studio allows you to build, publish, and distribute execution apps & instruments from a single low-code interface. The Business Views tab allows your organization to access the apps & instruments youve built. To build an app or instrument, citizen developers can use the following building blocks: Analyses to identify execution gaps in your process (available now!) Analysis1600806 161 KB Views to provide a tailor-made experience for your line of business personnel from executives to individual contributors (available on request) view1448919 132 KB Knowledge Models to incorporate business context such as KPIs and execution gaps (available on request) knowledge model19201080 174 KB Skills to address execution gaps through automation, tasks, and next-best-action recommendations (available end of November!) Skill with ML Router (1)1600880 197 KB The Studio is released to all EMS teams and available for everyone to get started with execution instruments (creating packages with analyses). Learn how to build execution instruments with this getting started guide. The capabilities to build execution apps (incl. Views and Knowledge Models) are available on request. But first, take a look and get familiar with the new concepts by taking the App Creator Training course, available on our LMS platform. Furthermore, you find the full Studio documentation here. To get more details on which functionalities, features, and components are released for the Studio check out the release notes here. Looking forward to your feedback regarding the Studio! All the best Sabeth, Product Lead Celonis Studio, & the entire Studio Team!

Feature retirement announcement: Reload all Data Models within schedules in Event Collection

Dear data engineers in the Celonis community, At the beginning of this year, we have released a feature that allows you to specify which Data Models are to be loaded after a successful Data Job execution: https://help.celonis.cloud/help/display/CIBC/Specify+Data+Model+Loads+in+Data+Jobs+to+make+the+pipeline+more+efficient This feature allows you to have more control on which Data Models are loaded in your pipelines. This feature is used by many of you already which is great. However, they are still a lot of teams on our platform which choose to load all Data Models after a schedule execution which was the previous behaviour, but one which can be completely replaced with the new feature. The old feature to reload all Data Models after a schedule execution will no longer be available after January 15th, 2021. Therefore, we encourage everyone to change their pipelines as soon as possible in the following way according to your situation: Case 1 You have already adopted the feature to choose the Data Models in Data Jobs and you no longer use Reload all Data Models after a schedule execution Action: No action is required. Case 2 You have one or more schedules that reloads all Data Models after a schedule execution and you want to keep the pipelines exactly as they are. Action: Our recommendation is to create a new Data Job that contains all the Data Models of the Data Pool to which the schedule belongs and add this Data Model Data Job to the schedule. Afterward, remove the Reload all Data Models after execution flag within the schedule configuration. Case 3 You have one or more schedules that reloads all Data Models after a schedule execution and you actually want to reload only some Data Models after these schedule executions. Action: Add the desired Data Models to the last Data Job of the schedule or create a new Data Job with only the desired Data Model loads and add it to the schedule in the last position. Afterward, remove the Reload all Data Models after execution flag within the schedule configuration. In case you do not change your pipelines until January 15th, 2021 the schedules will still run, but they will not reload Data Models anymore unless they are specified within Data Jobs. Best regards, Leonid