Entity property rule

Equals(Default)

Agreement with a compare value.

Any

Explicit → Value configuration

In list

Match with list entry in the compare value.

Any

Explicit → Value configuration

for 'list value' (List, Set, and so on)

Compare with

Rank comparison with selectable compare operator (=, <, >, <=, >=).

Any

Explicit → Value configuration

Starts with

Text comparison

NOTE The value configuration for the check value must provide a String value. For a compare value that is not a String, the string image is used, which can be specific for each execution context.

String

Explicit → Value configuration

Ends with

String

Explicit → Value configuration

Contains

String

Explicit → Value configuration

Is empty

Checks whether the check value is empty.

Any

Implicit → 'No value' ($null) or 'Empty list' ([]).

Value changed

Deviation from the Original entity.

Field value of an entity

Implicit → Corresponding field value in the Original entity.

Special case

Script

Custom logic that returns a Boolean value.

Any

Not provided.

After adding a new Entity property rule, it appears as shown on the right:

• The value configuration for the check value (left) contains an Object property resolver for which no field is selected.

• The Equals matcher type is predefined.

• The value configuration for the compare value (right) appears empty.

If there is a type reference for the reference object for the context of the Entity property rule, for example because a Check type is provided within an AND Junction 'above', a field can be selected immediately in the Object property resolver (after expanding).

In the example on the right, a 'company account' (see Companies/Clients) is expected as the reference object, so that the 'Metatype' (metaType) field is found when you search for 'type'.

After selecting the 'Metatype' (metaType) field, its data type is adopted as the type hint for the compare value. This is the Company meta type defined as a dynamic enumeration. The reason is that the Equals matcher type provides for this.

There is still no value configuration for the compare value, but in contrast to the first screenshot, the '+' symbol indicates that a value resolver is proposed when the value configuration is expanded, with which a Company meta type can be selected as a static value.

The screenshot on the right shows the Enumeration resolver proposed for the Company meta type based on the check value type, which returns two results in the dropdown for the entered search text ('a').

The Enumeration resolver only allows a single selection. If different 'metatypes' are defined as acceptable with the same Entity property rule, the Equals matcher type must be replaced by the In list matcher type.

NOTE Alternatively, it is possible to 'juxtapose' several instances of the Entity property rule in an OR Junction.

A change of matcher type must be initiated by clicking on the menu icon within the hexagon shape:

 CAUTION  As can be seen in the previous screenshot (right), the value configuration for the compare value is overwritten when the Matchers changes.

For the In list matcher type, a Create list resolver is proposed for the compare value configuration, with which any number of entries can be defined.

The data type of the check value is not evaluated as an indication of the level of the list entries, so that the appropriate Enumeration resolver is not automatically suggested here.

Instead, Any enumeration must be used to select specific values for the Company meta type enumeration.

NOTE If all selected enumeration values come from the same enumeration, this appears as a type hint for the return value of the Create list resolver (see screenshot on the right).

By default, the In list matcher type is considered passed if the check value is contained in the list provided as a compare value. The list therefore acts as a positive list (allowlist). If the list needs to act as a negative list (blocklist) instead, the logic must be 'reversed':

This is made possible by the not menu item in the context menu for the Matchers selection.

This Entity property rule passes only for companies whose Company meta type is neither 'Company' (COMPANY) nor 'Group' (GROUP).

NOTE Instead of reversing the logic for the Matchers, this could also have been done for the Entity property rule as a whole (see screenshot on the right).

This is made possible by the 'not' menu item in the context menu for editing the rule. You open the context menu by clicking the menu icon in the top left corner of the surrounding rectangle.

The screenshot on the right shows the 'negated' Entity property rule. The '!' indicator appears as an icon at the bottom of the rectangular shape and as a prefix in front of the text in the title bar ('!Compare...').

NOTE The screenshot on the right compares the appearance of the two variants for the negation in the context of an OR Junction.

• The first variant is textually more 'readable':

  metaType not(in list)

• The second variant visualizes the negation more clearly.

  NOT: (metaType in list)