The Set values event action shown on the right has been added to the 'Customize Search' block via the context menu for the icon (see above). It defines two assignments:

• The first assignment assigns the value of the firstResult variable to the 'First result' (firstResult) property of the 'Search' to be executed.
  
  

• The second assignment assigns the value of the maxResults variable to the 'Max. results' (maxResults) property of the 'Search' to be executed.

►NOTE◄ As no Target host is defined, the Object property value resolvers for the Target values (on the left in the image) refer to the configured 'Search' that applies to the reference object in the 'Customize Search' block.

The entity type of this reference object depends on which of the Search types is selected in the 'Search' parameter (see above). The label in the header of the 'Customize Search' block varies accordingly ('Customize Search', 'Customize tuple search' or 'Customize CSV search').

The screenshot on the right shows the configuration for Event actions in the 'Customize Search' block of a Search (Event action) that performs a 'CSV search':

• Within the Set values event action, a Simple property restriction is created as the Target host via Create instance and stored in the variable filter via the concatenated Store value as variable value resolver.
  
  

• Three value assignments to properties of the newly created Simple property restriction instance follow:
  
  

  • The 'Projection' (projection) property is assigned the value provided by the Variable propertyName.
    
    

  • The 'Compare type' (compareType) property is assigned the key value ilike as static text. This is the comparison operator for upper/lower case indifferent text patterns.
    
    

  • The 'String' (stringValue) property is assigned the value of the variable beginsWith concatenated with the static text value % (wildcard for any number of characters). This link forces a 'Begins with' match of the value from the property addressed by propertyName.
    
    ►NOTE◄ We do not take into account the special case here that the value from the beginsWith variable contains characters that would have to be 'masked' in the context of the database (e.g. wildcard characters such as % or _).

• Once the Simple property restriction has been created and parameterized, it is assigned as a whole to the 'Where' condition (where) property of the search in the following Set value event action. This access is made possible by the filter variable, which contains a reference to the created SimplePropertySearch object (see Store value as variable).

►NOTE◄ If the configuration for the 'Where' condition of the CSV search does provide for one or more (static) Restrictions, our assignment completely overwrites these. If the created restriction is intended to be considered in addition to existing restrictions, a Search junction must be adapted or created in order to create either an AND or an OR relationship as required.

The screenshot on the right shows the configuration for a Search (for the Company accounts Entity) within a Search (Event action), which actually only serves to create a Search object in the context of event handling, which is then to be used by an Open view (Action) as a filter condition for the view to be opened.

►NOTE◄ As execution of the Search cannot be prevented, it is configured here so that it generates as little data as possible. The Mode 'First result value' is therefore selected so that only one or no company account is saved in the dummy variable as the return value.

• The value-giving component of this search is the more or less complex Where condition. Specific details about its content are not relevant. The AND operation shown in the image can conceal an extensive and multi-nested logical aggregate.
  
  

• In the Customize Search block, a Set value event action assigns the 'Search' available there as a reference object to a mySearch variable, which, unlike the entity variable managed by the system, can also be accessed after the search has been executed by subsequent Event actions outside the 'Customize Search' block.
  
  

►IMPORTANT◄ In the subsequent Open view (Action) event action, the Search object is accessed as a whole. The Where condition defined in the where property is not directly adopted as a restriction for the opened overview. Instead, a Sub search restriction is created from the definition of the Search as a whole, which is AND-linked with any existing 'restriction' for the view to be opened (see Custom overviews). This procedure may seem unnecessarily complicated, but it ensures, among other things, that the Where condition in the transferred Search can also use Restrictions that address fields from Joins. The restrictive effect of INNER Joins can also only be transferred indirectly – with a 'detour' via the Sub search restriction – to the View name.

The Open view (Action) event action shown on the right opens a standard 'Company account overview' for which the 'Where' condition from the Search object in the mySearch variable applies as a 'restriction' if the value of this variable is resolved as a Search object in the Form data parameter.

►IMPORTANT◄ In case a Tuple search or CSV search is defined in the Search (Event action) in the mySearch variable instead of the Search, the addressed company overview would be opened but not restricted based on the search.

It is important to understand why: Open view (Action) only attempts to derive a restriction for the View name to be opened from the Form data parameter if its value corresponds to the 'Search' (Search) or 'Search restriction' (ISearchRestriction) type. A TupleSearch object would not pass this test. The applicable default handling for Form data (see Open view (Action) does not result in a selection (or an unintended selection due to the lack of an ID property) of an entity in the context of the opened overview.