The configuration shown on the right serves exclusively to demonstrate the effects of different parameters for the Rule list resolver with the same input value.

This is defined here in the Object Resolver parameter of an Ausführen mit event action via a Create list value resolver as a list with statically determined entries of different data types:

• The first value is the static Long value 123.
  
  

• The second value is the static decimal number 3.57.
  
  

• The third value is the static String value 0815.

This list is passed by concatenation as input value to a Rule list resolver. The table compares different parameters and the resulting output (as a string image of the return value).

In the configuration, a Show alert (Popup) event action generates this string image by outputting the return value of the value resolver as the Message text.

The Title of the message indicates the number of entries in the returned list.

The following table lists different parameters for the Rule list resolver, which are based on the diagram shown on the right:

• An Element type is selected or not.
  
  

• The option Resolve all as list is checked or not.
  
  

• A rule is not configured.

►NOTE◄ As the diagrams on the right show, the option Resolve all as list together with the selection for the Element type influences the data type for the return value.

In this specific case, a list of numerical values (Number[]) is expected as the data type for the return value at the top (with the Resolve all as list option checked), while only a single numerical value (Number) is expected at the bottom.

'All Number values as a list':

'Only first Number value':

<No selection>

3

[123, 3.57, 0815]

Without an element type, all entries are considered acceptable.

123

Long

1

[123]

Only the first value is explicitly defined as Long. The fact that the string '0815' could be converted to the Long value 815 is irrelevant.

123

Double

1

[3.57]

Only the second value is explicitly defined as Long. The fact that the Long value '123' could be converted to the Double value 123.0 is irrelevant.

3.57

String

1

[0815]

Only the third value is explicitly defined. A conversion of the numerical values as 'string image' does not take place.

0815

Number

2

[123, 3.57]

The parent class Number covers Long and Double, but not String.

123

The screenshot on the right shows the configuration for an association criteria that applies exactly when the Company of session is subordinate to more than one company account with the Company meta type 'Group' (GROUP):

• The primary data for the check here is provided by the Company of session value resolver, namely the company account of the logged-in company.
  
  

• The concatenated Object property value resolver accesses the 'Parent companies' (parentCompanies) field of this company account and returns the list of Long values stored in it, which refer to the IDs of the parent company accounts.
  
  

• The concatenated Rule list resolver filters out from this list the subset of IDs that refer to group company accounts:
  

  • The Resolve all as list is checked, because for our check criterion the number of all parent groups is decisive.
    
    

  • In order for the Entity property rule to check the 'Meta type' (metaType) of a parent company, the complete company account must first be obtained starting from the ID. This is done by the Input object (type safe) value resolver, which is concatenated on the left side with the Object property value resolver for the 'Meta type' field.

  • On the right side of the Equals comparison, the relevant Company meta type 'Group' (GROUP) is statically selected.
    
    

• The actual check criteria is mapped to the outer Entity property rule (per Compare with '> (greater than)'). The number of entries (length field) in the return value of the Rule list resolver is compared with the comparison value 1.

The screenshot on the right shows the configuration for an event handler that responds to a Custom action event XF_CALL_LAST_MODIFIER set up as a Triggering event.

The Validating rule is limited to a Typprüfung that ensures that an entity is present in the context of the event. This should ensure that the lastModifierId field exists and refers to the ID of a user, if applicable.

►NOTE◄ The possibility that Guest users can change an entity is not to considered here.

An Ausführen mit event action is used here as the Action on passed rule, since starting from the lastModifierId from the entity in the context, the relevant user account is set as the alternative reference object. This is made possible by the Input object (type safe) value resolver concatenated with the ID.

With the user account as the context, a Show alert (Popup) event action is executed that first accesses the 'username' (username) field in the Title within a Concat strings, which should identify the user in the notification.

The Message also uses the Concat strings value resolver to output the relevant phone number in conjunction with a caption. This is obtained via a concatenation of value resolvers, in which the Rule list resolver has the decisive role:

• First, the Object property value resolver must access the address field of the user account present as an alternative reference object.
  
  

• The concatenated Plural attributes value resolver returns the list of all communication information within that address.
  
  

• The concatenated Rule list resolver searches for the first match in this list (option Resolve all as list is unchecked), for which the two criteria AND-linked in the rule are true:
  
  

  • The first Entity property rule checks whether the Communication type 'Mobile' (MOBILE) is present.
    
    

  • The second Entity property rule checks whether the text key 24/7 is entered as 'context' (communicationContext).
    
    

• If the address contains communication information that meets both criteria, the concatenated Object property value resolver can then contribute its 'value' (communicationValue) field for the text of the Message.

►NOTE◄ In the example, 'error handling' has been omitted for the case that no value is specified for the '24/7 mobile number' in the user account. The Default value resolver could be used to assign information text like 'n/a' or the access method demonstrated in the example could be used to search for communication information with a different specification (e.g. type 'MOBILE' and context 'PRIVATE', see example data above) as a replacement.