The user account in question is defined as a reference object in the configuration on the right by an Execute with event action (not shown in the image). The assignment is done by a Set value event action:

• The Object property value resolver (left) defines the target property 'Companies' (companies) for the assignment.
  
  ►NOTE◄ As the reference to the data type below the property selection in the value resolver suggests, the property expects a list of Long values, i.e. in our context the IDs (id) of the repsective company accounts and not the complete company account as entity.
  
  

• On the right, the Create list value resolver creates one with the IDs of two company accounts, each defined by the Company value value value resolver, from whose return value the 'ID' (id) of the account is resolved via the concatenated Object property value resolver in each case.
  
  ►NOTE◄ After predefining the ID values of the two companies, one could also achieve the same result by setting the IDs as static long values in the Create list value resolver. However, this should be avoided with regard to the exchange of configurations via Meta exchange (e.g. between test/production system), since this automatically 'recognizes' only company accounts identified via Company value value resolver.

Within a With rule (not shown completely in the image), the reference object is the company address in the 'address' (address) property of the company account returned by the Company of session value resolver. In the context of this address, two AND-linked instances of the Entity property rule are configured:

• The first Entity property rule ensures that the Company of session is located in the searched country (here: Germany).
  
  

• The second Entity property rule checks whether the company is located in one of the searched postal code areas by means of the Zip code:
  
  

  • On the left, the Object property value resolver reads the ZIP code from the 'Zip code' (zipcode) property of the address. Using concatenation, the Substring value resolver extracts the first two digits from the postal code below, since only these digits are decisive for the check.
    
    

  • If the In list type is selected as Matchers, the Create list value resolver automatically appears on the right side as a suggestion. Here, the 'positive list' with the two-digit number combinations for relevant regions can be entered directly. An entry must be created for each region by clicking on the symbol. After that the leading digits of the Zip code can be configured as static text (see Static values) as value.

►NOTE◄ Instead of the Create list value resolver (right), the list could also be defined quite conveniently as static text in JSON notation (see below) and passed to a JSON to object value resolver via concatenation:

Within an event handling that reacts to the event 'Delete' (see Common action event), the action part is configured as follows:

• A For each loop iterates over a list of addresses and triggers a Custom action event 'Xf Mail Job' (XF_MAIL_JOB) for each address contained in the list (as input value).
  
  ►NOTE◄ Information about the deleted entity is provided to this event via the deletedEntity variable, which is filled in the loop header with the input value of the event handling shown here (i.e. the deleted entity).
  
  

• In the Resolver for entities, the Create list value resolver is used, which creates a list with exactly three entities:
  
  

  • For the first entry, the creatorId property of the entity is read and the relevant user account is obtained via the Input object (type safe) value resolver.
    
    

  • The second entry accesses the server-side state of the entity to be deleted via the Original entity value resolver (see note below), reads its lastModifierId property, and then obtains the user account in question via the Input object (type safe) value resolver.
    
    

  • The third entry reads the ownerId property of the entity to be deleted and obtains the relevant company account via the Input object (type safe) value resolver.
    
    

  • The Collect values value resolver concatenated with the Create list value resolver extracts the address property from all list entries, using (not shown in the image) the 'Unique values' option so that a notification is not triggered multiple times for the same 'address' object.