Status : Draft

Criteria Management

Criteria are rules set by the user and used by the Desktop connectors to recognize defined elements (applications, pages or items) in the running entities (Web pages, Windows items, and so on).

A connector recognizes a running entity as an element if the entity properties match the element criteria.

A criterion applies to one property of the entity. It comprises:

  • The 'name' of the property,
  • The 'value' that the entity property with this name must match,
  • The 'operator' used by the Desktop connector to test this match.


Available properties

The available property names depend on:

  • The technology of the entity (in other words, the 'URL' property is available in a Web Page but not a Windows Page),
  • The connector (in other words, the Window connector only tests the 'EXE' property of a Windows application).

When Desktop Studio captures a running entity, it only captures the properties available for use in criteria.


Available operators

Here is a list of all available operators:

Text Properties
Any The property can have any value
Empty The property value must be empty
Full The property value must be equal to the criterion value
Part The property value must contain the criterion value
Starts The property value must start with the criterion value
Ends The property value must end with the criterion value
Like The property value must match the criterion value considered as a regex
Numeric Properties
= The property must be equal to the criterion value
< The property must be lower to the criterion value
> The property must be greater to the criterion value
The property must be less than or equal to the criterion value
>= The property must be greater than or equal to the criterion value

Desktop Studio displays only the available operators, depending on:

  • The type of the property (for example text, numeric, boolean, or enumerated),
  • The connector (in other words, the Web connector manages the 'starts-with' operator on text properties but the Windows connector does not).


Available Combinations of Criteria: AND / OR

The general rule is that all of the element's criteria must be satisfied before an entity is recognized (AND).

However, some connectors accept two (or more) criteria on the same property.
In these cases, only one of these criteria must match (OR).

When the OR combination is available on a property, the Criterion Editor shows the Add button.

This button adds a criterion on the edited property, even if a criterion on this property already exists.


The Criterion Editor is available in the Criteria Tool Window.

The Criterion Editor can manage four types of properties:

  • Text properties :
    text criterion
  • Numeric properties :
    text criterion
  • Boolean properties :
    text criterion
  • Enumerated properties :
    text criterion


The procedure of adding a criterion is the same regardless of the element type (application, page or item):

  • Edit (optional) the criterion value and the operator in the Criterion Editor,
  • Click the Update button to validate the criterion.

A captured property can be quickly added as a criterion by double-clicking it in the Captured Data Tool Window.


To update a criterion:

  • Select it in the “Criteria list”,
  • Update the criterion value or the operator in the Criterion Editor,
  • Click the Update button to validate your change.


To delete a criterion:

  • Right-click on it in the “Criteria list”,
  • Select 'Remove criterion' in the context menu, or click the Delete button.


The criteria technical document can be automatically generated using the “Build criterion doc.” menu item from the “File” menu. This generates an additional HTML document for each PSC file. It is named 'PSCName.html':

The document is generated with the 'docGeneration_V1.xsl' file located in the following (default) location: C:\Program files\SAP Intelligent RPA\Studio\configuration\xsd

The file used for this purpose can be modified by changing the 'XSLDocTechFile' entry of the StudioExplorer.xml file.

Here is a brief example of this documentation: