Celonis Product Documentation

Display content rules are visual customizations of Studio components based on boolean conditions.

Display content rules apply a specific visual style to an object based on a specific logic. This logic is defined by users and contains a condition usually applied to a value. If the condition described in the logic is met, the style of the object can be changed. This means adding an icon or an avatar, adding borders or background colors, or changing the style of the object’s font.

Display content rules can be applied to the KPI Lists, Attribute Lists, Tables and in some cases, to Histogram components within Views. Display content rules must be first created in the Knowledge Model in order to be accessible from inside the View Components. In order to apply a display content rule to an object, the display rule must be added in the Styling rule dropdown for the object.

Display Content Rules are composed of three parts:

customObjects: 
  - id: DISPLAY_RULE_1
    displayName: Display rule 1
    customAttributes:
      - comparator: GREATER_THAN_OR_EQUAL     # comparator is used to compare value from ``DISPLAY_RULE.customAttributes.value`` to the value from PQL
        value: 1000       # value to compare. In case you use the comparator BETWEEN, you would define the value as such: '[8,15]'
        style: #styles to change the cell's appearance
          textColor: green #CCS collar or HEX code
          backgroundColor: "#FE4854"
          fontSize: 16px
          fontItalic: false
          fontWeight: bold

customObjects: 
 - id: DISPLAY_RULE_4
    displayName: Display rule 2
    customAttributes:
      - comparator: LESS_THAN
        value: 1000 
        style:
          textColor: red
          backgroundColor:"#FE4854"
          fontSize: 16px
          fontItalic: true
          fontWeight: bold
      - comparator: GREATER_THAN_OR_EQUAL
        value: 1000
        style:
          textColor: green
          backgroundColor: "#FE4854"
          fontSize: 16px
          fontItalic: false
          fontWeight: bold

Dropdown item components can be used to define breakdown items for your dropdown.

YAML example

customObjects: 
  - id: TIME_DROPDOWN
    displayName: Time Dropdown
    customAttributes:
      list:
        - name: DAY
        - name: WEEK
        - name: MONTH

The priority switcher allows you to set a Priority KPI as a company or department goal and pass it over as input for other components, e.g. to sort tasks and actions. As an example, task lists can be sorted according to the main objective to optimize towards. This objective is defined in form of a KPI that should change over time to a certain direction.

If the Priority Switcher is implemented in a View, it is displayed next to the title of the View.

In the priorities section of your record, add one or arbitrary priorities. Make sure that you are connecting the priority to an existing KPI. This link makes sure that the priority icon is displayed on a KPI. In case you don't want this link, you can enter a dummy KPI.

Priority switcher YAML example

records:
  - id: INVOICE
    displayName: Invoice
    priorities:
    - id: CASH_DISCOUNT_PRIORITIZATION
      displayName: Cash Discount
      pql: CASE WHEN "BSEG"."BELNR" IN ('0120205969', '9330002454', '5110056998',
            '5110055916', '5110055917', '5110052424', '5110056999', '5110052423')
            THEN 'Urgent' WHEN DAYS_BETWEEN(TO_TIMESTAMP(  '10012020'
            ,'MMDDYYYY'), ADD_MONTHS(PU_MIN("BSEG",
            "_CEL_AP_ACTIVITIES"."EVENTTIME", "_CEL_AP_ACTIVITIES"."ACTIVITY_EN" =
            'Cash Discount Due Date passed'),6)) < 0 THEN 'Low' WHEN
            DAYS_BETWEEN(TO_TIMESTAMP(  '10012020' ,'MMDDYYYY'),
            ADD_MONTHS(PU_MIN("BSEG", "_CEL_AP_ACTIVITIES"."EVENTTIME",
            "_CEL_AP_ACTIVITIES"."ACTIVITY_EN" = 'Cash Discount Due Date
            passed'),6)) < 5 AND DAYS_BETWEEN(TO_TIMESTAMP(  '10012020'
            ,'MMDDYYYY'), ADD_MONTHS(PU_MIN("BSEG",
            "_CEL_AP_ACTIVITIES"."EVENTTIME", "_CEL_AP_ACTIVITIES"."ACTIVITY_EN" =
            'Cash Discount Due Date passed'),6)) >= 0 THEN 'Low' ELSE 'Medium' END
      kpi: LOST_CASH_DISCOUNT

KPIs need to be activated to be displayed in the Priority Switcher. To do this, add the customAttribute "active: true". This will make the KPI selectable in the priority switcher.

YAML example

kpis:
  - id: LOST_CASH_DISCOUNT
    displayName: Lost Cash Discount
    customAttributes:
        absoluteCalculation: true
        active: true #required Defines if the KPI should be considered by the Priority Switcher
    pql: ( SUM(CASE WHEN MONTH("BKPF"."CPUDT") = 4 THEN "BSEG"."SKFBT_CONVERTED" *
        "BSEG"."ZBD1P"*1.1 * 0.01 ELSE "BSEG"."SKFBT_CONVERTED" *
        "BSEG"."ZBD1P"*0.01 END) - SUM(CASE WHEN "BSEG"."ZBD1P" > 0 AND
        "BSEG"."SKFBT_CONVERTED" > 0 THEN  "BSEG"."SKNTO_CONVERTED" ELSE NULL END)
        ) * 2
    filterIds: []
    format: $.3s
    breakdowns: []
    aggregations: []
    parameters: []
    desiredDirection: DECREASE
    priority: false
    type: KPI

Use the Recommendation component on Views to list out different recommendations on how to improve a KPI. Details about the recommended improvement measures can be provided in Profile Views.

Recommendation List Components are defined in the customAttribute section in KPIs.

YAML example

kpis: 
  - id: TOTAL_REVENUE
        displayName: Total Revenue
        customAttributes:
        recommendations:
          - id: RECOMMANDATION_REVENUE
                displayName: High volume of outstanding order shipments
                filter: CASE
                firstKpi: null
                secondKpi: null
                process: RM
          - id: RECOMMANDATION_REVENUE_2
                displayName: High inventory for low-demand products
                filter: CASE
                firstKpi: null
                secondKpi: null
                process: RM