cancel
Showing results for 
Search instead for 
Did you mean: 

Blue Prism UI mode not working in Chrome

BatakisNikos
Level 3
I have 2 environments, both have the same settings on Chrome, and BluePrism.
The one is on win10 and everything works fine, the other is on winServers where I am seeing the below issue.
The UI spying mode is not working on Chrome as it should.
Currently it is seeing the whole screen (everything below the URL bar) as one item while the buttons of <, >, refresh.URL field, etc. are being spied correctly.
Browser mode works fine as well for all elements within the screen.

Any ideas?

BP v6.10.1
Chrome v99.0.4844.84
Extension v6.10.1
1 BEST ANSWER

Best Answers

BatakisNikos
Level 3

Thank you @ewilson for your answer.
I was able to find the answer by going through the Troubleshooting Google Chrome guide for v6.10 in the link you sent me
(just a note that the link for 6.10 gets you to v6.9 and I had to change the url of the 6.9 guide from "https://bpdocs.blueprism.com/bp-6-9/en-us/z-pdf/chrome-firefox/v6.9%20User%20Guide%20-%20Native%20Chrome,%20Edge,%20and%20Firefox%20Integration.pdf" to "https://bpdocs.blueprism.com/bp-6-10/en-us/z-pdf/chrome-firefox/v6.10" in order to find the correct document.)

Basically the solution for me was the insertion of "--force-renderer-accessibility" at the URL of the start page in the creation of the Object's Application Modeller. Though it is kind of weird that this is not required in the other environment we are using.​

​​

View answer in original post

2 REPLIES 2

ewilson
Staff
Staff
Hi @BatakisNikos,

I'd start with the Chrome troubleshooting article available on the Support portal. You can find it here.

There are also various browser extensions issues that were fixed with the release of v6.10.3. Any chance you can upgrade? You can find the known issues list here.

Cheers,​
Eric

BatakisNikos
Level 3

Thank you @ewilson for your answer.
I was able to find the answer by going through the Troubleshooting Google Chrome guide for v6.10 in the link you sent me
(just a note that the link for 6.10 gets you to v6.9 and I had to change the url of the 6.9 guide from "https://bpdocs.blueprism.com/bp-6-9/en-us/z-pdf/chrome-firefox/v6.9%20User%20Guide%20-%20Native%20Chrome,%20Edge,%20and%20Firefox%20Integration.pdf" to "https://bpdocs.blueprism.com/bp-6-10/en-us/z-pdf/chrome-firefox/v6.10" in order to find the correct document.)

Basically the solution for me was the insertion of "--force-renderer-accessibility" at the URL of the start page in the creation of the Object's Application Modeller. Though it is kind of weird that this is not required in the other environment we are using.​

​​