The notification can be configured within an event handling as shown on the right:

• The Object Resolver within the Execute with event action primarily accesses a map present in the author variable. If the variable returns a map, this map will be the reference object for the output of the notification via a Show alert (Popup) in the action block below.
  
  

• If the author variable is empty or contains a data type other than a map, the Variable value resolver returns 'No value'. Then the concatenated Default value resolver becomes active and evaluates the configuration for its Default value parameter:
  
  

  • A 'client object' is created from the static string {name:NN,id:0} (see Static values) by the concatenated JSON to object value resolver.
    
    

  • The 'client object' replaces the missing map as a reference object in the output of the notification via Show alert (Popup) in the action block below.

Within the Show alert (Popup) event action, the Message combines values from the reference object in a Concat strings value resolver with literal text characters:

• The first text component reads the Key or the name field. Its name is assigned as static text.
  
  

• The second text component defines literal formatting characters as static text.
  
  

• The third text component reads the Key or the id field. Its name is assigned as static text.

►NOTE◄ We assume that the type of all 'keys' relevant to the notification is in the map String. Only then does the smooth switch between 'client object' and map as input value for the Map item resolver work as demonstrated here.

►NOTE◄ Creating a 'client object' in the Default value resolver is more efficient than defining a separate Default value for each read access. However, the 'default' only applies if the map is completely missing. If the map is available, but does not contain values for all relevant 'keys', then the notification appears incomplete, if 'individual default values' are waived as here.

The configuration on the right shows how the evaluation of combinatorics can be solved within an event handling:

• Details of the initial Search (Event action) are not important here. What is important is that it provides a list of users accounts in the variable users.
  
  

• The following Execute with event action sets a map created by Create instance with the Type 'Map' (java.util.Map) as the reference object for the further event actions. As long as all actions concerning the map can be performed in this context (e.g. Show alert (Popup) at the bottom), the created map does not need to be explicitly assigned to a variable.
  
  

• For the context within the following For each loop, the locales variable for accessing the map is defined via the Save map in variable parameter. The Reslover for entities parameter defines an iteration over unique values for the 'Locale' (locale) field within the list of all Users of the 'user group' (in the users variable):
  
  

  • The Variable value resolver first returns all user accounts listed in the users variable.
    
    

  • The concatenated Collect values resolver reads the Object property 'Locale' (locale) from these and returns a list as return value via the Unique values option, which contains each relevant 'Locale' exactly once.
    
    

• The Execute with event action within the loop does not define a Object Resolver, so retains the Locale as a reference object. The Save Locale in variable parameter additionally writes the decisive Locale for the respective iteration into the locale variable. This is particularly necessary in order to access the Locale in the Rule list resolver (see below), which here refers to a user as a reference object.
  
  

  • The Set value event action defines a write access to the map (locales), which on the one hand creates a Key for the current Locale and on the other assigns the desired 'country list' for the locale as a value.
    
    

    • On the left side of the assignment, a Variable value resolver establishes the reference to the map locales, which is needed as an input value for the concatenated Map item resolver. This defines the current Locale as the Key (per Variable value resolver for locale).
      ►NOTE◄ A specification of Item type and Is collection of is omitted here.
      
      

    • On the right-hand side of the assignment, a Variable value resolver accesses the list of Users (users) at the beginning of the value resolver chain, which is processed as follows:
      
      

      • The concatenated Rule list resolver returns all Resolve all as list for which the Entity property rule is fulfilled that the Object property 'locale' (locale) matches the current Locale (locale variable) in the iteration.
        
        

      • The concatenated Collect values resolver determines from this fraction within the 'user group' a list of unique values for the 'country' (address.countryCode) address field, provided that there is an entry for it
        ►NOTE◄ $null values are simply skipped by Collect values in the given configuration.
        
        

• After iterating over all the languages used, here we perform a Show alert (Popup) event action to output the string image of the map for demonstration purposes.
  
  ►NOTE◄ In a real use case the map can be processed otherwise.

Runtime example: (String image of the map)

{en=[US, DE], de=[DE, IT, AT], fr=[MU]}

►NOTE◄ Values of the dynamic enumeration Locale serve as a Key in the map and not just the internal names of these values (as a String) that the string image outputs. Also, the list in the associated value refers to dynamic enumeration values for the Country and not only to the text values output above.

For clarification, the server XML image of a map with the same data is also shown below

In the event handling used to 'roll the dice', the event actions shown on the right are configured:

• The surrounding Execute with event action sets a 'Client object' created by Create instance with the 'Client object' type (ASObject) as the reference object for the further event actions. The concatenated Store value as variable value resolver stores a reference to this 'client object' in the roll variable. This variable name can be referred to, for example, by the 'Result expression' parameter in a Dispatch custom action event (Form designer) behaviour (not shown in the image) as a return value.

• The For each loop event action should execute the number of dice specified by the Long value in the numberOfDice variable. A Dispatch custom action event (Form designer) behaviour can pass this value as a call parameter.
  

  • Within the iteration, the Set value event action assigns a 'diced' random number (as a long value in the value range between 1 and 6) to a field of the 'client object' present as a reference object, whose name combines a prefix with the index number of the dice.
    
    

    • On the left side of the assignment, the Map item value resolver defines the field name in the Key parameter using a Concat strings:
      

      • The first text component is the static text die.

      • The second text component is derived from the Long value in the $index variable, which specifies the current iteration index in a For each loop event action.
        
        

    • On the right side of the assignment, the actual 'dice rolling' takes place. Details about this are not relevant here.