Pega Robotic Process Automation Reviews

Mainly, we concentrate on RPA bots. However, we have a few demands where we needed RDA, their assisted bots. We need some assistance with the bot where some inputs are required from the business. 70% of the time, we concentrate on RPA bots. For the other 30%, there is also a requirement for RDA bots. 

Mainly, we interact with Windows web and sometimes with mainframes. Currently, we are targeting APIs as well. We are working on a few of the API-related stuff and Excel-related work, Outlook, sending email, and tracking email. 

In terms of third-party applications, we have multiple websites, which are web-based. Based on the client's requirement, we use it to interact with the applications.

As an RPA guy, every tool has its own advantage. That said, Pega has the best feature in terms of creating UIs. We can create the best UIs. Other tools, don't have a better UI for RDA. 

Some go for RDA bots in the banking sector, and they prefer Pega Robotics. 

We have centralized the monitoring. In Pega Robot Manager, we currently have multiple dashboards where we can track, schedule, and handle everything. That is the game changer in the last one-and-a-half years. It amended what the business expected. 

The initial setup is pretty easy and quite fast.

It's stable.

You can scale the solution if you need to. 

The feature I like best in Pega Robotic Process Automation is that I'm able to add external DLL section codes. I can inject the JavaScript, and I can write VB.NET, C#.NET, and DLL codes, then inject those codes into the existing process. Mainly, from a development perspective, I like that feature a lot, so if anything is not supported by Pega Robotic Process Automation, then I can build that either in JavaScript or in .NET, then use those functions within the IP.

What I don't like that much in Pega Robotic Process Automation is its monitoring tool because that tool is tightly connected with the platform. If the Pega team can deploy the monitoring tool separately, so that it's a separate solution altogether, then that would be good because currently, if you have to use the monitoring tool, then that means you have to use the Pega Robotic Process Automation platform.

The initial setup for Pega Robotic Process Automation also needs improvement because it is complex.

The only additional feature I'd like to see in the solution is for the monitoring tool to be a stand-alone rather than being tightly coupled with the Pega platform. Looking at the current features of Pega Robotic Process Automation concerning application automation, it covers most of my needs currently.

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.

My use cases are slightly difficult and challenging. It was largely used for automation purposes. 

Anything goes with Pega. If you want to make any kind of base automation, you can easily code exactly what you want. 

Here at the bank, there's a fraud investigation unit team. If they discover fraud on an account, they have to put restrictions on the banking account and/or credit cards, depending on what type of fraud it is. They also alert the end-user (or our associates) that there's a fraud on the account. After that, transfer calls are made to FIU. From our end, alerts would be sent out to different systems including the banking deposit and the credit card system as well as our main CRM. Restrictions and alerts would be set up on the accounts to make sure everyone knows there was fraud detected. 

The most valuable aspect for myself was access to the .net framework. If I couldn't figure something out using the objects that they had provided, I could bring in the .net objects and do so using similar logic that I would in a .net or C sharp coding language. Having that familiarity was helpful.

The tool is for OGC processes. 

We have asked our team to identify manual areas and automate them. 

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. 

We are using Pega for automation for a client that has huge hangars where all the planes and helicopters are stationed once they are back from the journey. There is a particular person called an aero inspector who goes to each and every helicopter or plane and collects and inspects all the elements of it whether it's a small plane or a large plane, such as the engine, windshield, air conditioning, etc. It's a 300-checkpoint document that he has to fill up. We have developed a mobile application for this particular individual or for his entire team, so instead of writing it down with a pen and paper, they can now just go and do it with a few clicks. The entire thing is transmitted to Pega, and then Pega feeds it into their SED system so that everything is recorded, everything is seen, and the management has the dashboards for what's happening on the ground for various businesses. This is only for their operations in Switzerland, Germany, and Sweden.

We are working with Pega's latest version.

Pega is very mature. It's very old. They have grown with time, and they have learned. Other robotic process automation solutions are basically focused on only doing the automation, whereas Pega also gives you a workflow system so that you can create a workflow.

A good thing about Pega is that the resource availability is pretty good. If you go out in the market looking for a Pega resource versus an ABBYY resource, it's most likely that you will get a Pega resource much earlier than an ABBYY resource.