Configuring conformance violations

Each type of conformance violation must be configured according to the available configuration options.

Note: You cannot create identical violations (with the same events) multiple times. Each violation must be unique.

Incorrect Sequence

The Incorrect Sequence violation marks cases that follow a specific sequence of events as non-conforming.

This table gives an overview of the configuration options for violation type Incorrect Sequence:

Field Description
Event Select an event from the list to set it as the first event of the flow. The list is populated with events that are loaded into the database.
Condition Select a condition to connect the selected first and last event. These conditions are available:
  • Is directly followed by
  • Is not directly followed by
  • Is never followed by
  • Is eventually followed by
Event Select an event from the list to set it as the second event of the flow. The list is populated with events that are loaded into the database.

Incorrect Start & End

The Incorrect Start & End violation marks cases that start and/or end with a specified event as non-conforming.

This table gives an overview of the configuration options for violation type Incorrect Start & End:

Field Description
Condition Start Event Select one or more events from the list as the start event of the flow. The list is populated with events that are loaded into the database.
Condition End Event Select one or more events from the list as the end event of the flow. The list is populated with events that are loaded into the database.

Missing Events

The Missing Events violation marks cases as non-conforming when expected events are missing from a process instance, especially when other related events are present.

This table gives an overview of the configuration options for violation type Missing Events:

Field Description
Condition Includes Events (Optional) Select one or more events that must be present in the case.
Condition Missing Events (Mandatory) Select at least one event that must be missing from the case.
AND/OR Toggle Select whether all or any of the selected missing events must be missing for the violation to trigger. Default setting is AND.

The system displays a validation error if you don't follow these configuration rules:

  • At least one event must be selected in Condition Missing Events.
  • The same event cannot be selected in both Condition Includes Events and Condition Missing Events.

For example:

If Condition Includes Events contains Order Shipped and Condition Missing Events contains Invoice Sent, a case where Order Shipped is present but Invoice Sent is missing is marked as non-conforming.