Skip to main content

Interrogation in Pega Robot Studio

Interrogation is the process of identifying the components within an application that you want to automate. The interrogation process begins when you press the interrogation button and launch interrogation mode. From there, you locate a target object in the application, and the system uniquely identifies the target object through one or more of its properties. Once the system identifies the target, it adds the target to the palette as a control object of the application project item.

The developer uses the controls to build automation workflows and manage events and processes within the application. During the interrogation process, the application project items establish a connection with the enterprise application but do not change the underlying source code or property values.

For example, a company using a CRM application requires workers to log in before performing a request. Before automating the CRM application's login process, developers interrogate the application's login screen. The developer performs the interrogation process and examines the username and password fields and the login button.

Following the interrogation process, Pega Robot Studio displays the representation of the CRM application's control objects within the Interrogation form.

Screenshot showing the hierarchy of interrogated objects from the CRM application in Pega Robot Studio

Each time the application runs within the project, it compares the application's target object property values to the saved matched rule values of the interrogated controls. If the values do not match, the developer investigates the match rules and corresponding values. Based on their findings, developers can re-interrogate or reconfigure the target object.

Best practices for interrogation

The following interrogation best practices, and their benefits, are listed in the following table:

Best Practices


Interrogate all controls needed for the business case to ensure controls needed for your automation.

 Checking all controls allows verification of which controls to interrogate.

Method-test all objects to ensure that the automation can interact with them properly.

Testing ensures the automation steps will work in the production environment.

Use interrogation to provide developer access to the applications used in the project.

Using interrogation also allows IT a chance to ensure applications are correctly installed and have the correct access.

Use interrogation to perform a preliminary examination of the application controls.

Interrogation allows developers to understand the complexity of the application and learn how the controls communicate better.

Provide developer access to give an advance look into possible issues with interrogation that may require adjustments to the interrogation process, or even the project itself, to meet the specific requirements.

Early developer access allows developers the chance to make sure controls are available within the hierarchy and, if necessary, re-interrogate the application to ensure they are using the right ones.

Find issues first to reduce development time before developing the solution.

Having a clear understanding of the controls in an application allows developers to quickly and efficiently create automations.

Use repetitive interrogation to review values and match rules. Re-interrogating the system controls allows the developer to verify match rules and data values with different test data.

Check your knowledge with the following interaction.

This Topic is available in the following Modules:

If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

100% found this content useful

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice