Rules and values

‘Values’

Value configurations using Resolvers

►NOTE◄ Resolvers can contain parameters that are determined by a value configuration or rule configuration. In this way 'values' and 'rules' can be nested as deeply as required.

‘Values’ – i.e. specific data is determined at runtime via configurable Resolvers, which can be aggregated as required within a value configuration by concatenation (see Chained resolver).

• The primary goal of a value configuration is typically to provide a specific return value, usually as an assignment to a parameter in a parent configuration (Resolvers, Rule types, Event actions, etc.).

• Resolvers can process a given input value and/or the reference object given in the context and also evaluate any existing Variable in the execution context.

• The Store value as variable resolver plays a special role, ‘forwarding’ the input value unchanged as a return value and writing it to a Variable at the same time.

Placeholder for a value configuration:

Value configuration with a value resolver chain (see Chained resolver), which links three Resolvers in series:

'Rules'

Rule configurations using Rule types

►NOTE◄ Rule types can contain parameters that are determined by a value configuration or rule configuration. In this way, 'values' and 'rules' can be nested as deeply as required.

'Rules' are specific rule configurations that use configurable Rule types as basic building blocks for more or less complex logical aggregates.

• The primary goal of a rule configuration is to return a truth value ($true/$false), which usually determines a parent-level case distinction.

• Many Rule types provide parameters for which a specific value is determined at runtime via value configurations. Other ‘rule’ parameters can only be ‘set’ statically in the configuration.

• In conjunction with the Value from localization resolver, rule types with parameters determined by value configurations can also be used exceptionally for assignments to variables in the context.

Placeholder for a rule configuration:

Rule configuration with an OR Junction of two different Regeltype:

Matchers

The compare type that can be selected in the configuration makes the Entity property rule an important interface between value and rule configurations.

►NOTE◄ For the Search API, the Field restriction plays a similar role, but on the basis of specific compare types for database queries.

Rules and values often require a connecting element as the basic building blocks of configurable logic:

Within an Entity property rule, a Matchers must be selected that determines the characteristics of the evaluation of a test value in comparison to a compare value.

While the check value is always determined by a value configuration, a value configuration is only offered for the compare value if this must be explicitly defined because it is not implicitly specified by the selected compare type (see Value changed, Is empty).

Entity property rule in which two value configurations are related via the Ends with compare type: