UiPath Orchestrator Reviews

I primarily use UiPath Orchestrator for deploying my robots along with their machines. We deploy our processes, which generate logs and help us understand what is happening with the robots. 

We generally use queues to help understand the overall health and average handling times, helping us monitor robot performance. Although I am an end-user of Orchestrator and do not work on configuration, we have certain implementations where we connect this with Splunk to generate insights from Orchestrator logs.

UiPath Orchestrator improves operational efficiency through its centralized dashboard and asset management. It offers APIs that facilitate connectivity with various systems, allowing the triggering of robots from other platforms, leading to impressive centralized control for our requirements.

We are partners with UiPath and we sell UiPath Orchestrator to other individuals and organizations. We recommend it to various companies, including banks, telecom operators, automotive providers, and other different segments.

UiPath Orchestrator is considered the brain of the system. It manages all robots and automations, as well as integrations. It is the core component of all UiPath solutions. It provides APIs to integrate with other systems, and we are already using it with some customers. It is very important for us.

I mainly use UiPath Orchestrator to run and manage robot tasks. Initially, I mainly focus on scheduling and monitoring during project implementation. After that phase, maintenance becomes less frequent, typically for the first three months.

We declare it for the regular application in our engineering and analytics report. We conduct engineering data analysis in our system, read out engineering data from the database, and create regular reports which we publish to others. This is how we use UiPath Orchestrator in our deployment.

UiPath Orchestrator has eliminated the need for human operation, enhancing our automation process.

I have worked with UiPath in many domains, like finance, banking, insurance, telecom, healthcare, and the oil and gas industry.

We can use it for different processes. Depending on the process, we can manage the bots. It may be attended to or unattended; it depends on the customer's requirements. We just need to go with that particular bot.

I manage assets in Orchestrator. I work with triggers, such as event triggers, queue-based triggers, and schedulers, such as time-based triggers, to schedule the bot. 

I also create user and machine templates and do other work in Orchestrator. I manage licenses. We also use advanced features like Action Center, Document Understanding, and Test Suite, where we can use Test Manager.

I use Document Understanding to process invoices for many customers. We also use Action Center when we need to work with approval workloads. For example, some tickets are raised in ServiceNow. That ticket needs to go to a particular agent and needs to be resolved within the SLA. 

If the ticket needs to go for approval, we can assign those actions to the approver. Once they approve or reject it, that information will go to the agent, and the next steps will go to the bot. The bot will act according to the status.

I also work with the central management function. We also work with different folders in departments like Operations, Finance and Accounting, HR, and other departments. We can create different tenants for them, and in those tenants, we can deploy bots and give access and roles to the end-users if the bots are attended. Everything related to that department can be managed in its tenant.

For AI, we use Document Understanding, where we use AI/ML models. We need to create custom ML models depending on the document types and formats. We have already done that in UiPath Orchestrator.

My company's customers create unattended bots, especially when we need to upload some files in SharePoint. We use some applications for certain decoding and when we need to extract the data and upload files.

UiPath Orchestrator's most valuable in terms of RPA management revolves around queues in the tool. UiPath Document Understanding and HITL are also valuable features associated with UiPath Orchestrator. If any of the invoices get stuck, we can go to the HITL section and manually try to process them. Instead of failing the bot, I think the tool serves as a second verification for the invoices.

The scheduling and management of bots in UiPath Orchestrator is okay.

Compared to other orchestrators, UiPath Orchestrator is more user-friendly. UiPath Orchestrator is a product that can be used with a lower level of knowledge. Compared to the orchestrator in Blue Prism, which is usually already integrated with Blue Prism Control Room, everything in UiPath Orchestrator is better categorized. It's easier to find what you want on UiPath Orchestrator. With UiPath Orchestrator, you also have a lot of other functionalities, which is much more than what Blue Prism offers.

UiPath Orchestrator is sometimes a bit clunky, and a few things don't work in the tool as they should. For instance, when working with queues and things like that, you may want to do some operations on transaction items, but you won't be able to do so because of the product's UI limitations, which may be frustrating. I think the aforementioned areas are where I have complaints about UiPath Orchestrator.

The product's technical support team is not bad, but I feel there is room for improvement.

With UiPath Orchestrator, my complaint stems from the part of the tool consisting of the interaction with queues, which I think needs to be a little more flexible to be able to manipulate the transaction items as intended with not so many restrictions on cloning, making it easier to create new transaction items, because nowadays, you have to import or clone it.

We use the tool to manage, monitor, and schedule robots. 

The key feature for scheduling robots is using time triggers or queue triggers.

The centralized login feature greatly helps because we can also use the Active Directory feature. We do not need to create a new user. We can connect with a user from a company, and we can add all the groups they have to set the features for a specific group. We do not need to do that for each user, and we can do that for a specific role we have in the company. I think this helps a lot.

In my opinion, the biggest benefit is the queue feature. It helps a lot to escalate the products. We can divide all our items without building any structure to parallel the robots because the UiPath Orchestrator can manage that. For example, if a specific robot runs an item from the queue, we do not need to calculate that. We need to run another robot to consume the same queue. It will get another item that is not the same item that is already running. It helps a lot because it's very simple to use, and we can escalate the robots. I think it's the best thing we have in the infrastructure.