Question
Ford Motor Company
MX
Last activity: 18 Oct 2023 19:06 EDT
Pega Roboitics Autmation loses the targets of the match rules, no matter how many times they are reassigned
Hello,
I am currently working on an automation using Pega Robot Studio v22. The automation involves accessing a web page, authenticating, and downloading files. I was able to successfully complete and test the automation previously, but suddenly, the match rules for almost all of my targets have started failing. I have attempted to regenerate the connection multiple times and even started the project from scratch on a VDI, but the issue persists.
Thank you for your assistance.
Accepted Solution
Updated: 18 Oct 2023 19:06 EDT
Pegasystems Inc.
US
@FernandaC16806626 I would examine what the match rules you are using are. If they are too specific, they may not work between sessions on the same application. A simple example would be the URL or Title match rule of a web page. If the URL or Title contained the customer's account number, then it would not match when you search for a different customer. You want to adjust those match rules to work for any account you search for. Whenever I see this scenario, I like to interrogate my application as expected and then restart it again to verify that everything is still matching as expected. If not, I would interrogate the same control(s) again and compare and contrast the match rule(s) used on the first control to what they are on the second. Often, you can see something here that differs that would allow you to make the required adjustments.
An even better solution might be to try using X-ray Vision to interrogate the application. This should take the matching complexity out of your hands. This is enabled by default in 22.1, so if it is failing while enabled, you might examine the Insights tab to see if it can provide some usable information.
@FernandaC16806626 I would examine what the match rules you are using are. If they are too specific, they may not work between sessions on the same application. A simple example would be the URL or Title match rule of a web page. If the URL or Title contained the customer's account number, then it would not match when you search for a different customer. You want to adjust those match rules to work for any account you search for. Whenever I see this scenario, I like to interrogate my application as expected and then restart it again to verify that everything is still matching as expected. If not, I would interrogate the same control(s) again and compare and contrast the match rule(s) used on the first control to what they are on the second. Often, you can see something here that differs that would allow you to make the required adjustments.
An even better solution might be to try using X-ray Vision to interrogate the application. This should take the matching complexity out of your hands. This is enabled by default in 22.1, so if it is failing while enabled, you might examine the Insights tab to see if it can provide some usable information.
If you are not using X-ray Vision and have DEBUG level logging enabled for Runtime, you should be able to search for the first control in the hierarchy that you expect to match. Any lines where the matching process failed will give you a reason why. It will log something like; {Type of} match rule failed for target X; target property was Y and match rule expects Z. Search for your control name preceded by the pipe character and a space (for example; | btnSave). This is very helpful when troubleshooting matching issues.