Celonis Product Documentation

Monitoring of conditional attributes: Quickly view and track business rule conditions.

Built-In conformance analysis: Automatically calculate conformance rates and non-conformance impacts on KPIs.

Reusable conditions: Utilize boolean calculated attributes in the Knowledge Model for conditions. For more information, see: Calculated attributes in a boolean format.

Configurable outputs: Using the condition list component, you can configure the following outputs:

Business rule data entity: You can now use the metrics available in your Knowledge Model without needing to maintain custom objects.

Visual editor: Configure rules, styles, and interactions in a consistent interface, eliminating YAML dependency.

Metric association: Display the impact of business rules on selected metrics directly within the component.

Advanced filtering: Chain filters for true or false conditions across multiple rules.

Component interactions: Create built-in linked views for detailed exploration of specific gaps.

Calculated attribute: Calculated attributes allow you to extend physical tables (known as records in the Knowledge Model) in your Data Model with virtual columns. These virtual columns are created using PQL, allowing you to reference and reuse the PQL calculations and formulas in your Knowledge Model. The PQL used to define the calculate attribute is then evaluated at runtime (after the Data Model load), displaying the result of your PQL calculation as values in your view or other Studio assets.

Boolean format: This is a data type that has three possible values, usually represented as true (1), false (0), and not applicable (NULL).

In this first example, all customer returns must be processed within 30 days. We can translate that to process language such that: If the throughput time between receiving a return and completing the return is less than or equal to 30 days, the statement is 1 / True. If the return does not meet this criterion, the statement is 0 / False.

CASE WHEN 
CALC_THROUGHPUT ( FIRST_OCCURRENCE [ 'Receive Return' ] TO LAST_OCCURRENCE ['Finish Return'], REMAP_TIMESTAMPS ( “Eventlog”.”Timestamp” , DAYS)) =< 30
THEN 1 ELSE 0 END

In this second example All Purchase Orders that are blocked (release indicator = 'B') need to have a 2nd level approval ('2').

If the case is not applicable (Release Indicator is not 'B'), the value is NULL. If the Release Indicator is 'B' and the Approval Level equals '2', the statement is 1 / True. If the Approval Level criteria is not met, the statement is 0 / False.

CASE WHEN "o_celonis_PurchaseOrder"."ReleaseIndicator" = 'B'
THEN
 CASE WHEN "o_celonis_PurchaseOrder"."ApprovalLevel" = '2'
 THEN  1 ELSE 0 END
ELSE NULL END

0 (Bad Behavior): Indicates non-conformance.

1 (Good Behavior): Indicates conformance.

NULL: Not applicable.