09-02-24 11:01 AM
Answered! Go to Answer.
09-02-24 11:45 AM
Hello @mmostaquim,
It sounds like you're encountering a common issue with website automation. Sometimes, despite being able to identify elements in spy mode, Blue Prism Web Browser may struggle to interact with them using the "Navigate" stage and the "Click" option.
I've experienced similar situations before, and it's possible that the issue lies in the way the website was constructed. One alternative method to overcome this challenge is to try mapping the element using either the UIA Mode or the Accessibility Mode in Blue Prism. These modes can sometimes provide a more reliable way to interact with elements on the webpage.
To enable Accessibility Automation mode, you can add the following command after the website URL in the launch stage (if the URL is being parameterized) or in the Application Wizard: "--force-renderer-accessibility".
If you open Chrome and in the URL go to chrome://accessibility it'll open another page with the accessibility settings. The "--force-renderer-accessibility" string turns on most if not all of the Accessibility Modes in that tab. I believe this will help you Accessibility Technical Documentation - The Chromium Projects
Give this approach a try and see if it resolves the issue for you. If you continue to encounter difficulties, feel free to provide more details, and I'll do my best to assist you further.
If I answered your question, please mark it as the "Best Answer."
09-02-24 11:45 AM
Hello @mmostaquim,
It sounds like you're encountering a common issue with website automation. Sometimes, despite being able to identify elements in spy mode, Blue Prism Web Browser may struggle to interact with them using the "Navigate" stage and the "Click" option.
I've experienced similar situations before, and it's possible that the issue lies in the way the website was constructed. One alternative method to overcome this challenge is to try mapping the element using either the UIA Mode or the Accessibility Mode in Blue Prism. These modes can sometimes provide a more reliable way to interact with elements on the webpage.
To enable Accessibility Automation mode, you can add the following command after the website URL in the launch stage (if the URL is being parameterized) or in the Application Wizard: "--force-renderer-accessibility".
If you open Chrome and in the URL go to chrome://accessibility it'll open another page with the accessibility settings. The "--force-renderer-accessibility" string turns on most if not all of the Accessibility Modes in that tab. I believe this will help you Accessibility Technical Documentation - The Chromium Projects
Give this approach a try and see if it resolves the issue for you. If you continue to encounter difficulties, feel free to provide more details, and I'll do my best to assist you further.
If I answered your question, please mark it as the "Best Answer."
09-02-24 12:43 PM
Thank you for the information. I tried with UI Automation. It worked for me.
09-02-24 01:17 PM
Hi @mmostaquim,
If I answered your question, please mark it as the "Best Answer."