cancel
Showing results for 
Search instead for 
Did you mean: 

Using Chrome or Edge / utilizing the JavaScript insert/invoke function

sabarirajanm
Level 3

"If the utility identifies you are affected (i.e., Using Chrome or Edge / utilizing the JavaScript insert/invoke function) please make sure your organization completes the survey sent to them by their account or customer success manager.  "
"Customers who currently use either of these browsers as part of their automations must upgrade to a version of Blue Prism software that offers MV3 support by the end of 2022 and test their automations as part of that upgrade process.  "

if we are using the insert / invoke JavaScript in both msedge and chrome browser. it will not going to work from 2023 ?
if yes, any idea what will be work around ?
if we upgrade the BP from 6.10.1, we i get solution ?
Kindly suggest some solution or alternate approach to overcome this JavaScript activity.

1 REPLY 1

diedoprel
Level 3
Hi Sabarirajan M,

I'm working on Blue Prism v7.1 where MV3 is already implemented.
I worked around this limitation by interacting with the browser through the Chrome DevTools Protocol using a library such as chrome-remote-interface
This is a NodeJS library which allows you to send JS snippets and other things from a command line interface, there's also python alternatives.

I launch Chrome with the following launch parameter: --remote-debugging-port=9222

I write my function to a file surrounded by the appropriate chrome-remote-interface commands:
const CDP = require('chrome-remote-interface');

CDP(async(client) => {
    const {Network, Page, Runtime} = client;
Runtime.evaluate({expression: `console.log(1);
console.log(2);`});
	client.close()
})​
Then in the command line I execute this:
[path_to_nodeJS]\node --inspect=9222 [path_to_script]\script_name.js

For more information regarding the setup, installation and other commands you can reference the chrome-remote-interface documentation.

There may be a better solution around or in the near future, but this works for me.
Do note that by opening the remote-debugging-port on your chrome instance, any other application could access everything in your browser, so use it at your own risk.