cancel
Showing results for 
Search instead for 
Did you mean: 

Insert Fragment | Invoke Javascript is not working BP 7.2

JadielLeyendeck
Level 2

Hi All,

brief summary

We are updating the browsers to manifest v3, and with that, and we got the javascript functions affected, so to work around until bp 7.2 the blue prism was provided a BAA app with JavaScript Invoker, but in the 7.2 version, it was fixed so the normal extension contains the JavaScript Invoker as documentation bellow.

https://bpdocs.blueprism.com/en-us/browser-compatibility.htm

My issue:

I'm migrating the bots from bp 6.7 to 7.2, My Browser is not receiving the javascript command sent by BluePrism, there is no error in Browser Console, but also does not return any exception in the blue prism, the issue occurs for both insert and invoke method.

I created the Html Page Bellow for the proposal test, so anyway if i try to insert a fragment passing "

document.getElementById('1').disabled = false" or call the function in the header nothing happens.
<html>

<head>
    <script>
        function myFunction() {
            document.getElementById('1').disabled = false;
        } 
    </script>
</head>

<body>
    <input id="1" name="2" type="text" disabled>
</body>

</html>

Best Regards.

1 BEST ANSWER

Helpful Answers

Hi @JadielLeyendeck

I wanted to highlight something here around the comment that Blue Prism 7.2 was "fixed so that the normal extension contains the JavaScript invoker". You're right that Blue Prism 7.2 now includes the Selenium based JavaScript invoker component that was introduced in the Browser Automation Agent (BAA) solution, but this isn't incorporated into the browser extensions themselves and is instead deployed alongside the core Blue Prism installation. The key point that I wanted to make is that the setup conditions that applied to objects and runtime resources that are intended to insert/invoke JavaScript with MV3 browser extensions remain the same as they were under BAA conditions, namely:

  • The object must have a debug port specified in the URL for launching the browser (therefore attaching to a browser won't work - unless the browser was previously launched with a debug specified)
  • The right version of the web driver for the browser in question (either Chrome or Edge) should be installed onto the machine on which the automation will run

If these requirements are met and you're still not seeing your JavaScript inserted/invoked as expected, then I suspect the best option will be to raise a support ticket as that doesn't align to what we'd expect to see with an installation of Blue Prism 7.2 and an automation that worked previously with the BAA solution.

Hope this helps!

Rob

Robert Nicklin Product Manager Blue Prism Warrington, England

View answer in original post

2 REPLIES 2

Hi @JadielLeyendeck

I wanted to highlight something here around the comment that Blue Prism 7.2 was "fixed so that the normal extension contains the JavaScript invoker". You're right that Blue Prism 7.2 now includes the Selenium based JavaScript invoker component that was introduced in the Browser Automation Agent (BAA) solution, but this isn't incorporated into the browser extensions themselves and is instead deployed alongside the core Blue Prism installation. The key point that I wanted to make is that the setup conditions that applied to objects and runtime resources that are intended to insert/invoke JavaScript with MV3 browser extensions remain the same as they were under BAA conditions, namely:

  • The object must have a debug port specified in the URL for launching the browser (therefore attaching to a browser won't work - unless the browser was previously launched with a debug specified)
  • The right version of the web driver for the browser in question (either Chrome or Edge) should be installed onto the machine on which the automation will run

If these requirements are met and you're still not seeing your JavaScript inserted/invoked as expected, then I suspect the best option will be to raise a support ticket as that doesn't align to what we'd expect to see with an installation of Blue Prism 7.2 and an automation that worked previously with the BAA solution.

Hope this helps!

Rob

Robert Nicklin Product Manager Blue Prism Warrington, England

JadielLeyendeck
Level 2

Hi @robert.nicklin 

Thank you for your answer, actually your guess was right, the problem was the Chrome driver was different from the Google browser generating a communication issue between the applications, anyway, I think there is a gap in this process seems like there is no feedback route to bp if the javascript code was run successfully in the browser.