cancel
Showing results for 
Search instead for 
Did you mean: 

Blue Prism 6.9 Issues

david.l.morris
Level 15
Hi Everyone,

Blue Prism 6.9 had a lot of fixes and enhancements that I was excited about. However, after testing some of these, it's a bit underwhelming and I'd like to see if anyone else has the same concerns as well as if there are workarounds for some of these issues.

1. Browser automation is much slower now when using the Path attribute. Yes, I know the concerns about using the Path attribute, but I sometimes use Get Path and dynamically manipulate the Path attribute to iterate over a webpage when otherwise Blue Prism is too slow to interact with it. I've had a handful of other qualified developers confirm on the same websites that this is the only viable solution. My question is why is it slow suddenly and is there some other combination of attributes that should make it faster? (Match Index does not improve the speed in this case)

2. Blue Prism browser automation in 6.9 is still slow. Blue Prism does a lot of things well, but finding attributes quickly in a web page is not one of them. Other automation tools do not have this issue. I've tested this myself. One of the reasons it is slow is that Navigate, Read, and Write stages do not have implicit wait times to allow for elements to appear, so we have to use Conditional Wait stages to wait for an element to appear. But what do you do when it takes Blue Prism 10, 20, 30 seconds to find an element? If you use a Wait stage and then a Read stage, you're waiting double the time when a Read stage, for example, could have a condition inside of it to wait for an element to appear and thus be more efficient. Anyway, this isn't an issue in particular with 6.9, but I feel like it deserves a mention in case I've been using Blue Prism wrong these past few years. Also, we need Match Reverse in Chrome/Firefox/Edge.

3. The Hover action was one of the biggest reasons I was excited about BP 6.9, but upon testing it I found that it is not actually Hovering the mouse cursor. Instead, it is activating the element's Hover trigger, which is not the same thing at all. This addition is certainly a good thing, and I've confirmed it does work in some cases. I have yet to implement it in a full-speed, back-office automation and haven't tried it in a ton of situations yet. But is there really still not a way to simply move the cursor to a particular element without clicking on it? Again, this is a thing in other automation tools, and Blue Prism needs it too.

4. The new feature involving the Tracking ID sounds cool, but in practice it doesn't appear to be thought out fully. There are two issues I've already come across and I expect that there are more. First, the Attach action of a Navigate stage does not output the Tracking ID, which means we can only use this feature if we newly launch the browser session. Maybe this is required based on how it works, such as Blue Prism may need to set something in the session when creating. I've no idea, but without the ability to Attach to a browser and then identify it by the Tracking ID, I am hesitant to use the feature at all. Second, the Tracking ID feature has broken Detach stages. Some automations I've seen do have detach/attach in them, and this is broken immediately in 6.9. I've tested this in two separate environments. If you don't use a Tracking ID, Detach just doesn't work at all which is a code breaking change in Blue Prism that obviously has a workaround but it involves no longer using the detach stage at all as well as having to edit who knows how many objects.

5. This is a small thing but noteworthy, in my opinion. The Release Notes of 6.9 say that Document Loaded was added to Wait stages, but actually Parent Document Loaded was added instead. Document Loaded is not available in 6.9. Those are two different things available in IE automation, and personally I'd like to see Document Loaded added to Chrome/Firefox/Edge automation as well.

Thanks for reading. Feel free to respond and tell me I'm wrong. My goal is to be told "No, Dave, you're dumb. Here's the right way to do that" and then I can cry in my pillow but be excited that the feature actually does work as intended or w/e. 😃

------------------------------
Dave Morris
Cano Ai
Atlanta, GA
------------------------------

Dave Morris, 3Ci at Southern Company
32 REPLIES 32

Hi Dave,

The version number of the extension has been increased from 2.2.0.2 to 2.2.0.3, though I appreciate that the store might just be truncating this to 2.2.0. We would normally look to increment the 3rd digit of the version number if we were releasing a patched version of BP core to work with the extension, but in this case as all the changes were extension side we only incremented the build number of the extension.

As a side note, we have been in discussions internally for a while about browser extension versioning and the decision has been made to start versioning the extension alongside the product moving forwards to reduce confusion when understanding which version to use with the version of Blue Prism you are using. This change is expected to be in place for the release of Blue Prism 6.10 onwards - all currently released versions of Blue Prism will continue to use the extensions that they use today as changing this would require a patch to point them at a newly versioned extension.

With regards to notifications about certain issues I don't believe we have something in place to handle this at the moment - significant issues are posted to the known issues support centre articles but I'm not aware of any other mechanisms that publish updates to users, which I think is what you'd ideally want to see happen.

Regards,
Rob

------------------------------
Robert Nicklin
Senior Product Owner
Blue Prism
Warrington, England
------------------------------
Robert Nicklin Product Manager Blue Prism Warrington, England

Hi Dave,

I would recommend you check out our Ideas portal and submit an enhancement request on this topic there. This way, you can track any updates to your specific request as it moves along the lifecycle, and you'll be notified if your enhancement is delivered. You can also follow any existing ideas you're interested in to receive updates on those enhancements as well. 

This blog post has more information on the ideas portal and how the review process works.

Thanks!

------------------------------
Melanie Giuliani
Online Community Manager
Blue Prism
------------------------------

Ah, gotcha. Makes sense that there's a version number past the 2.2.0.

I like the idea of the browser extension matching the version of Blue Prism.

Thanks!

------------------------------
Dave Morris
Cano Ai
Atlanta, GA
------------------------------

Dave Morris, 3Ci at Southern Company

Hi Melanie,

Yeah, I've voted on there and have submitted an idea that was delivered at one point. It's a bit cumbersome, but it may just be me wanting a traditional forum-like interface whereas it's organized as cards and hurts my brain. 😃 I'll give it another shot. 😃

------------------------------
Dave Morris
Cano Ai
Atlanta, GA
------------------------------

Dave Morris, 3Ci at Southern Company

Hi,

chrome web store shows 4 digits for earlier versions of BP extension, eg 1.0.6.3

I would highly appreciate to get informed of changes to extensions, especially when they come with automatic updates. 

Updates are done very restrictive in my company, only after being reviewed and tested in our environment. So i highly doubt any chrome web store version change will trigger automatic download. (I just checked another extension's version and my local differs to the latest version in web store).
So again it would be highly appreciated to get the info about updated extensions, otherwise we would just miss improvements. 

I would also highly appreciate getting the info, just in case existing browser automation processes behave differently, so we know if or if not this might be because of new version of extension. 

Additionally I would highly appreciate getting the info about updated extensions, just in case I can be sure when reading on community pages, if the behavior, fix, workaround, bug, ... related to extensions might also concern our Blue Prism installations.

------------------------------
Walter Koller
Solution Manager
Erste Group IT International GmbH
Europe/Vienna
------------------------------

Hi Robert,

Thanks for your previous update on the new version of the Edge Chrome V6.9 browser extension!

It seems that we currently are making use of the Edge Chrome V6.9 browser extentsion from the Microsoft store.
When viewing the extension in this store, it however seems that this extension has not yet been updated (last updated on 17 August 2020).

Can you confirm that this is the case? And if so, can you provide us with a time window for when we can expect the updated Edge Chrome V6.9 browser extension to hit the Microsoft Store?

Thanks in advance!

------------------------------
Arthur Philippa
RPA Developer
Port of Rotterdam
Europe/Amsterdam
------------------------------

I'm guessing they're just a little behind the intended schedule. They mentioned shooting for a fix on all 3 browsers by end of last week, but the Firefox extension was just updated this morning in the Add On store. I'm also guessing that they did it in order of precedence since the number of users/automations in each browser probably goes Chrome > Firefox > Edge. I'd expect they'll have an update out for the extension in Edge within the next couple days.

------------------------------
Dave Morris
Cano Ai
Atlanta, GA
------------------------------

Dave Morris, 3Ci at Southern Company

Hi Arthur,

Both the Firefox and Edge extensions were submitted to the respective stores on Monday morning, I believe the Firefox extension passed review yesterday and checking this morning I can now see the Edge extension has also been published to the store.

Regards,
Rob

------------------------------
Robert Nicklin
Senior Product Owner
Blue Prism
Warrington, England
------------------------------
Robert Nicklin Product Manager Blue Prism Warrington, England

Hi Robert,

Thanks for coming back to my query.

I can confirm that we now see an updated version of the BP browser extension in the Microsoft Store.
Moreover, with this new version running, we do see improvements in the speed of our Edge Chrome automations (same as when running V6.8).

So the slowness issue seems to be fixed!

------------------------------
Arthur Philippa
RPA Developer
Port of Rotterdam
Europe/Amsterdam
------------------------------

MarcoMatuttis1
Level 6
Especially your 2nd Point also bothered me a lot.​​

------------------------------
Marco Matuttis
Robot Process Automation Developer
INTER Krankenversicherung AG
Mannheim
------------------------------