Matchers

images/download/attachments/201666709/image-2025-4-1_15-7-58-version-1-modificationdate-1743512878669-api-v2.png

In the context of an Entity property rule, a check value can be subjected to an evaluation defined by the selected matcher types.

In the user interface for the Entity property rule, a the matcher type is symbolised by a hexagon shape, featuring the Equals matcher by default.

The matcher type cannot be removed, but replaced by another type from the context menu opened by the menu symbol (left in the hexagon, see following image):

The (+) symbol on the right-hand side of the hexagon only appears for parameterisable matcher types. It is used to expand the configuration interface for the parameters,

NOTE◄ The configuration interface appears expanded when the matcher type is changed. In a saved configuration and when adding a new Entity property rule, however, it is collapsed by default.

Lobster Data Platform / Orchestration offers the following matcher types for selection via the context menu:

The comparison logic and any available configuration options describe the child pages.

The not (Matcher) matcher takes a special position: It can only be selected in conjunction with one of the other matcher types to reverse its logic (true/false).


images/download/attachments/201666709/image-2025-4-1_15-12-32-version-1-modificationdate-1743513152467-api-v2.png


NOTE◄ The selection of the matcher type can change the configuration options for the Entity property rule. When the matcher type is changed, unsaved configurations for the optional compare value are deleted (see Entity property rule for details).

NOTE◄ The context menu for the matcher type does not provide options for cutting, copying and pasting a matcher type configuration, and these functions are only available for the parent Entity property rule. More complex configuration options are supported only by the Script matcher type anyway, which should be used only in special 'emergency' situations.