UIA mode not working with Microsoft edge

[MayankTiwari1]

Hi all,

I'm using BP version 6.10.1 and edge chromium browser but for some reason BP is only able to spy with browser mode and no other mode is working with edge, I want use UIA mode. Please help!

------------------------------
Mayank Tiwari
------------------------------

[david.l.morris]

For me, UIA works without using the accessibility flag, but you could try adding it to the URL.

Something like this:
https://google.com --force-renderer-accessibility

Let me know if it still doesn't work.

------------------------------
Dave Morris
Cano Ai
Atlanta, GA
------------------------------

[NileshJadhavBP]

Hey Mayank....

Some time UI mode is worked with Chrome and Edge however some time its not, that time you have to add 

"--force-renderer-accessibility" after your URL in Application Modeler.

Like - https://Portal.blueprism.com --force-renderer-accessibility

I hope it will solve your issue

------------------------------
Nilesh Jadhav
Senior RPA Specialist
ADP
India
------------------------------

[DipinDevP]

@david.l.morris @NileshJadhavBP 

Thanks for the information!

How we can use --force-renderer-accessibility if our object is set with A browser which already running instead of Launching?

[stepher]

Myank,

A couple of notes.

1) I believe the full argument should be "--force-renderer-accessibility=complete".  The '=complete' portion became necessary after a specific version of Chrome/MS Edge.  It seems like it has been a year or two.

2) I believe you need to have the argument in place when you originally started the browser (either using a form of the 'Launch' logic, or in the 'Start Process' action).

Best of luck,

Red

[DipinDevP]

@stepher Thanks for your help and suggestion!
I have still issues with UI automation while using A browser which already running option.
I have launched browser/application with --force-renderer-accessibility=complete in first object and attached from second object.

[david.l.morris]

I just wanted to pipe in and mention that '--force-renderer-accessibility' should work again. The '=complete' part was only necessary for a bit and it was a bug that Microsoft fixed. That said, we still use the '=complete' part as well because it should result in the same thing.

@DipinDevP Can you provide more information, such as your version of Blue Prism and any other info you can such as screenshots of your application modeller or the attach logic and its inputs, etc. For most versions of Blue Prism, the way you are describing what you're doing should work. So, either there is a bug, something is different with your system, or you aren't actually doing it correctly. We can't really guess which one it is without more information.