UiPath Orchestrator Reviews

I have three years of experience in UiPath and UiPath Orchestrator. I was using it for some of the automations we had done, and for the last six months, I have been on a different project that is mostly Selenium automation. However, I look for updates in UiPath whenever I get time.

Implementation timeframes vary depending on the application. If you have already done similar work, it will take hours, but when you do it for the first time, it will take around one to two days. The web application automations have been the primary focus, and we have also worked with SAP. There are no issues with the SAP integrations because UiPath has many SAP automations already available in their packages, making it easy for us to deploy and implement everything without major issues.

Myself and one colleague work on these projects. He has five years of experience, and I have four years of experience. We usually work together, with him handling most of the project setups and coding while I assist with some of the modules. I take care of UiPath Orchestrator and handle all the Orchestrator setup and administrative works.

Scheduling and running jobs is valuable because it simplifies automation. You just need to connect the bot and you can run it easily. For example, with Selenium automation, I tried Automation Anywhere, but I did not see many packages available in Automation Anywhere. Compared to UiPath, there are many packages available to make automation easier, which is why I find UiPath to be the best.

Another valuable feature is the ability to give access to people in UiPath Orchestrator at the organization level. They can log in and see the information themselves, which provides transparency to the people and helps with visibility.

At the account level, I think UiPath Orchestrator could provide some additional options. The account setup and organization page setup are a little difficult. When we do the organization setups, I find it challenging, though I think if you have experience, it becomes easier. For new people, it was a little difficult for them to understand. UiPath Orchestrator setup is easy, but the settings could be made easier for other people to understand.

I have nearly four years of experience with automation.

There is no complexity with on-premises installations. We usually install UiPath on-premises, and then we proceed with web application automations, which has been easy. There have been no issues with setting up UiPath automation on-premises. When there are firewall restrictions or other restrictions, we need to modify those things, but I do not see issues in setting up UiPath automation in on-premises environments.

Implementation timeframes vary depending on whether you have done similar work before. Sometimes if you have already done it, it will take hours, but when you do it for the first time, it will take around one to two days.

I can give customer service an eight out of ten, though sometimes I find difficulties and have trouble finding support. Most of the time, I am getting good responses from the support team.

Positive

Myself and one colleague were involved in the initial setup. He has five years of experience, and I have four years of experience. We both usually handle the setup together, with him doing most of the project setups and coding while I help with some of the modules. I take care of UiPath Orchestrator and handle all the Orchestrator setup and administrative works.

I have nearly four years of experience with automation.

I tried Automation Anywhere, but I did not see many packages available in Automation Anywhere. Compared to UiPath, there are many packages available to make automation easier, which is why I find UiPath to be the best.

As for pricing, compared to one year ago, it has increased a little, but I think it is affordable compared to other solutions like Blue Prism or Automation Anywhere. UiPath has better pricing compared to them.

We have not yet done any projects related to machine learning, but we are planning to do a proof of concept in UiPath with machine learning in the future. We are planning to do some proofs of concept for customers.

We have not done any rule-based things in UiPath Orchestrator yet. In the future, we may implement rule-based features for AML and related functionalities. Currently, only two people in my company work with UiPath automation. We already have the roles set up for people or clients to see information and view it. I have yet to do more experimenting with the role-based features.

I would definitely give UiPath a ten out of ten as it is my best tool to perform automation without issues. I can find all the information available in UiPath Orchestrator, making it easy for me. It is really helpful for doing business effectively. My overall review rating for this product is eight out of ten.

There are multiple typical use cases for UiPath Orchestrator, such as data extraction from sites and posting it to another place, which is one application. There are also several workflows in the banking segment that process file movement; these basic workflows are required.

From my perspective, the main feature of UiPath Orchestrator is their good library of ready-made processes, which is very time-saving.

The benefits UiPath Orchestrator brings to the company are twofold: first is the accuracy it maintains, and second is time saving, especially for tasks that have to be performed on specific timelines, where robotic process automation comes in handy and saves a lot of time.

In future updates of UiPath Orchestrator, I would want to see something that allows typing basic details of the workflow, which can then be used to design a text message workflow. As of now, almost all the features are available, and nothing seems missing.

I have been using UiPath Orchestrator for around five years.

There were not exactly any challenges in deploying UiPath Orchestrator because we get technical assistance from the OEM. My team takes care of the development part, and in case any assistance is required, we get back to the OEM and they assist with whatever technical assistance is needed.

My opinion about the overall stability of UiPath Orchestrator is that it is a stable product. I just couldn't get more specific. It is a stable product without any issues regarding stability.

The product is scalable.

Regarding the technical support of UiPath Orchestrator, I would rate it around eight. It's on the better side, but still has room for improvement in the speed of response.

Positive

The deployment of UiPath Orchestrator requires basically a few hours depending on the customer requirements. Sometimes, if there is a complex workflow that needs to be designed, then it takes a few days. Otherwise, most of the built cases are already there, so we pick the template and then process it.

In my deployment team, there are two people. They are certified engineers.

The impact of UiPath Orchestrator's analytics on the decision-making process is important because it shortens the decision-making time, which helps customers.

UiPath Orchestrator's ability to automate rule-based processes has a significant impact on human resources. For example, when a customer requests a password reset, it recognizes that this email requires action and works accordingly.

Regarding licensing costs and setup costs, the pricing is on the higher side compared to other RPA solutions that are entering the market, which are much cheaper, and sometimes we cannot retain customers because of this. Cost definitely can be reworked, and better pricing could attract more customers.

I am considering the possibility of choosing some alternative for UiPath Orchestrator in the future. If the pricing does not come down and another vendor offers similar functionality at a lower price, we will have to consider switching.

I don't find any downsides or weak points in UiPath Orchestrator. They are okay.

I have not integrated machine learning with UiPath Orchestrator.

The login and auditing features of UiPath Orchestrator have improved operational transparency because with single sign-on, login is much faster, and it automatically processes tasks such as resetting the password.

The solution is cloud-based.

On a scale of 1-10, I rate UiPath Orchestrator a 9.

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.

Orchestrator's most valuable features include schedulers, queues, and integration with Splunk. Logs can be directly pushed to dashboarding tools like Splunk or Tableau. The centralized nature of UiPath Orchestrator provides a seamless experience for managing automation processes.

There are overwhelming features added to UiPath Orchestrator, which can lead to complexities. Permissions, roles, and queues sometimes result in conflicts, requiring deeper understanding. 

I would prefer if the tool was more intuitive, and it is important to maintain simplicity instead of combining multiple functionalities, potentially through different licensing models to restrict features.

I have been working with UiPath Orchestrator for several years.

The solution is stable and integrated well with other systems, significantly aiding in deployment and management.

The solution's flexibility in integration and scheduling across different environments suggests good scalability.

UiPath provides excellent customer support. They lead in running their communities well, which helps professionals use UiPath effectively. Technical support is responsive and works directly with customers for in-depth assistance.

Positive

Initially, I worked with UiPath, then moved to Blue Prism and Automation Anywhere. Recently, I've also started working with Microsoft Power Platform. However, none of these solutions compare to the capabilities of UiPath Orchestrator.

The integration is seamless, with the capabilities to connect with Studio and manage versioning effectively.

Our engagements mostly involve the customer managing licenses, while we engage as an implementation partner.

It would be beneficial for UiPath to further refine pricing, setup costs, and licensing by making their tool more intuitive and simplifying complex functionalities.

I have evaluated solutions like Blue Prism, Automation Anywhere, and Microsoft Power Platform. However, UiPath Orchestrator's capabilities stand out in comparison.

Enhancing the user experience by making the tool more intuitive, particularly for modern features, and providing simple solutions would be helpful. Creating different license types to better manage features would also be helpful.

I'd rate the solution nine out of ten.

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 would like to see high availability over two sites, with a main site and a disaster recovery working as an active-active solution, which is not currently supported.

I have been using UiPath Orchestrator for five years.

We do not have issues with stability as of now.

UiPath Orchestrator is scalable, and we integrate it with various solutions.

UiPath basic support has some limitations, however, the premium support levels provide more convenient coverage & response times.

Negative

The pricing of UiPath Orchestrator is a bit high. However, we can compete with that, though if they decrease the prices, it would lead to better market penetration.

I rate UiPath Orchestrator an eight overall, considering the support. Without considering the support, it is almost a ten.

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.

The focus on repeat application automation is valuable.

The major issue is with the application according to the new version of the UI. We have developed our engineering and written it ourselves, so it becomes a problem.

I have used UiPath Orchestrator for about one year.

UiPath Orchestrator is stable as long as the problems with resolution or operation interface are solved. When set up correctly, it works normally.

I would rate the scalability around seven out of ten.

The technical support is about eight out of ten.

Positive

I cannot recommend UiPath Orchestrator to others since we only have one option in our company, and I haven't used other solutions.

The installation took maybe one day.

We have a team from our information department.

I'm not sure about the financial benefit for our company.

The price is about six on a scale from one to ten and needs improvement.

We only use UiPath and no other solution.

I would rate UiPath Orchestrator eight out of ten overall.

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.

UiPath Orchestrator needs to focus on dashboards. Previously, we had Kibana integration with Orchestrator, where we could develop dashboards. Now, there are Insights in Orchestrator, but they must be improved to a good standard. We should be able to create good dashboards with pie charts and other visualizations. It will make things clearer for management.

We can use Orchestrator as a central system for customers or vendors. But we need to depend on many other things, like repositories. For example, we need to use GitHub, DFS, or EFS. We need to do a lot of configuration and settings for them. If that was more accessible, the configuration would happen very easily. In Power Automate, there are many connectors. We need to drag that connector and use it. It is easier; there is less coding and configuration. 

In UiPath, we need more connectors or features. If we have direct connectors for third-party applications like SAP and Salesforce, we can quickly connect to those applications and automate. It will reduce development time for developers and lessen the burden on Orchestrator admins.

I started my journey with UiPath with the first version in 2016. Since then, I am currently working with the 2023.9 version of UiPath Orchestrator.

I've been working with UiPath for the last six to seven years. I've done many projects with UiPath, and I also handle the architect role, where I work with the admin roles in Orchestrator.

I would rate the stability a nine out of ten. 

I would rate the scalability a seven out of ten because the solution needs to have more connectors.

Orchestrator and UiPath are not dependent on any particular organization. We can utilize Orchestrator in any organization. If we work with a large enterprise, Orchestrator will be feasible. Even for a small business, we can use it.

UiPath Orchestrator needs to improve their SLA timings when we raise a ticket. They need to resolve issues quickly. If we have an issue and the bots are in production, it will hamper the business. We need to make sure that issues are resolved within a 24-hour or 48-hour SLA. UiPath support needs to connect quickly, provide solutions quickly, and resolve the issue on a priority basis.

Neutral

I work with Power Automate as well as UiPath.

I use Power BI for dashboards. Other than that, I have previous experience with Microsoft technologies like ASP.NET, VB.NET, and other Microsoft programming languages.

The main competitor for UiPath is Power Automate. Power Automate has many features. But UiPath has standard products with specific features, and the stability is good. If we look at other tools like Power Automate, they are still building their features. They have some sufficient features, but they are still trying to improve and need time to do that.

The products and features that UiPath launches are well-tested and utilized by the UiPath community. They suggest standardization and provide feedback for the products, and UiPath responds quickly.

Nowadays, UiPath Orchestrator is going with the cloud. It is easier to use the cloud. But if we go with on-premises, we need to install many things and do a lot of configurations for database connectivity, ports, and everything.

I work with both on-premises and cloud-based deployment models.

UiPath needs to rethink its pricing. In the market, if I compare with Power Automate, their price is less than UiPath. Even the developer license for Power Automate is only $15 per month, whereas UiPath costs more. 

The difference is nearly 50%. The cost is very high, including for other features. Based on my experience with multiple clients, they are moving from UiPath to Power Automate due to the cost.

Orchestrator is a good product. Overall, I would rate it a nine out of ten. 

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.

The licensing cost associated with the tool is too high. If the tool can reduce the license cost, most of the organizations will opt for it.

I would like GenAI to be introduced into the tool in the future. Though Generative Extractor is present in the tool, it is still in the preview phase. In our company, we depend on other tools. It is better if we have AI within UiPath, so that on an end-to-end basis, it will be all within one umbrella only.

The tool's support team has certain shortcomings, making it an area where improvements are required.

I have been using UiPath Orchestrator for eight years. My company has a partnership with UiPath.

It is a stable solution. Stability-wise, I rate the solution an eight out of ten.

Scalability-wise, I rate the solution a seven out of ten.

Whenever our production was down, sometimes it was very challenging for our company to reach out to the solution's technical support team. The communication goes here and there when we try to get in touch with the support team. When our production was down, and all of our stakeholders and leadership were behind, it was a very challenging situation for us. I rate the technical support a six out of ten.

Neutral

Back in 2017, the product's initial setup phase was easy. In our company, we have had Uipath Orchestrator upgrades, which we have been managing.

If ten points mean a very easy setup phase, I rate the product's initial setup phase as a seven.

In terms of UiPath Orchestrator's contribution to cost savings, I would say that 20,00,000 of our company's savings and some of our FD savings are due to transaction processing, which we can do with the tool's help. The savings are not for the current year but for the last four to five years, and it all depends on the total number of bots that we have processed and the savings we have gotten out of them. I have seen a return on investment from the use of the tool.

The tool's licensing cost is high. I rate the tool an eight or nine on a scale from one to ten, where ten means expensive.

We used to face issues with workflow efficiency earlier, but now efficiency has improved greatly. The tool is a good fit for any of the RPA processes.

The tool can be used in HR, finance, and global governance.

From the technical side, I have not found any issues with the tool.

The biggest impact of the product on our company's customers revolves around efficiency, meaning that large volumes can be processed very quickly, which leads to time savings. Our company's customers can also have a look at processing, while the data remains secure.

Before purchasing the product, I suggest others think from a scalability perspective and deploy the tool on both models, like the on-premises and the cloud one, so that things remain easy. One should not just opt for only one platform.

I rate the tool an eight out of ten.

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.

In my opinion, some improvements could be made in the UiPath Orchestrator. For example, it's not so simple to see all the time triggers that we have. We need to check each folder and see all the triggers to see what kind of robot will run. We do not have all the triggers in one place, showing the time they will run and for which process in each folder. Another thing is that the tool for monitoring processes does not show the relation between the process and the machines running them. We can check which machine is available or not because it is running a process, but we cannot see the process and the machine running it in one view.

I have been working with the product for five years. 

I didn't have any issues with the solution's stability.                             

The solution is very good for scalability. It's very easy to add another robot. For example, if we have a process with lots of items, it's very easy to configure another robot to run the same process and consume all the items in the queue. It already has mechanisms to control which item each robot will run. My company has 20-30 developers. 

The tool's deployment is not complex. We need to just upload the package. Deployment needs just a click of a button. It's very simple. After all the configuration is done, so when you have your machine connected to your Orchestrator and your licenses are set up, it’s very easy to deploy. After all this configuration, you just need to click a button and you are good to go.

The solution is very expensive. Compared to Microsoft, another tool that is much cheaper than the tool, it does not have the same features that UiPath Orchestrator has. The most valuable feature in my platform is the queue items in UiPath Orchestrator to evaluate the products using this feature.

WWith all the new tools in UiPath Orchestrator, we basically need to pay extra for them. For example, if we want to see a dashboard for all the automation or get more useful information from the logs or from the management, we need to pay extra for the UiPath Insight. So, the tool is expensive, and all the additional costs are also very high.

We do not integrate UiPath Orchestrator with our systems. When we need to, we just use the API. It’s not hard, but we haven’t explored the integration feature deeply. We handle everything we need through the API, for example, integrating with our system to create a request and generating a new ticket in our queue. All communications go through the API, and there is a Swagger interface, so it’s not hard to use.

When discussing the Orchestrator Cloud, it is not the user's responsibility. Whenever we need anything adjusted in the UiPath Orchestrator regarding the infrastructure, we need to contact UiPath, so that's very easy. For example, if we need to change any configuration in UiPath Orchestrator, it's simple. You can configure the changes in the Orchestrator Cloud when you have admin rights. So that's good. However, regarding the infrastructure, all the maintenance is not the user's responsibility. UiPath provides all the support.

I rate the overall product an eight out of ten. 

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.

Using UiPath Orchestrator, we can deploy tasks across different environments, including virtual machines, for both attended and unattended processes. Monitoring features, activity logs, and scheduling capabilities are particularly useful. The most beneficial features of Orchestrator for our automation process are its trigger and job monitoring, logging functionality, and scheduling capabilities.

I haven't faced many challenges with UiPath Orchestrator. Previously, it was on-premises, but having clear documentation on how to transition between on-premises and cloud-based setups would be beneficial. Clarity on integrating SQL databases and server configurations would also improve implementation processes.  

In terms of technical feedback, I believe UiPath Orchestrator has progressed well over the last few years, with many activities and expansions. However, there's still room for improvement, especially in the user interface.

I've been familiar with Uipath Orchestrator for about 4 to 5 years now. 

I would rate the stability 9 out of 10.

I am impressed by the scalability and I would rate 10 out of 10.

UiPath provides good technical support.

Positive

Before Orchestrator, I worked with different automation tools, but Orchestrator has advantages over them due to its broader capabilities.

The pricing seems reasonable based on project requirements.

My advice for those considering Orchestrator is to ensure clarity on usage, especially for attended bots. Overall, I'd rate Orchestrator 9 out of 10. In the future, I'd like to see features like direct PDF editing and improvements in email automation.

We are using UiPath Orchestrator to create an Excel file, filter the data, and send email alerts to colleagues. It is a simple email alert system.

UiPath Orchestrator has helped us by replacing manual processes with automation. Previously, we needed a person to work on a repetitive task every week. Now, with UiPath Orchestrator, we only need to check the log, freeing up time for our team.

We use UiPath Orchestrator to connect with different applications, extract and analyze data by specific criteria, and send emails. This feature supports integration between our existing applications and internal systems.

I am interested in seeing more features like document understanding and AI integration. These features seem interesting. I haven't had a chance to try them yet.

I have been using UiPath Orchestrator for some time and supporting our team to use it with one or two robots.

I only use UiPath Orchestrator - not any other tools.

I'd rate the solution eight out of ten.