Blue Prism 7.3.2 Element Not working in UI

[bmarshhouseloan]

We currently are migrating to 7.3.2. We have a servicing system and one element will not work in the control room from the App Modeller. We have tried UI/UIA/Browser and they all work in debug mode and when viewing from Bastion. However, it fails 100% in the control room. The same process and element spy works in 7.0.1 in the control room without issue. The element is a link that invokes a JavaScript that transitions the page after logging in. Any ideas on how to invoke the JavaScript or what may be different between 7.3.2 and 7.0.1?

[SouravSaha]

Hi @bmarshhouseloan,

Please check the two threads below, they might help fix your issue-

https://community.blueprism.com/t5/Product-Forum/Process-fails-to-identify-web-elements-when-not-logged-into/td-p/122394

https://community.blueprism.com/t5/Product-Forum/Blue-Prism-UI-Automation-Failing-after-Chrome-Edge-Update-to-140/td-p/122492

[david.l.morris]

If there is JavaScript in the href attribute, I assume it may just not work anymore and you need to use a different method to click it. I've only run into this once so far, and we just had to use UIA or AA to click the link instead. There is a checkbox in the system tab that controls whether Blue Prism will throw an exception instead of trying to click it. But if you uncheck that box, it may just silently fail to do it at all which is what happened for us.

Here's a quote from this page in the bpdocs:

Prevent click events where JavaScript in href attributes may result in Content Security Policy violation

Specifies that clicking a web element where JavaScript is present in an href attribute will be prevented. From Blue Prism 7.2 onwards, each Click action is evaluated at the browser. If there is a potential Content Security Policy violation, then, when selected, the action is rejected and an exception is raised in Blue Prism. In these situations users can spy the web element as a UI Automation element instead, and use this to perform the action.

[bmarshhouseloan]

That would explain why I am receiving an exception with Browser mode stating "Access Denied". I will try again with UI. I have a wait stage and it works in debug and Bastion but it is not found in Control Room. 

[RoopkiranBevara]

Hi @bmarshhouseloan , Good day!! Kindly use the AA mode as an alternative method. Try to change the application type in modeler configuration & enable AA mode to spy the required elements & change back to the web based application in the modeler. Use AA Elements as primary & use UI/Browser elements as secondary due to continuous failing of UI/Browser elements. Hope this method works fine.

Regards,

Roopkiran.