The screenshot on the right shows an overview of the configuration for event handling that reacts to the Triggering events 'Delete' and 'Create' (see Common action event).

An AND junction of two instances of the Check type is configured here as the Validating rule:

• The first Check type checks for the 'Entity' (Entity) type, which is the parent of all entity types. This check is actually superfluous, as the Triggering events are exclusively relevant for entity types. However, for formal reasons, value is placed here on the 'Entity' type hint for the Action on passed rule.
  
  

• The second negated Check type excludes the 'E-mail' (Mail) entity type from the e-mail notification, which is very important, because the E-Mail event action not only triggers the sending of messages, but can also trigger the 'creation' of E-mails as an entity, which without this exclusion criterion could lead to an endless loop of sending and possibly creating further E-mails.

A E-Mail event action is provided as the only Action on passed rule. As no further event actions are available, all preparation steps for content and addressing of the e-mail within the configuration for this event action must be carried out either statically or via value configurations for designated parameters.

For the context of this example, only the value configuration for the Subject, for which a text value is expected, is of interest from the numerous parameters for the E-Mail event action.

The screenshot on the right shows a value resolver chain through which the localisation for the entity type is integrated via the Class name of object resolver in the context of a Concat strings value resolver:

• In the Value from localization resolver, the Bundle parameter is bound directly to the return value of the Class name of object resolver. This returns the fully qualified class name for each entity, which is systematically also the Bundle name.
  
  

• The string $name is used as static Text for the Resource parameter, which is used by convention to localise the class name of entity types.
  
  

• The Default value parameter is only relevant if no applicable localisation has (yet) been assigned for a Bundle/Resource combination. In this case, only the last section of the fully qualified class name should appear in the Subject line, i.e. the class name in the narrower sense (without information on the package or namespace):
  
  

  • For this purpose, the return value of the Class name of object resolver is first split using the Delimiter (seperator) '.' into a list of substrings by the concatenated Split text resolver.
    
    

  • The concatenated List item resolver then accesses the last entry (Mode ‘Get last’) of this ‘list’.
    
    

• After a static seperator string (‘ / ’ as Text), only the return value of the Triggering event resolver is then added to the Subject. Localisation is expressly omitted here, as in the server context the internal names of the relevant events are predefined as DELETE and CREATE in the corresponding static enumeration and these terms characterise the process in a generally understandable way.