Skip to main content
Verify the version tags to ensure you are consuming the intended content or, complete the latest version.

Interrogation in Pega Robot Studio

Interrogation is a technique that exposes the underlying objects of an enterprise application and uniquely identifies each object. Interrogation results in the creation of controls that correspond to application objects. Pega Robot Studio creates a representation of the object called a control.

You can then use the objects to build automation workflows and monitor application events. While application adapters help you establish the connection with an enterprise application, interrogation exposes the Properties, Methods, and Events of the application and its objects. The interrogation process does not change the underlying source code or property values of the application.

For example, a company uses a CRM application that requires the worker to log in before a query can be performed. Before automating the login process for the CRM application, a robotics solutions developer must interrogate the controls on the login screen of the CRM application. The robotic solutions developer performs the interrogation and interrogates the username field, password field, and the login button.

Following the interrogation, Pega Robot Studio displays the representation of objects of the CRM application.

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

When you interrogate an object, Pega Robot Studio saves the attributes (matched rules) of the object. Each time the application runs within the solution, the solution compares the object property values of the application to the saved matched rule values of the interrogated objects. If the values agree, the object matches, and automation can proceed.

Best practices for interrogation

  • Interrogate all controls needed for a business case.
  • Method-test all objects to ensure that the automation can interact with them.
  • Use interrogation to provide developer access to the applications used in the project.
  • Use interrogation to perform a preliminary interrogation of the application controls.
  • 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.
  • Find issues first to reduce development time before developing the solution.

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