Blue Prism UI Automation Failing after Chrome / Edge Update to 140

[Adrian__Dones]

Hi guys,

Hope all of you are well and have a great week start.

Starting from last week (around Wednesday~Thursday) Blue Prism fails while running to identify properly the fields spied using UI Automation mode.

While trying to check in Application Modeler if the fields can still be visible, they were successfully identified, but while running the whole process, somehow the process remains blocked while trying to access those fields.

The interesting part is that after re-spying the fields using UI-Automation (just to test if a new fresh set of fields would make the cut) the bot still fails.

Just to mention, the process worked properly without any errors more than 2 years and all of a sudden it failed to work anymore.

Please let me know if this is a general issue and/or how it can be fixed.

Much appreciated all your help 🙂

[david.l.morris]

@DeclanKeeton I came across an issue today where I found that the same element spied in UIA had different attribute values from one machine to another with the same Edge version and with both launching using the flag as a launch parameter.

I don't know if that's the same issue you're seeing or not, but what I did was figure out what both possibilities were and I configured a single element in app modeller with wildcards and/or regex matches so that it supported both.

For example, I found that one element on one machine could have a UIA Control Type of "Button" and another machine might have the same element with a UIA Control Type of "MenuItem". I changed the match type to Regex and set the value to "MenuItem|Button" which means "either MenuItem or Button". Something to consider when you're adjusting attributes then is to keep the same original attributes working properly and adjust to make it flexible enough to support the new attribute values at the same time. A second option there might be to just have 2 separate app modeller elements representing the same page element and two different paths in a wait stage. 

[Denis__Dennehy]

Great information David.

On Not being allowed to control MS Edge updates, difficult one.  It should never be for the RPA team to control it, but there should be a different group for the robots so that update is part of a governed change control - that is for the IT service team to engage and do,  they are adding additional operational risk by not doing that so it should be possible to get exec sponsorship to do it.

The one type of company where that is often not possible at all are BPO service providers, they usually get what they are given with little ability to change it - that incluces having to automate via citrix desktops etc.