Question
ford
US
Last activity: 30 May 2024 9:29 EDT
Interrogate a web application
I tried to interrogate a web application, the step for clicking menu. After interrogation, I tried to run all for test. It only launches the application, and didn't click the menu.
I attached the screenshot
Pegasystems Inc.
US
Updated: 29 Apr 2024 13:27 EDT
ford
US
@ThomasSasnett I don't need login process, it's in internal network, and SSO enabled. I tried recording the steps in QuickStart, and got "The control is not matched" errors, so I started manual interrogation.
I attached the steps I need to automate, and I start the interrogation after application launched.
Pegasystems Inc.
US
@HuiW17144569 I am not sure how much assistance I can be without access to your application. If you perform these steps during interrogation, are you seeing the controls matching?
Forvandle
IN
@HuiW17144569 use on the control rise events method
Pegasystems Inc.
US
@HuiW17144569Are you using X-ray Vision or traditional match rules? If you are using traditional match rules, what are the match rules you are using for the menu? Can you post a screenshot of your Hierarchy of the control in the Palette? Do you see matching stopping at a specific control in that hierarchy?
Eclantiqx Digital Private limited
IN
-
Verify the Interrogation:
Ensure the element (menu) has been correctly interrogated. During interrogation, make sure you are selecting the right element and that it is properly highlighted in the application.
-
Element Matching:Check if the element’s properties (such as ID, Name, XPath, etc.) used for matching are unique and consistent. Sometimes dynamic elements might change properties on each load, making them difficult to match.
-
Wait Conditions:Add appropriate wait stages to ensure the element is available and clickable before performing the click action. In Pega RPA, you can use the
WaitForCreatemethod to wait for the element to be available. -
Ensure Visibility:Ensure the element is visible and enabled before attempting to click it. Sometimes elements might be present in the DOM but not visible or interactable.
-
Debugging:Run the automation step-by-step using breakpoints to see exactly where it fails. This can help identify if the element is not found or if some other issue is preventing the click action.Check for Frames/IFrames: If the menu is inside a frame or iframe, ensure that you are switching to the correct frame before trying to interact with the element.
-
Verify the Interrogation:
Ensure the element (menu) has been correctly interrogated. During interrogation, make sure you are selecting the right element and that it is properly highlighted in the application.
-
Element Matching:Check if the element’s properties (such as ID, Name, XPath, etc.) used for matching are unique and consistent. Sometimes dynamic elements might change properties on each load, making them difficult to match.
-
Wait Conditions:Add appropriate wait stages to ensure the element is available and clickable before performing the click action. In Pega RPA, you can use the
WaitForCreatemethod to wait for the element to be available. -
Ensure Visibility:Ensure the element is visible and enabled before attempting to click it. Sometimes elements might be present in the DOM but not visible or interactable.
-
Debugging:Run the automation step-by-step using breakpoints to see exactly where it fails. This can help identify if the element is not found or if some other issue is preventing the click action.Check for Frames/IFrames: If the menu is inside a frame or iframe, ensure that you are switching to the correct frame before trying to interact with the element.
- Dynamic Elements: If the menu element's properties change dynamically, consider using more stable attributes or a combination of attributes to locate the element.
- Browser Compatibility: Ensure that the browser and its settings are compatible with Pega RPA. Sometimes, certain browser settings or versions may cause issues with automation scripts.
Infosys
IN
Hi @HuiW17144569,
First need to check the browser extension after that you can provide the application URL in robot studio and start the interrogation. After interrogation build your logic in the studio and run that after the Robot automates that process, if it fails while interrogating properties the matching rule was not successful. for this, you need to test the control for every property/button/link and also check hidden controls like web controls/ text controls/link controls.
Regards,
Sai G
@HuiW17144569Is your menu item matching at Runtime? Have you tried automating the login process as potentially a more basic step?