29-03-22 04:11 PM
Answered! Go to Answer.
30-03-22 02:40 PM
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.
30-03-22 12:24 AM
30-03-22 02:40 PM
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.