Skip to main content

Celonis Product Documentation

Migration Guide: from Anomaly List to Execution Gap List

  1. Change your component type from `anomaly-list` to `execution-gap-list` and migrate any header settings:

    anomaly-list

    - id: AnomalyList
    type: anomaly-list
    settings:
      kpi: ON_TIME_PAYMENT
      name: Execution Gaps
          header:
                issue: Issue                    #Renames the table header for issue.
        kpi: "KPI"                            #Renames the table header for KPI.
        occurrences: "Invoices" #Renames the table header for occurrences.

    execution-gap-list

    - id: ExecutionGapList
    type: execution-gap-list
    settings:
      kpi: ON_TIME_PAYMENT
      name: Execution Gaps
          columns:
        issue:
          title: Issue          #Renames the table header for issue.
        kpi:
              title: "KPI"            #Renames the table header for KPI.
        occurrences:
                  title: "Invoices" #Renames the table header for occurrences.

  2. Move your flag definitions in the Knowledge Model from `record.customAttributes.flags` to `record.flags`

  3. In your anomalies objects in the Knowledge Model, migrate your kpiIds property to the kpis property.

    Before

    anomalies:
  - id: SYSTEMIC_BLOCKER_LATE_ENTERED_INVOICES
    displayName: Late Entered Invoices
    flag: LATE_ENTERED_INVOICES
    kpiIds:
      - ON_TIME_PAYMENT
    type: ANOMALY

    After

    anomalies:
  - id: SYSTEMIC_BLOCKER_LATE_ENTERED_INVOICES
    displayName: Late Entered Invoices
    flag: LATE_ENTERED_INVOICES
    kpis:
      - kpiId: ON_TIME_PAYMENT
    type: ANOMALY

  4. If you have been using the 'absoluteCalculation: true' property in any of your KPIs to influence the impact calculation in the anomaly list, you may now want to use a customer impact calculation instead.

    kpis:
  - id: IMPACT_FOR_PERCENTAGES                          # this used to be the default impact calculation in the anomaly-list component
    pql: "CASE WHEN {p2} > 0.0 THEN ({p2} - {p1}) / {p1} ELSE 0.0 END"
    format: "+.0%"
    displayName: impactPercentages
    parameters:
      - id: global
        defaultValue: 100
        displayName: Global
      - id: flagged
        defaultValue: 20
        displayName: Flagged
  - id: IMPACT_ABSOLUTE_RATIO                           # this used to be the impact calculation in the anomaly-list component for kpis with customAttributes.absoluteCalculation set to true
    pql: "{p2} / {p1}"
    format: "+.0%"
    displayName: impactAbsoluteCalc
    parameters:
      - id: global
        defaultValue: 100
        displayName: Global
      - id: flagged
        defaultValue: 20
        displayName: Flagged

Note

You can reference these custom impact calculations in your anomaly objects in the Knowledge Model.