• A Validating rule is actually irrelevant for the workflow. Therefore, a Static rule with the default condition 'true' is used here, so that the Actions on passed rule are executed unconditionally. At this point, it would be conceivable to check whether a value exists for the variable eanNumber, via which the value of the text attribute 'EAN number' is transferred.
  
  

• Among the Actions on passed rule, a Search (Event action) is executed first, which is not described here in detail. The module label ('reference = eanNumber') refers to the 'condition' for searched Documents, namely that their entry for the 'reference' (reference) field must completely match the value of the text attribute 'EAN number' (here: Variable eanNumber). The search is executed as a 'tuple search' that returns the ID (id) field for all Documents found as a single column (Property projection). The return value of the tuple search is stored as a 'search value' in the documents variable.

• The following event action For each loop iterates over the 'rows' from the 'search value', i.e. a 'list of client objects'. With each single client object Show document (Event action) is executed, where the single Object property id is assigned to the parameter.

►NOTE◄ In the example, it is assumed that the relevant 'EAN number' is specified in the 'Reference' field when uploading documents for certain articles. Whether the document was actually assigned during the upload (see Assigning documents) is irrelevant for the assignment by the Search (Event action) in the Client workflow. The 'reference' is used here – completely bypassing the actual assignment logic for documents – as a search criterion to find 'matching' documents. If necessary, an additional search criterion (e.g. for the Document type) could be used to prevent random finds.