Question
Syntel
IN
Last activity: 1 Sep 2017 3:20 EDT
not able identify dynamically generated controls in Pega RPA
Hi Team,
we are trying to automate Pega 7.1.7 application by using Pega robotics automation, But we are unable to uniquely identify the controls like Submit, Approval, and Reject etc. We tried interrogating with select element. In run time it is generating exceptions like controls not matched. Please suggest is there any other approach to uniquely identify controls.
Thanks,
Vijay T
<Moderator Edit: Vidyaranjan | removed personal information>
Pegasystems Inc.
US
Can you attach a log - RuntimeLog.txt - so I can see exactly what is happening? Logs are written out to the %appdata%/openspan folder.
To enable logging:
- Open Pega Robotics Studio
- Go to Tools -> Options
- Then scroll down to 'Pega Robotics' and click on 'Runtime Diagnostics'
- Click the 'File Publisher' mode to ON if it is not already.
- Then click on 'Log Categories' under 'Runtime Diagnostics'
- Change the option 'All Categories' to 'Verbose'.
Westpac Banking Corporation
AU
Hi Vijay,
As per screen the element is not identified when you are running the automation, it means the matched rules at the time of interrogation are not matched when running the automation. So, can you check
1. Start interrogation and check whether interrogated elements are highlighted, if yes then it should work, If not then change the match rules.
2. If the button match rules are correct (step1 ) then check if the application url is changing dynamically? if yes then change match rules of application.
Note: You need to check the identified match rules at the time of interrogation and when running the automation are matching correctly or not.