Celonis Product Documentation

To start with the variable configuration, please go to the Knowledge Model (KM).

Go through the variables section in the view mode and validate whether the input used for the variables is correct for your business needs. To view all variables in use, you can navigate to the variables section of the KM.

For the apps, only non-auto-generated configurations are used, so you can disable the auto-generated definitions. In some cases, variables are used are for storing values (strings, integers, etc.) that are used inside of KPIs and inefficiencies, such as the Most Favourable Payment Term, for storing target and benchmark values of KPIs and frequently used activity names like the Record Goods Receipt activity.

Some variables are more important than others to update, in the sense that the business logic of the app will not work if they are not set correctly. An example are the variables that reference different fields and activity names, e.g. the ‘Record Goods Receipt’ activity.

However, If you identify some variables that need to be adjusted, you can easily update them directly inside of the variable part of the KM visual editor. Other variables are stored in the plain text variables section of the package settings. These variables can also be changed if needed and are only affecting the package where they are defined.

In the Knowledge Model, runtime variables are used to allow for better maintainability and bulk changes. In any App you would need to review and validate the runtime variables that appears on this section. However, the Starter Kit has the Validation Cockpit that is used to do this exercise.

Some of the existing runtime variables that can be validated across the Validation Cockpit are the following:

The business logic is packaged into formulas (KM KPIs) to reuse in the different parts of the app or inside of other KPIs/formulas to make the setup more concise.

These PQL-statements define the calculations of KPIs, filter statements on your data, and inefficiencies.

Hence they are one of the most important parts of the app.

To give you an example, the formula FORMULA_TOUCHLESS_ORDER is used in many different places like filters (FILTER_TOUCHLESS_PO), records and it attributes (PO_ITEMS.TOUCHLESS_CLASSIFICATION), KPIs (KPI_PO_ITEM_TOUCHLESS_ORDER_RATE_THIS_MONTH, KPI_PO_ITEM_TOUCHLESS_ORDER_RATE_LAST_MONT, KPI_PO_ITEM_TOUCHLESS_ORDER_RATE, KPI_PO_ITEM_TOUCHLESS_ORDER_COUNT) and it could be also used on flag as well.

So by adjusting the underlying business logic in that one place, you adjust the business logic for all KPIs and related definitions at once.

This list is not exhaustive and should be checked inside of the knowledge model. Make sure to also check nested formulas that might be used within the listed KPIs below. You can identify by the prefix whether it’s defined as KPI or formula.

In case you update the underlying business logic or used variables, please make sure to also update the documentation for the business users in the Documentation folder.

You should also check that other objects make sense for your deployments, like filters and record attributes. This can mostly be achieved by using the visual editor and looking for the orange alerts that indicate errors or going into the YAML, like the examples below: