Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Matching optimizations

Updated on May 26, 2022

Pega Robot Studio only matches in response to events within an application to ensure good performance. Additionally, Studio performs a number of other matching optimizations.

Matching index

When a child control is created within Pega Robot Studio, the system automatically persists the index at which the target was found. Subsequently when matching, Studio begins at this index to find the control.

Element ID matching

A web developer can assign IDs to controls in a web app. You can match these controls using the Element ID match rule. This is the fastest way to match controls in a web app, particularly in very large web pages.

Tag matching

Within the web adapter, child controls are not matched using the full element hierarchy, because even simple web pages usually contain hundreds, possibly thousands, of elements. Instead, Robot Studio retrieves a collection of elements with the same tag as the control you are matching. For example, if Robot Studio is matching a text box, it retrieves all <input> elements to iterate and match against.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us