Skip to main content

Celonis Product Documentation

Case explorer for Views

A case explorer displays the data tables connected to the Celonis engine and provides an intuitive tool for examining cases and their respective activities. It is useful to localize problems, validate insights and validate data. It can be added to a View as a component and can also be accessed in Business Miner by clicking the button next to the case number.

case_explorer_numbered.png

The table on the left side is the case table with all cases. Each row contains information for one case. Clicking on the case ID allows you to view the activity details of that case on the right panel. The colors used for each event log are consistent with those in the process explorer.

  1. Where you can clear all sorting, revert to the default settings and change the visibility of columns. The Case Explorer displays the following columns by default:

    • Case ID

    • # of Activities

    • TPT Duration

    • First Activity

    • First Activity Timestamp

    • Last Activity

    • Last Activity Timestamp

    If the activity table contains more columns, they can be displayed by changing the column visibility of the table.

    activity_table_columns.png

  2. Move to the next or previous case.

  3. Expand to see activity details.

  4. Search for an activity by activity name

  5. The View Case Explorer component supports multiple event logs. One event log from the multiple event logs is the main event log for a case explorer. The case IDs in the case explorer are the case IDs from the main event log. The columns of the case explorer table are the columns from the main event log. Other than the main event log, the other event logs can get hidden when changing the visibility of event logs on the case detail panel. When an event log is hidden in the activity table, the activities in this event log are also excluded from the case explorer table.

  6. The View Case Explorer component supports multiple event logs, however, only one of the event logs is the main event log for the case explorer. The case IDs displayed in the case explorer and the columns from the case explorer table are both from this main event log. Other than the main event log, the rest of the event logs can be hidden by changing the visibility of event logs from the case detail panel. When an event log is hidden in the activity table, the activities from this event log are also excluded from the case explorer table.

    casr_explorer_eventlogs.png
Configure the case explorer
Basic case explorer configuration

To configure a basic case explorer, use the following YAML:

id: case-explorer
type: case-explorer
settings: {}
Advanced case explorer configuration

If you have multiple event logs, using the basic configuration settings: {} would only include the main event log for case explorer. The main event log for Case Explorer is the default event log set in the data model. Using the advanced configuration below, you can include all available event logs. The columns of the case explorer table are taken from the main event log. You define which event log is the main event log for the case explorer by listing it in the first place of the event log list. So in the example below, Invoice_Order is the main event log.

id: case-explorer1
type: case-explorer
settings:
     name: Retail order management
     data:
          record: km_invoice_record -- optional
          eventlogs:
               - eventLog: Invoice_Order
               - eventLog: Return_Order
               - eventLog: Sales_Order
               - eventLog: Delivery_Order

Attribute

Required

Type

Possible values

Description

name

No

String

Defines the case explorer name that will be displayed on the top left corner of the component.

data

record

No

string

Record Ids from the Knowledge Model

If you don’t want to use the default auto-generated record in the Knowledge Model for the Case Table, you can configure your own record in the KM with the appropriate attributes and correct unit/format. Then use the RecordId from the record you configured as the main record rendered in the case table section of this CaseExplorer component.

Note

The attributes and PQL statements used in this record should have a data model relation with the actual case table. Otherwise the component will not be able to render and you will get an error message.