We're a customer and end-user. 

If a person wants to use this product, they need to know what is happening and how it runs. If the person is new and needs to run the solution, they need to follow the use case that the developers are giving to understand how the bot will run. With so many people, what they do is when the bot is running, they disturb some of the applications, and the bot will close or give exceptions.

If a person intends to use coding, they really do need a good grasp of what it is they want to build. Only them should they move into actual development. It will make it easier in the end if there's a good understanding at the outset. 

In any case, after two or three months of using the solution, chances are you'll have enough knowledge to be able to help train others. 

I'd rate the solution eight out of ten. If it was faster and had less complexity I would rate it higher. 

My work is focused on RPA solutions, so I know UiPath RPA and Pega Robotic Process Automation.

I'm using version 19.1 of Pega Robotic Process Automation.

In terms of the number of users of Pega Robotic Process Automation, that would depend on where you're using the solution. For example, I worked with one of the telecom providers that had fifty thousand users. I worked with a client in the banking sector and that organization had five thousand users of Pega Robotic Process Automation. Note that I've worked on the text automation or assisted automation only, not on the process automation.

In terms of maintenance, you only need two to three people to maintain Pega Robotic Process Automation.

I'd rate the solution six out of ten. It could be simplified, however, being able to code your own automation is very powerful. 

Pega is an LCNC platform, so learning Pega is very easy. It would not cost you even a single penny to start learning it. Everything is available on YouTube and the cloud. You should have at least a basic idea of Pega before doing any installations or using it. As a program manager and as the head of robotic process automation, I've seen people burning their hands with smaller companies. They didn't have any idea. They picked up the project just to make some money and then came to me. It would be ideal if someone from the IT team of the customer at least does a basic Pega course, which is totally free, before implementing it.

For workflows, Pega is the ideal tool. It's probably one of the best and one of the first ones in the world, but in terms of RPA, there are many other players, such as Automation Anywhere and UiPath, who are ahead of Pega. That's not because of the technology they have. That's because of the marketing and sales initiatives that they have. For example, currently, UiPath is the market leader in RPA, but UiPath's product is not as good as Automation Anywhere. UiPath is the leader because their sales team is very aggressive. So, it's not about the technology part. There are many aspects of how a particular product grows. Pega is not expanding its operations into Asia, Japan, Australia, New Zealand, etc. Until and unless you have a global presence, you will not be counted as number one even if you are the best in the market.

I'd rate Pega a seven out of ten. Its rating would be a bit lesser than UiPath and Automation Anywhere. 

Overall, I would rate the solution an eight out of ten.

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.

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 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. 

I would rate the product a seven out of ten. Pega has RPA and DPA. Pega is fantastic when it comes to DPA. The same is not the case with RPA. Pega's RPA is not on par with other tools and needs a lot of improvement. 

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.

In the past, we had an RPA solution set up with Pega. Then our company got bought out. The other company was using Automation Anywhere, so we are in the midst of transitioning Automation Anywhere.  We have platforms paid for by the different entities right now. Before we could get Pega really started, the company that bought us kind of squashed it. We got it up and running and installed. However, I haven't developed an entire solution on it yet due to the changes in our organization.

With Pega, there are two different parts: the platform and the actual automation software. In terms of the versions we're using, I believe the automation software is called OpenSpan and is 19.1 and the platform is 8.1.

In terms of advice, I would give to users considering using Pega, I'd caution to make sure you get an outside contractor that knows what they're doing. We had something on the books for that. Then, due to budget cuts, there was a hiring freeze, so that never got implemented. That definitely hurt the implementation of the project.

I would give the solution a seven out of ten. It wasn't bad at automating. It was just a little complicated to implement.

I would rate this solution a seven out of ten. 

I think that they are improving the IDE with the new and latest features that will help to do things in a faster way.

I would rate this solution a nine out of ten.

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.

It is a good, mature robotic process automation solution. Pega is also broadening its landscape by building on top of PRPC (CRM, EPC, etc.), and with a cloud offering available, it is a genuine contender to compete with Salesforce. 

There is one downside though. It is still a niche skill and resources are scarce in the market unless big IT companies are involved. On the other side, involving trusted partners helps get the required talent pool as well as accelerators.

I rate Pega Robotic Process Automation a ten out of ten.

I need to explore the solution more. However, I have enjoyed the usage of this solution.

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.

Pega Robotic Process Automation is easy. If you're a developer, it's a good tool to start with building bots. Overall, I can give it seven out of ten.

To use Pega RPA, you have to be mature. If you are interested in RPA, I would still rank UiPath first. Pega would be the second recommendation and the third would be Appian. 

Salesforce does not have a large RPA at this point. For pure RPA, there is no question that UiPath would be the suggested product.

Pega and Appian have to achieve a certain level of maturity. They are still a part of the product line and are still excellent products similar to OpenSpan, Jira, and also Appian. The integration is not as smooth as expected and it might take a year to get seamless integration.

If I were to rate Pega as a suite, I would rate it a nine out of ten. It has CRM, process implementations, customer experience, and has RPA.

I would rate Pega Robotic Process Automation a seven out of ten.

The solution is relatively stable and we find it a good product. The only drawback which we found is a lack of OCR capabilities, which we'll need other software to cover for us.

I'd rate the solution eight out of ten.

People who are considering Pega should be aware of a few things. Pega has got plenty of online training. Make sure that you take advantage of all the online training. You might even want to hire someone from Pega just to get you started. This will keep you from running into issues where you are going to struggle when using the tool. If you have a good start, then basically it is easy flying after that. Once you build something, you learn so much from building that first robot that you will have way fewer troubles building more. It might even be a good idea to hire someone on for 90 days just to get that first robot built. You learn and then you have a roadmap on how to move forward.  

Additional features that I would like to see in Pega in the next release all have to do with ease of use. Pega itself is really easy to use when you get away from Visual Studio. What I am mostly looking for is a better UI for better building.  

On a scale from one to ten (where one is the worst and ten is the best), I would rate Pega Robotic Process Automation as an eight-out-of-ten. The good thing about Pega is that it is very flexible. You can do a lot so the capabilities are broad. It can be tough at first to understand and start building. That is the only thing I would say is a downside. Put that aside and it has got tons of capability.