Application Categories

The article provides instructions on working with the search pattern editor in various application categories. General information about the search pattern is available here.

When adding multiple components to a pattern, each row with a component can be detailed in the table below:

In patterns, you can use variable names in the format {variable}. If you specify a variable, the robot will replace the variable with the appropriate value during operation. Variable calls can be written directly in JSON.

You can also use the * character in field values.

ATTENTION! In the editor window for all modes except SAP, the UI explorer tool is available, which allows you to thoroughly examine application interfaces. Working with the tool is described in more detail in the UI explorer section.

Browser

The search pattern for the Browser application category looks like this:

In the Title field, specify the name of the website where you need to find the component. In the URL field, specify the website address. Do not forget to select the browser type in the parameter next to the Title field. Chrome is selected in the picture above.

To add a component manually:

1. Click the button, then highlight the new row and enter data in the Tag, Text, Index (starts at one) and Search in Frames (search inside iframe elements) fields.
2. To refine the search, enter the names and values of the attributes of the desired component in the table (key, value). If you specify multiple rows, the search for the element in the robotized application will go deeper from the top pattern.

To add a component automatically, click the Select Component button and click the desired component in the desired browser window. You can also use the quick add button on the element itself.

Search in Frames

The “Search in Frames” property is designed to search for elements inside HTML frames <frame> and <iframe>, but there are the following limitations when using it:

• 1. Protected Frames: If the frame is protected by browser settings, searching inside it is not possible.
• 2. Different Domains: The search does not work if the frame content is loaded from a different domain or host. For example:
  • Works: <iframe src="/local.html"> (same domain).
  • Does not work: <iframe src="https://externaldomain.com/page.html"> (different domain).

To ensure correct operation, make sure that the frame loads content from the same domain and has no security restrictions.

Desktop

The search pattern for Desktop applications looks like this:

To connect to the desired application, simply fill in one of the fields:

• Title — the name of the main window of the desktop application.
  ‼️ Important. If the title contains the special character \, it will need to be escaped. Examples: ◽С:\\Users\\User1\\AppData\\Local\\Primo.Exchange\\ext.chrome - Notepad++; ◽ *\\cmd.exe.
• Process — the name of the process of the running Windows application.

If both fields are filled in, both values will be considered simultaneously.

In the upper right corner, there is a parameter with user interface automation types :

Automation technology provides programmatic access to the user interface elements of the application. The following types are available:

• UIAUTOMATION — the default value. Suitable for desktop applications running according to Win32 rules.
• UIAUTOMATION_UIA — it is recommended to use it if it is not possible to access the desired control in UIAUTOMATION mode. Older technology.
  Note: If UIAUTOMATION_UIA mode was selected first, and then — UIAUTOMATION, then for the correct operation of the search pattern, you will need to restart Studio.
• MSAA — Microsoft Active Accessibility library. Has more limitations than UIAUTOMATION, as it is an outdated technology. Addressing MSAA will be useful in a limited number of cases: for example, when searching for text elements, it is necessary to use the Role identification property.
• JAVA and JAVA_EXT — designed for Java applications. The Java type uses the Primo extension, the Java_Ext type — extensions from third-party vendors.
  When working with Java, the bitness of the Studio and the Robot must match the bitness of Java.
• RDP — used to work with remote desktop applications using the RDP protocol.

To add a component manually:

1. Click the button, highlight the new row and enter data in the AutomationID, Name, ClassName, ControlType, LocalizedControlType and Index (starts at one) fields. The fields are filled in selectively. At the same time, the AutomationID property is one of the most important when searching: it does not change with each launch and uniquely identifies the component.
2. To refine the search, enter the names and values of the attributes of the desired component in the table (key, value). If you specify multiple rows, the search for the element in the robotized application will go deeper from the top pattern.

The Quick Search function is enabled by default and activates a shortened search route for the component in the application. It is recommended to use this parameter when working with 1C. Quick search does not support searching for BoundingRectangle, AcceleratorKey, ProcessId, NativeWindowHandle, Orientation identification properties. If the component is not found in quick search mode, disable the parameter and search again.

To add a component automatically, use the Select Component option and click the desired element in the window of the desired application. A window will open for selecting the component properties (control tree). If it is necessary to bypass the entire tree of properties, use the Automatically button with the Full control tree checkbox checked:

SAP

When working with SAP, it is recommended to use specialized components.

The search pattern for the SAP category looks like this:

If you are working with SAP WebView, the search pattern will look like this:

The Browser area is a search pattern for the browser.

In SAP search patterns, the * character is allowed.

Containers

It is still recommended to use Studio elements in conjunction with containers to save computer resources. At the same time, connecting to an application/browser will be configured inside the corresponding container. For example, if we use the Attach Application container, then the desktop application title and automation type are configured in its properties, and not in the search pattern editor.

If the element is placed in a container, then the search pattern editor window will also open in Container mode:

At the same time, the search parameters will correspond to the application type — desktop or web. By analogy with the parameters for the Browser or Desktop category.