The event handling shown on the right is aimed at preventing the saving of changes for existing tracking state entries by means of an Abort action, provided that these affect Orders:

• The only Triggering event selected is 'Update' from the Common (Events) category.
  
  

• The Validating rule includes three AND-linked criteria that are deliberately arranged precisely in the following sequence with performance in mind:
  
  

  • The initial check type determines whether the 'Update' event has been triggered for a tracking state entry. Only then will further checks take place.
    
    

  • The first Entity property rule ensures that the tracking state entry in the input value per the statusOwner property refers to the 'Order' class. Only in this case is the referenced object for the last check criterion requested from the server.
    
    

  • The second Entity property rule requests the order referenced in the tracking state entry from the server via the Tracking-state-referenced-object value resolver to verify that its tracking state attribute for the tracking state type 'Current' (CURRENT) refers to the ID (id) of the changed tracking state entry via the trackingStatusEntryId properties. If this is not the case, the Validating rule as a whole is considered 'passed'.

• The only Action on passed rule is an Abort action, which aborts the transaction to change the tracking state entry and informs the user about it with a message of the 'Semantic Exception' type.

After clicking on a ribbon button, a notification of the 'Info' type should be displayed on the right side of the screen for each 'current' tracking state change, containing the following information:

In the title:

• Time of tracking state change
  (Date is 'Today' by definition)

• Added tracking state code

• Entity type (tracking state owner)

In the message:

• More information about the 'referenced object'
  (here: ID ~ Owner ID/Current working state)

The tracking state entries relevant for display are provided by a Search action. This returns a chronologically sorted list of all tracking state entries readable in the context of the session that have been created since the beginning of today's tag (see Relative date with time) in a variable whatsNew.

The following For each loop action iterates over the tracking state entries in the whatsNew variable:

For each entry a Show alert (Popup) event action is executed in which the desired information is prepared:

• The information for the Title can all be obtained directly from the tracking state entry, which is the reference object within the loop. This processing is done here by a Concat strings value resolver, the configuration of which will not be discussed in detail.
  
  

• Of the data specified for the Message, only the tracking state owner ID is available in the tracking state entry (statusOwnerId property). For all other data, access to the 'referenced object' (aka tracking state owner) is necessary. The Tracking-state-referenced-object value resolver returns the entity in question starting from the reference object (tracking state entry). The Type of referenced object here must be the overarching 'Entity' class, so that all types of tracking state owners can be covered.
  
  

• The concatenated Template value resolver defines the formatting of selected content from the data object of the entity determined to be the 'referenced object' for the tracking state entry.

►NOTE◄ The id and onwerId properties are 'entity attributes' that each entity type uses. A working state, on the other hand, is not supported by every entity type that can 'own' a tracking state. A position of a business transaction object, according to its class, is considered as an 'Entity' but not as a 'Business transaction object'. It has no working state, but tracking states can be added to it. If specific detail data should appear for different entity types, case distinctions are required.