Within the list settings for the guest user overview, row formatting (see Row formatting in datagrids) is created in the datagrid settings, which defines the 'white/red' color scheme for the 'alert level'.

The 'condition' of the row formatting is formatted as shown on the right:

• A Field restriction checks whether one of the Roles explicitly intended for guest users is selected in the 'Role' (roleId) field of the guest user account.

• On the right side of the Field restriction, the positive list of allowed Roles is first created by a Create list resolver. Each entry uses its own instance of the Role resolver, in which an allowed role is selected.

• A Collect values resolver follows per concatenation, which converts the list of Roles (Rolle[]) into a list of Long values (Long[]) by accessing the 'ID' (id) field of the role via an Object property resolver.

• Another Field restriction follows within the AND conjunction here, which checks whether the guest user account is 'Active', so that the formatting does not define a 'false alarm' for accounts that are already deactivated.
  
  ►NOTE◄ Additional constraints can be added or exceptions can be defined, e.g. to prevent 'expired' Guest users from being alerted.

An event handler that responds to 'Create' and 'Update' (see Common action event) as Triggering events is configured as shown on the right:

• The Validating rule first ensures that an entity of the 'Guest user' type is saved.

►NOTE◄ Depending on the objective, further criteria could be examined in order to specify the scope of the rule, for example via a Role rule or Company type rule.

• Within the AND conjunction, an Entity property rule follows below. Its structure basically corresponds to the Field restriction from the previous example:
  

  • On the left, an Object property resolver accesses the 'Role' (roleId) field of the guest user account stored as the reference object.
    
    

  • By combining the In list matcher (below) in conjunction with the negation by the not (Matcher), the Entity property rule is considered to pass if the ID of the role (roleId) is not included in the positive list defined on the right.
    
    

  • As in the previous example, the positive list (right) is first constructed starting from a Create list resolver, in which each entry specifies a permissible role via a Role resolver.
    
    

  • The Store value as variable resolver following in the concatenation stores the Roles list in variables whiteList, so that the positive list can be reproduced in the error message in case of cancellation.
    
    

  • Similarly to the previous example, the Collect values resolver is used below to obtain a list of Long values from the Roles list for matching with the roleId , where the Object property resolver accesses the 'ID' (id) field of the role.

An Abort is executed as the Action on passed rule, which is configured as follows:

• The Error type is assigned to 'Notification: Error' so that the message appears at runtime as a 'red flag' in the right margin.

• In accordance with the randomly chosen Error code SECURITY_GUEST_USER_ROLE_ALERT an entry of the Localization is addressed (see below). The text key used as an Error code is also specified here in the Default error message parameter, which appears in the error message if no localization is found.

• A parameter is added to the Parameter list that generates a formatted list of role names (roleName) from the contents of the whiteList variable via the Template resolver.

In Localization, an entry is created in the Resource bundle error for the localization of the error message, whose Resource name corresponds exactly to the Error code (SECURITY_GUEST_USER_ROLE_ALERT).

• The German field shows the localization for this Locale. To the right is the corresponding definition for the Locale English.
  
  

• In both languages, the reference to the parameter {0}marks the position where the list of allowed Roles from the Parameter defined by the Template in the error message is inserted at runtime.