Interrogating Cloneable Targets

When interrogating an application that contains cloned controls, you can confirm matching for each clone by using the Make Prototype function. This function applies the match rules used when the initial target instance (the prototype) was interrogated to a clone of the target by setting the clone as the prototype.

This example shows the Make Prototype function for an example CRM application that contains three MDI child windows open during interrogation:

In this example, the window with Text New Call 2 was the initially interrogated window – the prototype. To ensure the match rules used for this window are valid for the other cloned windows (New Call 1 and New Call 3), change the prototype designation using the Make Prototype function. In the illustration above, selecting Make Prototype for the New Call 3 MDIChild_NewCall window will make that window the prototype and will apply the established match rules to the New Call 3 window. This way, you can review the matching status of the window and all of its child objects.

In the sample CRM application, an account number label is displayed on each MDI child window. The label is matched using the Windows Text match rule. So for the prototype window, the label is matched by its text. However, the account number label text differs on other instances of the Child window and would therefore fail to match. Using Make Prototype for other instances of the MDI child window would show that the label is not matched.


Related information

Key Property

Cloned Controls

Match Rules Overview


Privacy | Trademarks | Terms of Use | Feedback

Updated: 18 June 2020

© 2016 - 2020 Pegasystems Inc.  Cambridge, MA All rights reserved.


OpenSpan data classification label