Skip to main content

Additional web application match rules

Developers use the HTML tags within web applications to identify the application object, allowing Pega Robot Studio to match each target consistently. In addition to the web-based match rules which work for web applications running in IE compatibility mode, there are also match rules that work best for applications running in Google Chrome and Microsoft Edge. The process for using match rules between these types of applications is similar but with a few distinctions. 

The first difference is the number and scope of Chrome and Microsoft Edge application match rules versus the web-based default match rules. Unlike the default web application match rules, applications in Chrome and Edge use only three match rules:

  • Attribute Value match rule
  • Property match rule
  • Control Children match rule


Another difference between the web application match rules and the web-based default match rules is the number of times a web application match rule within Chrome and Edge can apply to one interrogated target.

When web applications are running in IE compatibility mode, a specific match rule is usable only once per interrogated control. Pega Robot Studio displays a match rule designer window when adding or editing other web application match rules to a target on the application project item tab. Adding a property or attribute match rule for any property or attribute for a control provides a more robust matching capability for Chrome and Edge web applications.

match rule designer

Attribute Value match rule

Developers use the Attribute Value match rule to select an attribute that has a unique value. You decide which attributes to use, when to use the attribute, and what values to use for the attributes. Select the attribute based on its associated value from the Match Rule Designer window to manually add an attribute match rule for a Chrome or Edge web application project item control.

In the following image, you see how the Match Rule Designer specifies the id as the attribute with the value of login_button.

attribute value match designer

Property match rule

While interrogating a specific control in a web application, you see that each control contains inherited properties from the class or object that makes them unique to that control type. The Property match rule exposes the inherited control properties, such as those from a parent, to identify an interrogated object. The properties of a control’s parent can also be used as match rules for the interrogated control.

In the following example, the defaultValue object is a string set to Sign In until the user selects the check box.

default value match rule designer

Control Children match rule

The Control Children match rule uses the matching criteria of a child control to designate the match of a parent object. The rule first matches the child objects. When the child matches, the parent then matches. The number of children selected determines if the parent matches. For example, if three children are selected, all three must be matched before the parent matches.

In the following image, user_name and user-pass are the control children of the highlighted control, where the user_name target is the selected child to match first for the parent control, form1

control children match rule designer

Check your knowledge with the following interaction.

This Topic is available in the following Module:

If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice