<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Using Chrome or Edge / utilizing the JavaScript insert/invoke function in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/Using-Chrome-or-Edge-utilizing-the-JavaScript-insert-invoke/m-p/102104#M48912</link>
    <description>&lt;P&gt;&lt;SPAN style="font-size: 9.0pt; font-family: 'Arial',sans-serif;"&gt;"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.&amp;nbsp; "&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN style="font-size: 9.0pt; font-family: 'Arial',sans-serif;"&gt;"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 &lt;STRONG&gt;end of 2022&lt;/STRONG&gt; and test their automations as part of that upgrade process.  "&lt;P&gt;&lt;/P&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 9.0pt; font-family: 'Arial',sans-serif;"&gt;if we are using the insert / invoke JavaScript in both msedge and chrome browser. it will not going to work from 2023 ?&lt;BR /&gt;if yes, any idea what will be work around ?&lt;BR /&gt;if we upgrade the BP from 6.10.1, we i get solution ?&lt;BR /&gt;Kindly suggest some solution or alternate approach to overcome this JavaScript activity.&lt;P&gt;&lt;/P&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 26 Jul 2022 07:26:40 GMT</pubDate>
    <dc:creator>sabarirajanm</dc:creator>
    <dc:date>2022-07-26T07:26:40Z</dc:date>
    <item>
      <title>Using Chrome or Edge / utilizing the JavaScript insert/invoke function</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Using-Chrome-or-Edge-utilizing-the-JavaScript-insert-invoke/m-p/102104#M48912</link>
      <description>&lt;P&gt;&lt;SPAN style="font-size: 9.0pt; font-family: 'Arial',sans-serif;"&gt;"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.&amp;nbsp; "&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN style="font-size: 9.0pt; font-family: 'Arial',sans-serif;"&gt;"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 &lt;STRONG&gt;end of 2022&lt;/STRONG&gt; and test their automations as part of that upgrade process.  "&lt;P&gt;&lt;/P&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 9.0pt; font-family: 'Arial',sans-serif;"&gt;if we are using the insert / invoke JavaScript in both msedge and chrome browser. it will not going to work from 2023 ?&lt;BR /&gt;if yes, any idea what will be work around ?&lt;BR /&gt;if we upgrade the BP from 6.10.1, we i get solution ?&lt;BR /&gt;Kindly suggest some solution or alternate approach to overcome this JavaScript activity.&lt;P&gt;&lt;/P&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 26 Jul 2022 07:26:40 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Using-Chrome-or-Edge-utilizing-the-JavaScript-insert-invoke/m-p/102104#M48912</guid>
      <dc:creator>sabarirajanm</dc:creator>
      <dc:date>2022-07-26T07:26:40Z</dc:date>
    </item>
    <item>
      <title>Re: Using Chrome or Edge / utilizing the JavaScript insert/invoke function</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Using-Chrome-or-Edge-utilizing-the-JavaScript-insert-invoke/m-p/102105#M48913</link>
      <description>Hi Sabarirajan M,&lt;BR /&gt;&lt;BR /&gt;I'm working on Blue Prism v7.1 where MV3 is already implemented.&lt;BR /&gt;I worked around this limitation by interacting with the browser through the Chrome DevTools Protocol using a library such as &lt;A href="https://github.com/cyrus-and/chrome-remote-interface" target="_blank" rel="noopener"&gt;chrome-remote-interface&lt;/A&gt;&lt;BR /&gt;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.&lt;BR /&gt;&lt;BR /&gt;I launch Chrome with the following launch parameter: &lt;EM&gt;--remote-debugging-port=9222&lt;/EM&gt;&lt;BR /&gt;&lt;BR /&gt;I write my function to a file surrounded by the appropriate chrome-remote-interface commands:&lt;BR /&gt;
&lt;PRE class="language-javascript"&gt;&lt;CODE&gt;const CDP = require('chrome-remote-interface');

CDP(async(client) =&amp;gt; {
    const {Network, Page, Runtime} = client;
Runtime.evaluate({expression: `console.log(1);
console.log(2);`});
	client.close()
})​&lt;/CODE&gt;&lt;/PRE&gt;
Then in the command line I execute this:
&lt;PRE class="language-javascript"&gt;&lt;CODE&gt;[path_to_nodeJS]\node --inspect=9222 [path_to_script]\script_name.js&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;
&lt;CODE&gt;&lt;/CODE&gt;For more information regarding the setup, installation and other commands you can reference the chrome-remote-interface documentation.&lt;BR /&gt;&lt;BR /&gt;There may be a better solution around or in the near future, but this works for me.&lt;BR /&gt;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.&lt;/P&gt;</description>
      <pubDate>Tue, 26 Jul 2022 13:34:32 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Using-Chrome-or-Edge-utilizing-the-JavaScript-insert-invoke/m-p/102105#M48913</guid>
      <dc:creator>diedoprel</dc:creator>
      <dc:date>2022-07-26T13:34:32Z</dc:date>
    </item>
  </channel>
</rss>

