An event handler is configured as shown on the right:

• 'Client logged in' is selected as the Triggering event (see Login (Events)).

• As a Validating rule, a Role rule for the 'Super user limited' role is checked.

• Under the Action on passed rule, the Execute SQL query event action is executed first, which should store its search result in the records variable specified by Store result as.
  

• The Alias hub, is specified here as static text. It defines the context in which the statement defined by the SQL Query parameter is executed. This is also defined as static text, but unlike the version above, it contains the placeholder @1:s@, which 'makes variable' the last section of the string to be checked. This is to demonstrate the use of a placeholder, but also simplifies an adjustment of the statement, if any other keyword than 'started' – e.g. 'stopped' – is to be searched for.
  

• In the present configuration, the Value for the placeholder is defined as static text for Variable name 1.
  

• This is followed by an event handler of the Show alert (Popup) type, which prepares the result of the SELECT statement stored in the variable records for a notification like the following (see below for details):

• The information should appear as a notification of the Type 'Info' (i.e. temporarily displayed on the right edge of the screen).
  
  

• The Title content builder defines a static text, for the notification headline.
  ►NOTE◄ In practice, a value resolver of the Value from localization type would actually be preferred, which provides a suitable localization entry.
  
  

• In the Message content builder, a concatenation of value resolvers controls access to the 'loading capacity' from the return value of the SELECT statement:
  
  

  • First, a Variable value resolver reads the variable records, whose value is always expected as a list (see the option Is collection of) of client objects (see Type) with a single data field (date_at), which can be empty if necessary.
    
    

  • Since the query used can return multiple 'matching rows', the decisive match at the first list position must be explicitly addressed by the List item resolver with the Mode 'Get first' and Offset 0.
    
    

  • Within the 'result row' determined in this way, the following Object property value resolver accesses the only field (latest_ts) with the searched timestamp. This is prepared for output by Format date, so that the user is not confronted with the huge number of milliseconds.
    
    

  • The concatenation of value resolvers is completed here by a Default value resolver, which outputs a statically defined text in cases where the searched log entry tag is not found at all. Then the variable records contains an empty list and the List item resolver for the first list value returns 'no value'.
    
    

The variant for the configuration shown on the right executes the notification via the Show alert (Popup) event action only if a suitable entry was found in the log table. Otherwise, after executing the Execute SQL query event action, the records variable returns a list object without entries.

The Is empty compare type used within the Entity property rule is negated here, so that the Show alert (Popup) event action placed in the 'Then' block is only executed if the log returns a 'match'.

►NOTE◄ The Default value resolver used for notification in the above configuration can be omitted within this case distinction if it can be assumed that the date_at column in the database table contains a timestamp for each log entry.

An event handler is configured as shown on the right:

• The event handling reacts to the Triggering event 'Finished' (see Working state (Events)), which is triggered when a business object is assigned the working state 'Finished'.

• Deletion in the interface table should be performed only for common business objects of certain types. For this purpose, a Check type (on 'Common business object') and an Entity property rule for the field 'Business object type' are AND-linked (collapsed in the image), which checks whether the type of the input object is named in a positive list.

• If the deletion is relevant, an event action of the Execute SQL query type is first executed under the Actions on passed rule, which passes the DELETE statement to the database and stores the returned number of deleted records in the deleted variable. Details about this are explained below.
  
  

• Then the return value is used to check whether records have been deleted (deleted> 0) via If then else.
  
  

• The user will only be notified about the deletion performed via the Show alert (Popup) if records have been deleted. A detailed description of the configuration for this event action is omitted here. Essentially, the components relevant to the output are combined by text concatenation. This accesses the value of the deleted variable, which contains the number of deleted records.

The Execute SQL query event action is parameterized as shown on the right:

• The return value is stored in the variable named deleted by the Store result as parameter.
  
  

• The database with the interface table who_is_who is to be accessible for the Lobster Data Platform / Orchestration server via the Alias scm set up for this purpose. The delete query defined in the SQL Query parameter is sent to this database.
  
  

• At runtime, the placeholders @1:l@ and @2:s@ defined in the SQL Query are replaced with the Values of the variables defined below with the Variable names 1 and 2.
  
  

• The placeholder @1:l@ is assigned the reference (reference) from the reference attribute 'Receipt No.' (RECEIPT_NO) of the just completed business object. This is previously converted from the String type to Long via the concatenated Input object (type safe) resolver, which the placeholder specifies to match the column definition of the interface table.
  
  ►NOTE◄ It is also possible to do without this explicit type conversion. However, an error (possibly with abort and rollback) occurs if the reference attribute contains a string at runtime for which the automatic type conversion to Long fails. In contrast, the explicit type conversion returns the value null in this case. Whether this causes an error, no effect or undesired effects, depends on the specific content of the SQL Query. If required, a Default value resolver can be concatenated in the definition for the Variable name, which assigns a specific value with the data type of the placeholder in case of conversion problems.
  
  

• The placeholder @2:s@ is assigned the internal name of the business object type to which the just completed business object belongs. In the runtime example, the text value LOT is for the type 'Lot/Batch'.