Comprehensive and Detailed Explanation From Pega Robotics System Exact Extract:

During interrogation of web applications, developers often encounter dynamic or hidden controls — such as drop-down menus or hover-triggered lists — that do not immediately appear on the page.

To successfully interrogate these elements, Pega Robot Studio provides two essential tools:

The Delay option on the Interrogation Form, which allows the developer time to trigger the hidden control before capture.

The Select Element option, which enables precise selection of an element directly from the DOM, even if it is not immediately visible.

According to the Pega Robotics System Design and Implementation Guide, section “Interrogating Dynamic and Hidden Web Controls”:

“When interrogating hidden or dynamically rendered controls:

Use the Delay option on the Interrogation Form to give yourself time to hover over or activate a hidden control before Robot Studio attempts to capture it.

Use the Select Element option to manually highlight and select a control from the web application’s DOM, even when it is displayed only after an interaction such as mouse hover.These methods are particularly effective for controls that expand or render asynchronously, such as drop-down menus or tooltip-triggered elements.”

Detailed Step Reasoning:

C. Use the Delay option on the Interrogation Form.

Correct.

The Delay setting pauses the interrogation process for a specified number of seconds, allowing you to hover over the hidden element (e.g., AddressType menu) and make it visible before capture.

Once the menu appears, Pega Robot Studio can detect and interrogate it.

D. On the Interrogation Form, select Select Element.

Correct.

The Select Element tool allows manual selection of an element directly from the web page’s HTML DOM structure.

This is especially useful for hidden or dynamically rendered elements like the AddressType dropdown that may not be visible until hovered over.

Incorrect Options Explained:

A. In the Interrogation Form dialog box, select HTML Table Editor.

Incorrect.

The HTML Table Editor is used to inspect and modify HTML table-based controls (grid or table structures), not dynamic menus.

B. On the Web Controls tab, select the page, and then click List Web Controls.

Incorrect.

The List Web Controls option lists already recognized controls in the DOM but cannot reveal or capture hidden dynamic elements.

E. On the Application tab, click the Virtual Controls tab.

Incorrect.

Virtual Controls are used for defining custom controls when the default adapter cannot identify one, not for capturing hidden menu elements.

Final Correct Answer:

C. Use the Delay option on the Interrogation Form.

D. On the Interrogation Form, select Select Element.

To diagnose a failure occurring on a link from a control’s Properties call to a String service’s Equals(), you must place breakpoints on the event links immediately before the failing link so you can inspect the values being passed (for example, the account number) and confirm whether a null is being propagated.

Pega Robot Studio debugging guidance:

“Breakpoints can be set on event links to pause execution at specific steps in an automation. During a paused state, developers can inspect the values on connected data ports to determine whether null or unexpected values are being passed to the next step.”

“Place breakpoints upstream of the failing event to verify the value retrieved from a control (for example, via a Properties call) before it is sent into a service method (such as Equals).”

Option A shows a breakpoint on the event path feeding the Properties block and another just before the segment that calls Equals(). This allows you to stop exactly where the input to Equals(string2) would be evaluated and verify whether it is null.

Option C also places a breakpoint directly on the event link leading into the Properties/Equals segment, which is the correct spot to pause and inspect the data value before the comparison occurs.

Options B, D, and E place breakpoints either too early (not reaching the Properties/Equals path yet) or on unrelated branches, which won’t reliably expose the null value being passed into IStringService.Equals().

(Correct Order):

Start the interrogation for the Windows application.

Interrogate the Windows form.

Navigate to the window that contains the menu.

Select the control in the control hierarchy list.

In the More menu, select Add menu items.

In the Add Menu Items dialog box, select the menu items.

Click OK to save the selection

Unlike web or text-based controls, Windows application menus (such as File, Edit, or Help) are often rendered as non-standard Windows controls that cannot be directly interrogated using the bullseye tool.

Instead, Pega Robot Studio provides a specific method to add menu items through the interrogation hierarchy.

According to the Pega Robotics System Design and Implementation Guide, section “Interrogating Menu Items in Windows Applications”:

“Menu items in Windows applications are not directly interrogated through visual selection.

Instead, the process involves interrogating the parent form, identifying the menu control in the hierarchy, and then using the ‘Add Menu Items’ option to expose individual menu commands as controls.

Steps:

Start interrogation for the Windows adapter.

Interrogate the main form that contains the menu bar.

Navigate to the window containing the menu to ensure visibility.

In the control hierarchy, select the menu bar control.

From the More menu, choose Add menu items.

In the Add Menu Items dialog box, select the menu items to expose as interrogated controls.

Click OK to confirm and save your selections.”

Detailed Step Reasoning:

Start the interrogation for the Windows application.

Launches the adapter and begins the interrogation session.

Interrogate the Windows form.

Interrogates the main form containing the menu bar control (the top-level parent for menus).

Navigate to the window that contains the menu.

Ensures the correct active window is in focus for interrogation.

Select the control in the control hierarchy list.

Identifies the menu bar or parent control within the form’s hierarchy.

In the More menu, select Add menu items.

Opens the configuration dialog for menu interrogation.

In the Add Menu Items dialog box, select the menu items.

Displays a list of all available menu items to expose as automatable elements.

Click OK to save the selection.

Finalizes interrogation and creates the selected menu items as controls in the project hierarchy.

Final Ordered Steps:

Order

Interrogation Step

1

Start the interrogation for the Windows application.

2

Interrogate the Windows form.

3

Navigate to the window that contains the menu.

4

Select the control in the control hierarchy list.

5

In the More menu, select Add menu items.

6

In the Add Menu Items dialog box, select the menu items.

7

Click OK to save the selection.