Pega Robotic Process Automation Reviews

The most valuable part of the solution is integration with CRM tools. This product offers seamless integration with other tools, and it is much more useful in digital transformation. It depends upon easy licenses.

The 2021 version of Pega Robotic Process Animation is really light.

It's a scalable product.

Its stability has been good.

The orchestration needs to be better.

It needs to offer an end-to-end solution similar to Google Chrome Universal Web adapters. They have few limitations in comparison. 

Technical support could be more helpful. 

We'd like to see more automation in terms of picking up on changes surrounding the browser. If it could automatically identify the attributes of the expected controls.

I've been using the solution for about four or five years. 

It is a stable, reliable product. There are no bugs or glitches. It doesn't crash or freeze. 

The solution scales very well. It's not hard to expand as needed.

We have experience with Pega technical support. They are okay. They do have limitations concerning the projects. Their response is fast enough. However, the answers they provide could be better.

Neutral

I'm using Pega, UiPath, and also Blue Prism.

The initial setup is  moderate, not simple, and not complex. Adding integrations can make it a bit more complex. 

A team of two to three people would be able to handle deployment and maintenance tasks. 

We found the 2021 version very light and could handle the initial product ourselves. 

I don't have too much knowledge of the exact pricing of the product.

We did take time to evaluate other solutions. Pega does come with integration capabilities. UiPath does a lot of maintenance, which is helpful. Of course, depending on your implementation plans with RPA, orchestration, and the cloud, that would be something you'd have to consider when choosing the product to use. 

We have a partnership with Pega. 

How the solution is deployed depends on the client's requirements. They can have it on the cloud if the customer and the client requires it to be on the cloud. That said, even though it is on the cloud, it's again via machines to be used before the robotics part.

I'd rate the solution eight out of ten. 

Our use cases are for the RD and the RDP processes. I'm the technical project manager. 

This solution is a kind of visual studio base. You can do a lot of things with it including adding custom DOLs. The most valuable feature is the logs. The solution is user-friendly, easy to understand and has many features including the ability to track. Pega has a very quick loading time which makes for great performance and provides good data transcripts. 

One of the difficulties we have is not knowing when we will receive alerts.

I've been using this solution for about 10 years. 

The solution is very stable. 

The customer support is excellent. 

Positive

The initial process is very straightforward. 

We've definitely seen a return on the investment in this product. 

The solution is quite expensive.

Concept-wise, all robotics platforms are similar. The difference between them is in the technical aspects, the methods and properties. Once you start learning Pega, the additional skills can easily double up because sometimes you need to write your code in a visual studio, making it also a visual studio platform.

I rate this solution nine out of 10. 

We use it mostly in banking, telecom, and also in government. It will be useful for intelligent workflow management. It can be helpful for you to make adaptive decisions. So, it has got some kind of feature called adaptive buttons. Wherein it will understand the user's persona and recommend the next best action and the next desktop.

In Pega, the UI has to be improved because that is the most challenging area that most of our customers ask for because we have to depend on some other React JS or some other tool to bring that kind of UI experience. So, there is a lot of room for improvement in terms of UI and UX.

I have been using this solution for five years. I'm using Pega as a tool for our organization.

It is a scalable solution. We work for different customers, in my particular area there are around 200 customer. It is a B2B solution.  

The deployment process depends on which project we are working on and what kind of delivery we are doing. Also, it depends from customer to customer. 

So, maybe if it is a decisioning framework as it is in telecom, maybe it will take at least six months because it has to self-learn the models, and there is a continuous interaction between artificial intelligence and machine learning teams. But if it is a typical workflow, maybe it is easier, but it depends on how quality engineers are working on that particular workflow. It changes from customer to customer.

I am a system integrator. A solution architect or enterprise architect can help with the deployment. So, the work is shared between the deployment. So, there will be a technical team from the system integrator side, there will be a team who works on the support side, and there will be different team members on the customer side. So, typically, there are ten people involved in the process.

The licensing cost is too high. And the amount which the customers are spending; I don't know if they are getting that kind of value at this particular time when they are setting it up.

The solution has a pay-as-you-go type. So, the pricing depends on the customer and how Pega is dealing with them. 

It is a good start, but as long as you're learning the framework that has been developed by Pega, that will take them far. But in the next five years or ten years, I don't see much visibility because there is a lot of competition across the local vendors, as there are many new local vendors entering the marketplace. Microsoft is giving tough competition to many low-code vendors.

Overall, I would rate the solution a six out of ten.

My experience was predominantly Pega Robotic solutions. I worked as an individual contributor with the developers. And I worked with the team, I led a team of five members in the last organization.

We worked in insurance. My last couple of projects were in insurance. It is mostly back-end process automation, like manual tedious tasks. One of the latest use cases we worked on was for creating third-party cases for dubious claims. Every insurance agency has an investigative third-party company that investigates dubious claims. Every time we have to log a claim, it was a very tedious task. Previously, each day, users would log about 150 claims with the third party and each one would take five to six minutes. We have automated this process.

The data entry and the automation of data entry are the most valuable aspects of the product. It was very smooth and very seamless to create automations. There was no scope for any errors and it was really error-free. That really helped us.

The initial setup was pretty easy.

There aren’t many areas for improvement. The process itself was really fine. There was no unnecessary jargon and unnecessary steps.

In one of the past projects, however, I observed they made it unnecessarily complex by, let's just say, exporting a screenshot at the end of each step which was cumbersome - especially when you could just save it in a drive locally or a shared drive. Extra necessary steps just make the automation complex. You really need to think out the process and simplify as much as possible to avoid complexity.

I would like to see some features improved that are already in there. One thing is the ease of deployment. They have integrated the deployment. They have tied the deployment with the Pega BPM product, the robot manager. You need to have the BPM installed. On top of that, you need to install this robotic manager solution. I understand that they want to tie their products together and make customers use both or all of their products in one suite; however, it can be annoying. It makes things unnecessarily complex. It would have been great if they just provided a standalone deployment system.

Features-wise, I'd like to see the OCR Optical Character Recognition. Pega is way behind its competitors in terms of OCR implementation and OCR capabilities. I'd like to see that improve. I haven't personally tried out many OCR solutions, however, on a proof of concept level, we did a few things and there is significant room for improvement there.

I've been working with RPA solutions for about five years now. I’ve used Pega from the beginning. My entire RPA experience was predominantly with Pega Robotics and also WinAutomation. It’s been around four years now.

The solution was stable. There were no bugs or glitches and it didn’t crash or freeze. It was reliable.

Just in the UK, there were about seven to eight people using the solution. It is not done 24 hours a day. There are no dedicated resources. Manually, we may work on it for one to two hours a day. Once it’s deployed, just one or two machines are needed to run the solution.

I have found the solution to be scalable.

Pega Robotics itself makes solutions really scalable. If you want to integrate it into this process with existing automation, you could just plug in this project to the existing ones. The scalability is really good.

I personally have dealt with multiple issues and have gotten support from them. The response time is definitely quick. The turnaround time is good. However, when solutions get tricky, where the answer is not straightforward, and there is research that needs to be done, they take time. That is quite understandable. However, it would've been great if solutions were provided quicker. You don't reach out to them unless it is absolutely essential. First, you try to fix it internally. Once you reach out to them, it’s vital to get a quick resolution. Therefore, that turnaround time is imperative.

Neutral

I also have experience with WinAutomation.

This use case itself is not that complex, which meant the setup was easy. It is pretty much a straightforward solution. It is A to B to C. There were no exceptions. On paper, it was a very good solution with a good process and a very stable process at that, which made things easy. Some are relatively easy to implement. They vary. I’ve had others that were harder in the past.

The last project was entirely an individual project. For the deployment, we tested along with the user. We did user acceptance testing. Once it was approved by everyone, we did a pilot run, and then we handed this over to the deployment team. They deployed it. They were a team of six or seven members. They handled setups individually as well. Typically there are not more than three hands on an entire solution. Once the solution was handed over to the client, it took them a day or two to set everything up.

Maintenance is handled via tickets. If there are any improvements to be made, we get tickets and resolve the issue. The engineers typically work on the solution and fix anything. Upgrades depend on the ticket's priority. It’s allocated to whoever has time to pick it up and action the maintenance.

The ROI is good. RPA, in general, provides a good return on investment. Pega Robotics is not an exception. They’re exceptionally good

Licensing is based on the number of machines that you deploy it on. Usually, it is based on the other products you buy per anum or per machine. In Pega Robotics, it is based on the number of solutions you deploy and the number of times you run. The cost is variable. My previous client worked based on this hourly model, the number of robots and the number of solutions that are run. They also provided per machine.

Pega doesn't just provide these robotic solutions. It comes with their BPM products as well. It depends on what the client uses. If the client uses this along with the BPM products, They might get added discounts, et cetera. Every contract is unique.

I’m a customer and end-user.

We started with the eighth version. The last one I used was 19.1. Until the latest build from February, we used the 19 version, the 19.1s. We stopped using the solution in February.

I’d rate the solution seven out of ten.

If a person is familiar with the .NET framework, it will be a great visual studio in general. Plus, picking up Pega Robotics will be very easy for them. It’s good in general to brush up on programming skills, along with Pega Robotics. If you need to add capabilities out of the scope or out of the realm of abilities of the tool, programming is essential to customize your solution.

We use the product for workflow automation features. 

The platform's most valuable feature is the ability to perform most tasks reliably. It efficiently integrates with other systems and automates various tasks.

The solution's configuration and settings could be more comprehensive. 

We have been using Pega Robotics Automation for approximately five years.

Internally, Pega Robotics Automation is deployed in a private cloud behind a Virtual Private Cloud (VPC). However, it is also exposed to customers through a public cloud to automate their solutions.

The setup process is complex. It varies depending on the case and system integration, but it tends to be more challenging overall.

I rate the product a seven out of ten. 

This is a client solution that assists operational teams on a daily basis. If a client wants to automate tasks, they provide their requirements to us and we build a solution for them using Pega to deploy onto their infrastructure. 

We have a very large operational team and we are able to avoid mistakes and ensure accuracy and speed using Pega.

There have been some scenarios where the bot was not able to replace some of the controls and could not recognize and personalize the task we wanted to automate.

This is a stable solution. The stability is dependant on the solution that an architect provides for their particular bot. It also depends on the design and the development that was done.

We have also use UiPath which is also a good tool. UiPath has a couple of new features which give it the edge over other solutions. 

The complexity of the initial setup depends on if the customer is new and if they have an existing enterprise structure environment. This determines the kind of installation that is needed.

I would rate this solution a seven out of ten. 

The solution is primarily used for any process automation. However, it is also is great for any DevOps deployment. It's a zero-code, no-code kind of development as well. 

The low-code/no-code development aspect of the solution is great. 

It's a pretty good, robust application. 

The product has been very scalable.

The stability is good. 

Technical support is great. They know what they are talking about. 

The development experience needs to be improved. It could be better.

The initial setup could be a bit easier. 

I've been using the solution for four years or more. 

The stability of the product is very good. It's robust and reliable. There are no bugs or glitches. It doesn't crash or freeze. 

The scalability of the product is great. If a company needs to expand it, it can do so. it's not a problem. 

We have ten customers on Pega right now. 

Technical support is pretty decent. We're very satisfied with the level of attention we get when we need assistance. They are pretty knowledgeable. We have no complaints. 

We would like to see the initial setup be a bit easier. Right now, it's a complex process. 

The initial setup only took about six to eight hours or so. 

We have a big team that can handle deployment or maintenance. We have about 30 or 40 people who can handle any related tasks. We have mostly engineers and then a few team leads. If you include the team leads, we're looking at about 50 or so people that can cover this area. 

There are different licensing models for the product on offer. 

I'd rate the solution at an eight out of ten. 

I'd advise potential new users to do process evaluation with respect to Pega before you jump in. It's a complete end-to-end product suite. You have to know which product suite is applicable to your environment.

The most valuable feature is the workflow. The workflow system is very intuitive.

It would be nice if they brought in some pre-defined functions such as drag and drop coding.

I would like to see an enhanced auditing feature included.

I have been working with Pega Robotic Process Automation for 36 months, three years.

We are using the latest version.

It's a stable solution. We have not had any issues.

It's a scalable product.

I have a team of approximately 50 people who are core Pega developers.

The community support is awesome. They answer your questions and they support them.

The technical support is okay. I would not rate them a ten, but maybe a six or a seven out of ten.

I have used other solutions and if you were to ask me about Robotic Process Automation, I would first choose Blue Prism and Pega would be second. The last would be WorkFusion.

The initial setup was straightforward.

It took a couple of weeks for the team to set it up.

We have our in-house community for Pega deployment. In fact, I lead the community.

Pricing is handled by my legal team. This is something that is out of my control or knowledge.

For anyone who is interested in using this solution, I would suggest doing a POC, (Proof of Concept) before the implementation.

Blue Prism, is a little better.

I would rate this solution an eight out of ten.