The user 'Karola Mustermann' is logged in for the portal operator (Xflow AG) as 'CustomerAccountManager' and accesses the company account of a customer company via the 'Companyaccount overview:'

• In the Contacts tab, the address contacts of the company are listed there. So far, the list of contacts refers only to the 'CEO'.
  
  ►NOTE◄ The form layout in the image on the right has been slightly modified compared to the default. Among other things, the symbol for deleting entries is hidden. Instead, a Delete Button has been added inside the repeated container for the address contact. This can be set active or inactive depending on the contact type to allow or prevent deletion (see Remove element (optional/repeatable element)).
  
  In the present application case, an address contact with the Contact type 'Account manager' should not be able to be deleted and should also appear deactivated except for the Button for 'e-mail' sending (see screenshot below right).

As soon as the processing of the company account for 'fast-or-furious Ltd.' is completed via Save (in the ribbon), 'Account manager' appears in the company account, which shows the address for the user account (see Users) of 'Karola Mustermann'.

Only the name fields are displayed here, but the address contact provides access to the entire address, so that, for example, the e-mail function, can use the communication information it may contain.

An event handler is created for the 'registration' of the user making the last change to a company account and configured as shown on the right:

• 'Update' and 'Create' events (see Common action event) are set as the Triggering events.
  
  

• The Validating rule uses Check type to determine whether the input value is the 'CompanyAccount' type. If this is the case, the AND-junction Sub criterion rule is evaluated, which determines per Role rule whether the 'CustomerAccountManager' role is claimed in the logon context.

• An Action on passed rule is an event action of the Execute with type that is used to define the reference object differently from the company account that is the input value:
  
  

  • The company account from the input value is saved per Save Company account in variable parameter in a variable with the name company .
    
    

  • In the Object Resolver, the User of session is first determined via concatenation and then the associated user account is read via an Input object (type safe). In the address field, the address contact that is added for the 'customer advisor' can be found. This is valid for the following action block as a reference object.
    
    

• In the Execute with event action block, the only event action that follows is Adresse als Kontakt einer Firma hinzufügen with the following parameters:
  
  

  • As Contact type, 'Account manager' is assigned as a static value (per 'Any dynamic enumeration' value resolver, see Static values).
    
    

  • Access to the Target company, which is the input value outside the Execute with event action, is available within the Execute with event action only via the Variable company .

►NOTE◄ The fact that the Target company is also the input value of the event handling is a coincidence. If the address of 'Karola Mustermann' in our example is not yet entered as an address contact of the 'Account manager' type, the 'Update' event for the company account will be triggered twice, because the address contact is added again.

In the course of addressing a shipment, a company account is selected for the company and address attribute Loading party (Company type DPA) initially in order to be able to specify a precise pickup position (here: Loading party Address), which, if necessary, will subsequently be stored in the address of the same company and address attribute.

When selecting the company for the Loading party, the action Use contacts of this company for the Combobox of the Loading party Address is executed in the entry form. In the example, this should then offer all address contacts with the Contact type 'Gate/Entrance' or 'Building' for selection, which are found in the company account of the selected company.

Alternatively, a completely new Loading party address can also be entered.

Via the 'Add as company contact' button, a newly entered or changed company address should be added as a contact. The user should be able to define the assigned Contact type for the address contact via context menu (see screenshot on the right) from the options relevant for the pickup address.

For the Triggering event 'Add address' (see Address (Events)) the event handling shown on the right is configured:

• The Validating rule uses Check type to ensure that an 'address' was passed as the input value. When triggering the event by the 'Add as company contact' button, this should be implicitly guaranteed. So the Check type here essentially declares the data type 'address' for the input value.
  
  ►NOTE◄ The event is defined here in a generic way and therefore does not need any further rules for the transferred 'address' or the values of the variables that are automatically filled when the event is triggered (contactCompanyId, contactType und contactTypes).
  
  

• Therefore, among the Actions on passed rule, it is first determined whether the Contact type to be added to the company account is uniquely determined by the context. In the Object Resolver, the Execute with event action defines the Contact type list in the contactTypes variable as a different reference object for the following block of event actions:
  
  

  • An If then else event action examines the field length of the list by an Entity property rule to determine if it contains more than a single element. The user should only have to select from the available options via the context menu if this is the case.
    
    

  • If a decision is required, the Show context menu event action displays the localized texts for the contact types contained in the list as options.
    
    

    • Since the list is already available as a reference object, the Object property value resolver inserted under Root items gives the entire list without a field.
      
      

    • The label expression accesses the Localization with the syntax [bundle, resource] to look up the localization entry for the name of the respective contact type (resource {name}) in the bundle de.lobster.scmbase.address.attributes.ContactType there.
      
      

    • The contactType variable is specified here as the Name of result variable. This variable contains the first value of the list until the context menu is called, because the 'Add address' event automatically preassigns this variable.
      
      

    • The selection in the context menu returns the Contact type clicked on, unless the user allows the Wait time (set here to 300 seconds) to elapse or closes the context menu without making any selection (via the Esc key or by a mouse click in the form.

►NOTE◄ The already pre-assigned variable contactType is also specifically selected here as the target for the return object of the context menu, so that within the event action Adresse als Kontakt einer Firma hinzufügen for the parameter Contact type the value of the variable contactType can always be transferred. In the special case of a crash or timeout after opening the context menu, however, the Adresse als Kontakt einer Firma hinzufügen event action is then blocked from being executed at all, otherwise 'no value' is passed as Contact type, which leads to a crash with an error message (incl. rollback).

After completion of the Execute with event action, which is only relevant if the Contact type is not uniquely predetermined, the address to be added is again considered the reference object. In this context, the event action Add company address contact is executed:

• Within an If then else event action, however, it is checked beforehand whether the variable contactType is empty:
  
  

  • If the variable specifies the predetermined or selected Contact type, then the event action Add company address contact is executed, assigning the variable contactType as the Contact type and the variable contactCompanyId as the Target company.
    
    ►NOTE◄ If there is no permission in the logon context of the session to change the company account in question, the event action should be executed within an Run as event action with a different logon context.
    
    

  • Without any specification for the Contact type – i.e. if the user has exited a context menu without any selection – the event handling should be terminated without comment or further event actions.