Skip to main content

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

Cloned controls and the UseKeys property

Updated on October 19, 2022

When interrogating applications that create multiple instances of controls with identical types, such as rows in a table or multiple document interface (MDI) child windows, use the UseKeys property to tell Pega Robot Studio to work with all of the controls through one interrogated object. UseKeys also allows you to work with an unknown number of identical items. Essentially, the cloned controls are a list of controls that are easier to work with in automations.

To enable cloning check the UseKeys property in the Property Grid for the highest level control that requires cloning. Enable UseKeys for the control to specify interactions with specific instances of the control in automation logic.

Note: The UseKeys and Key properties are available on all interrogated controls. However, the value of UseKeys is False by default and the Key property defaults to null.

When you interrogate an MDI window, Robot Studioidentifies a client and child control, as shown in the following figure:

MDI client and child controls
Figure showing MDI client and child controls in Robot Studio.

When you enable the UseKeys property for a control, it becomes a cloned control. The Palette shows how many instances are attached to a cloned control instead of showing the eye icon. If the control has 10 or more instances, the Palette will show 9+.

As you open multiple instances of the target (for example, the MDIChild window), multiple matched targets are displayed in the Targets section, as shown in the following figure:

Mutliple child windows
The Targets tab of the Application Designer view that shows multiple MDI child windows as matched targets.

  • 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.

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