Skip to main content

Celonis Product Documentation

View Customizations

A general rule is that customizations should be avoided, if possible, to enable easier maintenance and to ensure that the new updates to the App can be installed without issues. Nevertheless, there are parts of the app that need to be adjusted in order to get it working, especially when the data model setup is different to the Marketplace template.

In the below section, we’ll have a look at the best practices on how to customize the application. In general, only the updates on the tabs structure are performed in the “Process Cockpit'' or "Validation Cockpit" views. All other updates are performed in the Base views or in the content views (=Tabs) embedded in the “Process Cockpit'' or "Validation Cockpit" views.

If something should be updated throughout the whole application, one of the Base views is the place to start in most situations (= bulk update). If a specific view should be customized, the content view itself is the place to go (=individual update).

Complete your customization with the useful resources:

Base Updates (Bulk Update)

As all components and layout in the Base View are inherited to the extending Views, all updates performed in the Base View are populated to the extending views. If the extending views have overwritten the configuration or the layout already the update is ignored in the extending view. So updating the Base is a powerful way to change general patterns in the application.

So let’s have a look at a few examples:

Update Layout

Let’s assume that the KPI List should be removed for all Process Cockpit Views.

  1. To do this, navigate to the Base View “Process Cockpit Base” and click on “Edit Mode”

  2. Navigate to the KPI list and click on the “eye” saying “Hide section”. Click on save and leave the edit mode.

  3. If you navigate to the extending views (e.g., Touchless), you will see that the KPI list is gone.

Update Components

The update of components works very similarly. So let’s assume you want to adjust the KPI list not to show some KPIs.

  1. To do this, navigate to the Base View “Process Cockpit Base” and click on “Edit Mode”

  2. Navigate to the KPI list and click on “Edit Component”

  3. Click on “Hide” for the items you want to hide.

  4. Click on save and leave the edit mode. If you navigate to extending views , you will see that all extending views show only the KPIs defined in the base view.

Extension Updates (Content View)

While the updates in the Base views provide potent updates to the general structure, it’s still essential to customize the individual view to show the most relevant information. You might have noticed that the App does this already out-of-the-box by using, for instance in the “Payment Terms” view, a different structure than the one in the base view. So, in case specific views should be updated individually, you should navigate to the Tabs folder and look for the respective view.

Creating a new Extension View from a Base

To better understand the advantages of the Base/Extension concept, the following section explains how to create an entirely new view focusing on a specific set of KPIs as defined in the Knowledge Model. Therefore, the already mentioned methods around Base/Extension Views are used to build a basic view.

To simplify the process, the following example will use some existing KPIs coming from the Knowledge Model that will result in a view allowing the business user to analyze the development of the “Return Rate” as well as the “amount affected sales orders”. This, however, will also work with any other KPI created in the Knowledge Model.

  1. To do this, first of all, create a new view in the same package where we store the other views of the Starter Kit App, ideally in the Tabs folder, called “Returns” (as an example) by clicking on the “+” icon in the folder.

  2. Select the Knowledge Model from the Dropdown and select the View Process Cockpit Base as the Base View for the new Extension View. Once the Base for the Returns view is selected, clicking the create button shows an exact copy of the base view in the Edit Mode.

  3. Switching to the YAML editor by clicking on the </> button in the top right corner results in basically an empty view without any Layout or Component definitions. All components you see in the View are inherited from the Base View. So far, nothing was overwritten by the Extension.

  4. To adapt the content to show the mentioned KPIs, all we need to do is change/add a few KPIs in the components. These would be:

    1. KPI List

    2. Trend Chart

    3. Drilldown table

  5. Once made the changes to the Base View, you can add new tables, charts depending on what you want to show for the Order Returns Process Cockpit View.