Skip to main content

Get help for ARIS Process Mining functions and services

Code filter

You can use the ARIS Process Mining process language to flexibly define any filter in the text editor supplied. The textual editor provides only the operators and operands required to define a code filter. To display all supported operators and operands, click in the first line of the editor and press Ctrl + Space. A box with the available elements opens. Select the required elements in the box.

Operator type

Subtype

Syntax

Description

Filter list

Value filter

VALUE_MATCHES (field: Filter, value1: text | date | long | double, ...)

This filter matches if one of the values provided matches.

Range filter: between

VALUE_BETWEEN (field: Field, lowerBoundary: date | long | double - upperBoundary: date | long | double, ...)

This filter matches if one of the ranges provided matches.

Range filter: greater than

VALUE_GREATER_THAN (field: Field, comparisonValue: date | long | double)

This filter matches if the value is greater than the comparison value provided.

Range filter: less than

VALUE_LESS_THAN (field: Field, comparisonValue: date | long | double)

This filter matches if the value is less than the comparison value provided.

Path filter: directly followed by

DIRECTLY_FOLLOWED_BY (activity1: text, activity2: text)

This filter matches a case if the second activity directly follows the first activity anywhere in the case flow. This filter works only in a MATCH_CASE() operator.

Path filter: eventually followed by

EVENTUALLY_FOLLOWED_BY (activity1: text, activity2: text)

This filter matches a case if the second activity eventually follows the first activity anywhere in the case flow. This filter works only in a MATCH_CASE() operator.

Activity filter: case starts with

CASE_STARTS_WITH (activity: text, ...)

This filter matches a case if the case starts with any of the activities provided. This filter works only in a MATCH_CASE() operator.

Activity filter: case ends with

CASE_ENDS_WITH (activity: text, ...)

This filter matches a case if the case ends with any of the activities provided. This filter works only in a MATCH_CASE() operator.

Activity filter: case passes through

CASE_PASSES_THROUGH (activity: text)

This filter matches a case if the case passes through all activities provided. This filter works only in a MATCH_CASE() operator.

Activity filter: case passes through any

CASE_PASSES_THROUGH_ANY (activity: text, ...)

This filter matches a case if the case passes through any activities provided. This filter works only in a MATCH_CASE() operator.

Field

FIELD (field: Field, parameterValue1, parameterValue2, ...)

Reference a field and optionally provide parameterized values.

Filter inversion

Inverts filter

NOT (value: Boolean | Filter)

Inverts a logical expression of a filter. Filters can be inverted only once.

Example 107.

This selection filters all cases with a case duration between 10 and 10000000.

VALUE_BETWEEN("_ARIS.Case"."Case duration", 0 - 10000000)



Variables

The code filter supports also variables to create dynamic filters. You can reference a variable as follows: ${variable name}.

Example 108.

This code filters all cases with a specific case duration. The value for the case duration is specified as a variable.

VALUE_MATCHES("_ARIS.Case"."Case duration", '${variable}')