Upgrade to 7.3.2 - Click Action on Buttons/Hyperlink not working in Chrome

[uncki2]

Dear Community members,

Hope you're doing well.

We have recently upgraded to BP 7.3.2 from v6.10.5, we have observed that CLICK action in NAVIGATE stage spied using Browser mode is not working in chrome-based applications.

Highlighting & focus of the element is working; however, action click is not working. Bot was able to click same button / link in BP 6.10.

For interim we have spied the element using UIA mode for clicking so that bot execution can continue.

However, I foresee a serious concern if browser mode can highlight the element but unable to click. Anyone have faced the similar issue before and how to resolve this? Any pointers would be greatly appreciated.

Chrome Version
BP Extension

[david.l.morris]

Check to see if there is JavaScript in the href attribute of the link by doing Right Click > Inspect on the element. You may need to do right click > inspect twice in a row for it to highlight in the Developer Tools pane.

--------------------------------------------------------------------------

Below is only applicable if there is JavaScript in the href attribute of the element.

This is one of the limitations introduced as of MV3 (Manifest Version 3). One of the workarounds is what you implemented which is to use UIA/AA to click it instead. There are one or two other workarounds too.

How do I work around the href JavaScript issue in Browser Automations? :

[BPE] BP-11545 / BP-12841 - Browser interactions with elements that trigger JavaScript fail to run when using Manifest V3 browser extensions :

I'll say this. Based on BP's documentation, it would lead me to think that 7.3.2 and other recent versions shouldn't have this issue, but (from my testing) all of the MV3 versions cannot use browser mode to click links where the href attribute has JavaScript in them, at least not without doing a special workaround.

Here's info about MV3: [IMPORTANT NOTIFICATION] IMPACT OF MANIFEST V3 ON USE OF CHROME AND EDGE BROWSERS AS PART OF BLUE PRISM AUTOMATIONS :

[uncki2]

Hi @david.l.morris ,

Apologies for the delay in response and than you so much for responding.
I tried the above approach to click submit button with regards to the JavaScript shown on the bottom left. However, navigate stage not able to click.

May I check if you have clicked based on the value shown when u hover over the button to be clicked?

Thanks alot in advance.

[david.l.morris]

While there are other workarounds listed in that support article, the only method I've tried is using UIA/AA to click it instead. Personally I'd just try to stick with that if it works. Plus UIA gets faster as of v7.4.1 anyway so it should run faster for you at that point. For now, AA is faster because of the ability to use Match Index and Match Reverse to increase the speed.

[uncki2]

HI @david.l.morris ,

Somehow, UIA mode is not reliable for us in one of the process where application is a legacy one. Every time new session is launched, attributes changes. Hence, thinking to use JavaScript as shown above in the earlier chat. 

Appreciate if you can provide some pointers how to use that to click.

Thanks.

[david.l.morris]

Try AA instead of UIA. If it's a browser mode object, then AA won't be available by default. But you can temporarily change the application type to Windows application, spy in AA, and then switch the application type back to Browser. Your AA elements will still work and you can still click highlight on them. Be sure to use Match Index and also try Match Reverse (try both True and False for Match Reverse and see which one is faster and use that).