Celonis Product Documentation

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 on Profile View.

For more details, please click here.

Use the "Attribute" component on Profile Views to give your users a quick overview of all-important attributes and KPIs for a specific object.

For more details, please click here.

Use the "Button" component on (Profile) Views to navigate your user to specific websites or trigger Skills.

For more details, please click here.

Use the "Chart" component to display content in visual form. Charts can have different visuals - line, bar, point, text, lollipop. It's possible to have multiple visuals on the same chart.

For more details, please click here.

Use the "Comments" component on (Profile) Views to allow your user to exchange information to process an object. Comments can be listed by using the "Activity History" component.

For more details, please click here.

Use the "Dropdown" component on (Profile) Views to allow your users to filter the entire View based on attributes or changing input variables which can be used e.g. for changing dimensions for other components.

For more details, please click here.

Use the "Embedded View" component on (Profile) Views to box Views inside Views. Optionally, parameters such as filters, selections or inputs can be passed. This makes embedded Views a powerful and versatile component. However, embedded Views are not immediately visible to your business users but oftentimes seamlessly fit in the parenting View.

For more details, please click here.

Use the "Global Search" component on (Profile) Views to allow your user to search by relevant attributes. The entire View will be filtered by the entered search term.

For more details, please click here.

Use the "Image" component on (Profile) Views to embed relevant images for your users. It can be used to display a company logo or any other image.

For more details, please click here.

Use the "Input Box" component to show a text entry field with a label that prompts the user to enter input. The input can be a string, number, time or date.

For more details, please click here.

Use the "Input Checkbox" component to show a checkbox with a label, which when selected will be activated, or deactivated. It is a great way to allow for user interaction.

For more details, please click here.

Use the "KPI List" component on (Profile) Views to allow your users to see the current value of a KPI. Furthermore, it can be used to set KPI targets as well as visualize benchmark information.

For more details, please click here.

Use the "KPI Bowler" component on (Profile) Views to allow your users to define and track the progress of their KPIs over time.

For more details, please click here.

Use the "Line" component on (Profile) Views to clearly separate content into different sections for your users to make the Views better understandable.

For more details, please click here.

Use the "Network Explorer" component to visualize a custom Graph from a variety of data structures.

For more details, please click here.

Use the "Process Explorer" component to show the most frequent activities and connections. Any number of Event Logs can be visualized. There are multiple types of transitions between Event Logs that can be defined.

For more details, please click here.

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.

For more details, please click here.

Use the "Quick Filter" component on Views to allow users to quickly filter on relevant attributes with as few clicks as possible.

For more details, please click here.

Use the "Sankey Diagram" component to show weighted networks, i.e. flows. They can be used to visualize Source to End connections: For a total amount, the diagram can show where it comes from and where it ends up, with possible intermediate steps. Or they can be used to visualize evolution: Nodes are duplicated in two or more groups that represent stages. Connections show the evolution between two states, similar to Chord diagrams.

For more details, please click here.

Use the "Table" component on (Profile) Views to give your users a quick overview about all relevant attributes. It supports a vast variety of configuration options.

For more details, see Table.

Use the "Task List" component on Profile Views to list all Tasks existing on a specific object, give details about them and display the options for a Task Action. It is typically used in Profile Views.

For more details, please click here.

Use the "Text" component on (Profile) Views to provide your users relevant information in text form. The component allows text and HTML.

For more details, please click here.

Use the "Time Filter" component on (Profile) Views to enable your users to filter the View by a selected date.

For more details, please click here.

Use the "Treemap" component on Views to display hierarchical data using nested rectangles. Size and color of the rectangles can indicate up to two KPIs.

For more details, please click here.

Use the "Waterfall Chart" component to display the cumulative effect of values.

For more details, please click here.

Use the "World Map" component to display distributions of a dimension across different countries worldwide.

For more details, please click here.

Display Rules is a shared component that can be used inside View components to create visual styling for the content. Display Rules are defined in the Knowledge Model as a Custom Object and can be called by components of a View.

Components that can apply Display Rules are:

First, define a Custom Object in the Knowledge Model for your Display Rule.

- id: DISPLAY_RULE
  displayName: Display rule
  customAttributes:
  # comparator is used to compare value from ``DISPLAY_RULE.customAttributes.value`` to the value from PQL
  - comparator: GREATER_THAN_OR_EQUAL
    # value to compare
    value: 1000 #In case you use the comparator BETWEEN you would define the value as following 'value: [ 8, 15 ]'
    # styles to change cell appearance
    style:
      textColor: red # CSS color or HEX code
      backgroundColor: black
      fontSize: 16px
      fontItalic: true
      fontWeight: bold

The Custom Object contains Custom Attributes.

Then you can use the Display Rule on a component by adding it to the View's YAML configuration.

- id: attribute
  type: attribute
  settings:
    data:
      - id: INVOICE.TOTAL_NUMBER_OF_INVOICES
        displayContentRule: DISPLAY_RULE
      - id: INVOICE.TABLE_COUNT
        displayContentRule: TABLE_COUNT_DISPLAY_RULE

Supported visual styling

You have a broad range of options to add specific style elements to your View.

The key:value pairs of style accept the following types of values

Supported comparators

You can use the following comparators for defining a display rule in the knowledge model:

comparator:
    "IS_EMPTY"  # for 'int' | 'float' | 'date' |  'string' 
    "IS_NOT_EMPTY"   # for 'int' | 'float' | 'date' |  'string'
    "TEXT_CONTAINS"  # for 'string'
    "TEXT_DOES_NOT_CONTAIN"  # for 'string'
    "TEXT_STARTS_WITH" # for 'string'
    "TEXT_ENDS_WITH" # for 'string'
    "TEXT_IS_EXACTLY" # for 'string'
    "DATE_IS" # for 'date'
    "DATE_IS_BEFORE"  # for 'date'
    "DATE_IS_AFTER"  # for 'date'
    "GREATER_THAN" # for 'int' | 'float' | 'date'
    "GREATER_THAN_OR_EQUAL" # for 'int' | 'float' | 'date'
    "LESS_THAN" # for 'int' | 'float' | 'date'
    "LESS_THAN_OR_EQUAL" # for 'int' | 'float' | 'date'
    "EQUAL" # for 'int' | 'float' | 'date' |  'string'
    "NOT_EQUAL" # for 'int' | 'float' | 'date' |  'string'
    "BETWEEN"  # for 'int' | 'float' | 'date'
    "NOT_BETWEEN"  # for 'int' | 'float' | 'date'

Icon Library

You can use the following icons in your display rules by adding iconName: [name of the icon from the list below].

Some components such as tables and buttons can incorporate icons. You can also use icons in your display rules by adding iconName: [name of the icon from the list below].

Info Text is used to add an info icon next to the title of another component. On hover, an info box with title and description appears next to the component header. It is a handy general components setting that can be added to other components.

This is how the info icon looks like next to an icon:

This happens on hover:

For many components, formats and units can be specified within the View component configuration. This allows for flexibility in displaying content to your business users.

The format strings used in the Studio are based on d3 formatting.

Example number formats

For an executive view, you might want to give a broad overview of relevant KPIs. Rounding and abbreviating large numbers will help the executive user to quickly grasp the status of a KPI. In contrast, an operational user working with Action Views needs to be aware of the details and the displayed KPI's should be as accurate as possible.

Example date and time formats

Different components might require different abstraction levels when it comes to date and time formats. To get a visual overview, e.g. in a chart, you might want to use a broader scale (such as month and year). When displaying comments, your business users might benefit from the exact time a comment was created (such as date and time).

Some examples to encode the following date and time "2018-04-15 15:22:01"

Use Cases

Add these general component settings to components to provide your business users with more information. Examples could include

The content part can include HTML to use for example formatting but also include pictures (if they are hosted freely accessible on a website). If you are new to HTML, we recommend the following external resource.

As you can see below, the info text is added directly within the definition of another component. Info text can be applied to all components with a "name" key.

components:
- id: "kpiList"
  type: "kpi-list"
  settings:
    name: My KPI List
    infoText: # add this line below the name attribute of a component
      title: "Please note!" # enter the title of your info text here
      content: "Please note that filters are used to calculate the KPI" # enter the content of your info text here - HTML is possible but will be sanitised for security
    data:
      type: "tile"
      kpis:
      - kpi: "KPI1"
      - kpi: "KPI2"