Skip to main content

Celonis Product Documentation

Anomaly List

Deprecation warning

This component is deprecated. Please use the new Execution Gap List component instead. (See also the Migration Guide: from Anomaly List to Execution Gap List.)

Introduction to Anomaly List

Use the "Anomaly List" component on Views to give your users a quick overview of all automatically detected anomalies in their system. It provides an overview of the defined KPIs, occurrences, and impact. Details of an Anomaly can be analyzed in Profile View.

This is what the component looks like:


How the impact is calculated

Let's say we have an on-time payment rate of 7% due to the slow approval rate. In all other cases, we detect an approval rate of 23% then the impact is getting calculated as the following:

(23-7) / 23 * 100 = -69%

This means due to the detected anomaly the process runs -69% worse than it could be when resolving the anomaly.

And here you can see the interaction with a profile view providing your business users more details of an anomaly.



Check out this community post to learn how others use the anomaly list.

Example configuration

Configuration of Knowledge Model.

Knowledge Model

    displayName: Late Entered Invoices
      - ON_TIME_PAYMENT #References a list of KPIs in the Knowledge Model. Make sure those KPIs have the attribute "desiredDirection:" defined, which is important for the impact calculation.
    type: ANOMALY
        knowledgeObjectId: SYSTEMIC_BLOCKER_LATE_ENTERED_INVOICES_OBJECT # This object will be later used when creating the Profile View

Configuration of component in View configuration


- id: Anomaly List
    type: anomaly-list
      kpi: ON_TIME_PAYMENT #required Deferences the KPI in the Knowledge Model. Also a parameter ${currentKpi} can be used.
      name: Execution Gaps #Defines the Title displayed above the component.
                issue: Issue #Renames the table header for issue.
        kpi: "KPI" #Renames the table header for KPI.
        occurrences: "Invoices" #Renames the table header for occurrences.

Configuration of Profile View:

Profile View

  key: Anomalie-Template
  appStoreBased: false
  key: AP_DEMO_SystemicBlocker_LateGoodsReceipt
  template: false
  name: Execution Gap - Late Goods Receipt
  knowledgeObjectId: SYSTEMIC_BLOCKER_LATE_ENTERED_INVOICES_OBJECT # references the knowledgeObjectId (see Knowledge Model configuration) for the respective anomaly
  profileView: true # defines that the it's a profile view
  order: 1