Robotic Process Automation (RPA) Features

Read what people say are the most valuable features of the solutions they use.
Saif Ul Islam Khan uses UiPath
Sr Managing Consultant at a tech services company with 1,001-5,000 employees
* The ease of the processes * There is no coding at all required to implement a complex business process. If you have some programming background, it will help you. However, if you are a business user, you can still develop simple processes. * The automated recording helps quite a bit. You record a complete business process along with human interactions to the desktop or web application. You can easily manipulate them. Once you are done, you have a complete recording of the interactions, which you can use to tweak your requirements. View full review »
Rao Parathnandh uses Blue Prism
RPA Program Manager at a tech services company with 51-200 employees
The automation in version 6 seems to be a lot better than it was in previous versions. In my opinion, that is great. The matrix in terms of reporting is becoming more friendly. It can be used with other analytics tools and that too is a great thing. You can pull stuff into stats, you can pull stuff into any kind of data analytics tool, like Tableau for example. You can easily see where all your problems lie, in a visual way. It's always nice to have a visual representation of things, whether you're a kid in school or whether you're a professor at a university. Seeing things at one glance makes a lot of difference, instead of having to read through the fine print and see where the issues are. Another feature I like about Blue Prism is the Control Room and how easy it is to find exceptions, to find common issues, and to troubleshoot your exceptions. Your Control Room person, without any development skills, can easily pick up what the problem is, with the exceptions, especially when there are a lot of exceptions related to one use case or process. View full review »
Emrah Karaca uses Blue Prism
Financial Control and Governance Specialist at a comms service provider with 10,001+ employees
It allows me to fix a lot of systems. For example, Pega is useful customer service and some other application is useful for HR. You can use Blue Prism for every process. Because it uses codes, you can fix every process. I like it a lot. View full review »
Gavin Price uses Blue Prism
Lead RPA Engineer at a recruiting/HR firm with 1-10 employees
Access to the SQL database allows for extra capabilities. View full review »
Luis Benitez uses IBM Robotic Process Automation
VP, Digital Workplace Strategy at a financial services firm with 1,001-5,000 employees
I think simplicity is key. One of the things that we've noticed is how our developers have been able to quickly adopt the platform; but not only the developers or the techy people, also the business. One of the things I want to do is empower different business units to be able to do their own automations, so that I, from IT, don't become a bottleneck, but rather I empower others and I enable others to be successful. View full review »
Luis Enrique uses IBM Robotic Process Automation
Director at a consultancy with 10,001+ employees
Deployment is done in a small amount of time. View full review »
HeadOfDae17b uses IBM Robotic Process Automation
Head of Data Science at a pharma/biotech company with 10,001+ employees
The most valuable feature is the ability to automate mundane tasks. This improves efficiency, reliability, etc. You can form critical operations which can be highly automated. At this stage though, we are not using AI. I think that is the next step. Today, we are mostly focused on taking the human element out of processes. The next step for us before we can deploy to scale will be solving for exception handling. We think AI can help with this. View full review »
SrArch893 uses Pega Robotic Process Automation
Sr Architect at a tech services company with 10,001+ employees
The case management and UI capabilities were the most valuable, though the integration capabilities were also quite useful. We also liked the DCO methodology as it reduced the build effort because some of the development (flow) was created during req and design phases. View full review »

Sign Up with Email