Learn what your peers think about Pega Robotic Process Automation. Get advice and tips from experienced pros sharing their opinions. Updated: April 2024.
Senior Business Automation Support Developer at TIAABANK
Jun 28, 2020
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.
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.
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.
Pega Robotics offers all the required features to build end-to-end process automation like any other similar tools. It's unique development style using data line and control flow line makes it easy to debug through the flow.
Learn what your peers think about Pega Robotic Process Automation. Get advice and tips from experienced pros sharing their opinions. Updated: April 2024.
Senior Business Automation Support Developer at TIAABANK
Jun 28, 2020
Pega has a no-code low-code environment. We do everything based on established rules. You kind-of have to learn how all their rules work and how it works for robotics before you can use the solution effectively.
The new players such as UiPath and ABBYY are moving very quickly, but Pega is not. I'd definitely like to see Pega doing a few more interesting things on the AI or machine learning front so that we can use the platform for multiple things.
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.
I have faced many scenarios in the business workflow, where a few applications run on the Citrix environment. That could be a critical part of the process without which business won't be able to accept the automation solution. Because of one small bottleneck, you will lose a very good candidate for process automation.
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.
