Blue Prism pros and cons

I find Blue Prism's debugging functionality to be quite useful.

All of the processes that we've automated have been completed successfully, and the bots are able to process them as expected.

Blue Prism is highly scalable and reliable.

It's fast to get up and running if you use a cloud deployment.

RPA processes are helpful when we need interaction with different applications and close the technical gaps between them. In one of the use cases that we evaluated, there was a single Excel template from a vendor. The Excel file has 7,000 objects, and it included information about the part numbers, prices, and some of the details about each object of the aircraft. This file had to be input to SAP, so a human had to enter these 7,000 objects one by one, which is a pretty mechanical and uninteresting task. The RPA bot was easily able to import this file. Without RPA, this import had to be done by a person who had to do the same task 7,000 times just to import one contract.

The object design way of implementing things actually brings a lot of reusability for us because you can design your objects once and leverage them in multiple automations.

Blue Prism currently supports SQL Servers and structured data.

We have integrated the product with our centralized infra-monitoring tool, which gives us real-time insights into BOT health and also the health of the underlying resources.

Mostly we use the Design Studio to develop the automation. It's great. We put them into deployment and have the automated process running. It's essentially the Design Studio for Blue Prism and the entire methodology of delivery that is the most useful or valuable to us.

The technical support is very good.

Occasionally, there may be stability issues where certain nodes begin to behave erratically and produce errors.

All of the processes that we've automated have been completed successfully, and the bots are able to process them as expected.

Blue Prism is not very flexible when it comes to integrations.

From a monitoring perspective, the way the screens are set up, or the reporting within Blue Prism, is not really user-friendly. You need a technical person to basically put that up. It's not necessarily easily viewable.

There are some security issues in Blue Prism. The German vendor Servicetrace is way better. This is also reflected in the Gartner report where Servicetrace is mentioned as the tool of choice in high-security environments. So, security, particularly in terms of administration, needs to be improved. We must have the possibility to prevent the administration from taking a look at the ongoing process. When we have restricted data flow, the operations team should not be able to take a look at the data that is processed.

The control room is still the desktop version, which restricts access. You can't really access it from anywhere.

The solution can be improved by switching off data DB and including a report section.

Emerging technologies adoption is a challenge for every organization, especially the products which address productivity/automation.

It's not very easy to use. There is some learning curve that you need to manage as an individual.

Blue Prism can improve a lot. The interaction with Google Chrome can be massively improved. I know in the next version there are slight improvements. We don't know how much, but we are comparing them. At this moment, Google Chrome is a massive issue within the toolset, due to the way Google Chrome receives updates regularly but Blue Prism is unable to cope. The spy method of Google Chrome is not as user-friendly as Internet Explorer is. However, Internet Explorer is being discontinued from their support, therefore it's not the best browser to be using. This has caused us major issues in the last six months.