NICE Robotic Automation vs OpenText Robotic Process Automation comparison

"NICE is one of the only vendors that does attended and unattended out-of-the-box. Using the unattended processes we've been able to build a "feature library." We break each process down into workable chunks that we can save into a big library. The next time we come to automate a task, we already have chunks of that automation built."

"Provides good automation features."

"The deployment of NICE Robotic Automation is easy."

"It is easy to deploy. To do the automation in NICE, you really need to use your programming expertise. There are no inbuilt features in it, and you have to create all the required features, which can be very interesting for a programmer."

"It is a kind of desktop automation. Its licensing model is a little bit different. It tends to be individual automation specific to a role. It excels at that."

"Through interfaces called Callout (created with HTML code) it is possible to create a strong interactivity with the user. These interfaces can be extremely dynamic in relation to the behavior of a local or remote robotic flow."

"What we've done with the RTI client is that we've brought it into a bit more of a 21st-century feel. Our agents have the ability to move around when they want, click into stuff. They use it according to how their conversations go with the customer."

"It lets us automate almost anything, even with the legacy tools. It is very easy for us now to automate with legacy tools, which used to be difficult earlier. We work with a lot of other automation tools from Micro Focus, such as Operation Orchestration, but these tools can only connect to the API. So, there was a gap when we wanted to automate older and legacy tools that didn't have any API to connect to. We can now also automate without any changes in the customer environment. We don't need to change anything in the way that the customer environment works."

"Its connectivity with other applications should be improved. In the version that I was using, it would just stop interacting with the other application. Its graphical interface should also be improved. It should have a user-friendly interface. Sometimes, people find it very difficult to understand. One of the obstacles that I faced while programming was that if I needed any kind of help, there wasn't much content on the internet. It can be very difficult to find a solution for a particular issue."

"The solution is not as intuitive as it could be and integrating took a lot of time."

"[During the upgrade] any issues, where it couldn't remotely connect to upgrade, I needed the floor plan so I could go to that PC and have a look at it. Often it was either that the PC was switched off or had a bug or some other application needed to be reset."

"There are a few areas for improvement in the installation phase"

"There is a need for NICE robotics to be more user-friendly."

"We haven't found it to be as powerful as some of the other platforms. From a true RPA perspective, it is pretty far behind some of the other solutions. It has emerged as a more desktop automation kind of tool, but it lacks a lot of enterprise features. It is not really a true RPA because of its licensing, which is kind of user-initiated. It would be nice it can be deployed at a more enterprise licensing model versus a user-based model. It didn't have autonomous automation so far, and they have just released this feature. They have kind of hodgepodged a bunch of products together to get there, but it is not as seamless as other solutions."

"The one thing I'd like to see, and NICE is already heavily investing in it, is improvement in the user interface itself. They call it the Designer and it's what the developers use. It is a bit clunky; that is the polite way to put it. I'd like to see it be a bit more user-friendly, a bit more intuitive, and to move to something a bit more web-based..."

"It currently supports only on-premises deployments. They can include support for cloud deployments. It should provide us the ability to choose a robot for executing a workflow. We want to control which robot executes a certain workflow. Right now, it automatically chooses the robot that is going to execute our workflow. It should also provide the ability to get filters on the outputs of the steps. We have each workflow as a step, and each step has some output. We would like to have the functionality to execute some script or some logic on these outputs to format the tests directly on the variables."

"As per my understanding, UiPath has a much lesser cost than NICE, but I am not sure."

"The pricing model is very straightforward. You can have a one-year or three-year subscription. You pay for each robot that you want to use simultaneously. If you want, you can install 50 robots and get 50 licenses. If you want to use only one robot at a time, you just need one license. For each license, you pay around 10% or 15% to support. You pay for the license, and you pay a small percentage of the cost of the license for support. This is their licensing model, which is very easy to understand."