Within the Windows adapter, matching occurs whenever the target application becomes idle. Idleness is defined as a certain period of time that has elapsed in which the application has not received any messages to create, destroy, or update controls.

Only visible controls are available for matching. However, if a matched control is subsequently made non-visible, Pega Robot Studio does not un-match it until the control is destroyed. When idleness occurs, Studio attempts to match only those controls that have raised the following events:

• Created
• Shown
• Activated
• Text Changed
• Parent Changed

Within the web adapter, matching occurs whenever a new web page is loaded into the browser. When a web page is loaded, it goes through stages:

• Uninitialized
• Loading
• Loaded
• Interactive
• Complete

Because some web pages may take several minutes to load completely, the web adapter matches when the page becomes interactive and again when the page becomes complete.

Like the Windows adapter, matching occurs within the Java adapter whenever the target application becomes idle. When idleness occurs, Studio attempts to match controls that have been recently added to the Java control hierarchy.

Within the Host adapter, matching occurs when the emulator or console presentation space is updated. The Host adapter first determines if the current screen has been modified, but not unloaded. If the current screen has been unloaded, the Host adapter attempts to match the new screen.