UiPath Platform Reviews

I am an API developer and I use UiPath for development. I use it to develop solutions for banking problems, like banking automation.

For example, in my previous company, I used the API for developing automated reporting solutions that take a lot of Excel files, check their data, and try to generate a web page containing many graphics based on the Excel data. It's basically translating the data on the web and it's made automatically every month. 

For my current company, it's a banking company, and I'm working on the banking solution. It's a process of verification of the user identity or the client's details. This process is based on taking the ID card of the person and digitalizing the data. It's a technology meant for reading data from documents. After reading this data, we automatically take this data and put it into the database and create accounts for the user or do a lot of automated things. 

At my current company, the use case is for the process of managing the relationship between the client account and any fees. A robot always checks if there is something to pay for the client and can take the fee automatically if that is the case. Then there is a transfer of money based on the request.

For example, when someone wants to do a transfer they add the money and sign a paper. This paper contains the information of the client's account, including details such as the client name, the account number, and the amount of the transfer. We take the data and the robot automatically takes the data and, via the web, goes to the apps of the bank in order to search for the client, search for the account, say the amount, and take the proper amount from his account, et cetera. We're able to save steps as everything is automated.

The actual company has three environments. There's one for development, one for pre-production, and one for production. Every element has two UiPath robots and one Studio. We have in total three studios and six robots, and each one has its own lessons. 

In the first, there was only one robot and one studio. They upgraded the solution from one studio one robot to three studios and six robots and they have found a good benefit in that. They know that it will give them more opportunities and more advantages within the banking environment. They made an investment in this technology to make their work easier so that they could be the best in the market of banking. It's helped them become more efficient.

There is an additional library that I discovered that allows me to work with the previous version of UiPath. There are some libraries that are new on the UiPath Studio, which are also helpful.

In terms of the ease of building automation using UiPath Studio, I must say that I used Automation Anywhere once as well. However, the way the UiPath connects the idea for development makes it so easy to build with the components that we can just drag and drop in. It's the easiest way to develop a solution and is an easier tool to use.

UiPath helps implement end-to-end automation starting with process analysis, then robot building, and finally monitoring of automation.

Being able to implement end-to-end automation is important for me. As much as they make me work, they make the work easier for me. For example, I use it to make the connection between ABBYY Studio, a solution for OCM, and writing scripts inside. I try to launch the script and take the output of the file and try to do a lot of things to make a connection between UiPath Studio and ABBYY Studio. UiPath Studio has given us a strong and new plugin, that we'll put some parameters around and we are done. It makes things easier like that. The features added into the latest update are helping a lot.

UiPath Studio has helped minimize our on-premise footprint in that there's less staff required. Previously, the company had three or four people doing the same thing. Now, only the robot does it. The four people are doing something else now. It's allowed them to focus on other tasks. The robot did not replace them, however. They still work in the same company, however, they are focused on doing different jobs - specifically jobs that can't be automated. They work on jobs that require a human operation, human intervention, and that's it.  The employees are happier too. The current company recently won an award based on employee happiness. In 2021, they were awarded excellence in employee condition. Automation hasn't made them bitter or changed their work ethic.

Robots started doing a lot of tasks that four people take one week to finish, except they can do it in one day. It's saved lots of time. For example, if we have 52 weeks, every week the robots can do a week's task in one day. A human may only be able to do 52 tasks in a year, whereas a robot can overperform by roughly 86% over the course of a year. 

UiPath speeds up and reduces the cost of digital transformation. The robots are extremely helpful, as they can work 24 hours a day, every day. They can do processes faster than people. It makes everything ultimately speed up.

The product has reduced human error. Even the robots make some errors, however, at least we are aware of them. The errors end up being fewer than that of a human counterpart. The issue with human errors is that we can't know if and when an error is made. At least with the robot, if it makes an error, the person is blocked somewhere and therefore we know that the robot missed something or it found a wrong account number, for example. The robot will notify us of an error whereas a human might miss it completely. 

Between version 19 and version 20, the Orchestrator tool interface has changed a lot. It totally changed. The menu changed, the place of the button changed. It took me a week to understand and to make myself used to this new interface. In the end, I found it's a good change and it's helping so much in understanding what the robots are doing in terms of checking logs, extracting some data there to make some analysis, and giving reports to the director.

The scaling could be better. There are so many parameters and options to check and so much to do before the solution is ready to use. Not everyone knows what to do at the outset and it's all a little bit complicated.

I've been using UiPath for one year and a month. The company may have been using it for longer than that.

While the stability is fine, with a license that needs to be paid yearly, UiPath will put out a new version annually. That way, when companies go to renew, they often need to upgrade or pay for a new license. The product does this to keep earning money year after year. 

For me, having the ability to scale automation without having to pay attention to infrastructure is okay, generally, however, even though I find that the company can use the tool to make the process automate well, I don't have so many people working with process automation. There are now just a few people developing in the APA and the licensing is still expensive and clients aren't excited to do anything even if it's a good solution for automating the process.

If you have a lot of money, you can put it all in UiPath and make the robot far bigger. I heard about a company located in Qatar that has 3600 robots. They buy it every year. It's a banking company and every year they pay for it. They are not using all of the robots, however, they've given their developers full reign of the environment.  

In my current company, I'm the only one using it. Many companies actually spend a few years testing it before they officially start using it. However, the company does plan to increase usage and does plan to add three or four more people to the team who would be working with me. I would manage them and provide training as we expand. 

There's a third party that takes responsibility for troubleshooting. They made the environment, and they are in charge of everything. Personally, I go first to the UiPath forum if I need help. I've found a lot of answers there. If I don't find something useful or helpful, I write an email to the third-party provider so that they can take charge of the problem and solve it.

They are good. There are three people who assist me typically. One is from the Middle East, one is French and the other is from India. Their way of communication, their way of giving information, and giving support have been great.

Both companies I have worked for that use this product have never used an automation solution before. 

I have worked with the solution for two enterprises. One was a Canadian company. I implemented the solution for them. I met the organization's boss, and I also put the training together too. I made the environment and I developed the solution and did the full implementation. 

The second, which I am actually working for, is a combination between Europe and Africa on the main. In both companies, the solution is already implemented and I work with it. The solution was started by another department. We don't share or manage the site of escalation or choose which kind of installation. The installation in this case is on-premise. We have constructed on our IAS, local server, and that's it. It's on the server, and we're not using UiPath's cloud.

The initial setup is good. There are no problems. Setting up the robots is also good. For the Orchestrator, sometimes I face some issues surrounding not UiPath, but the OS. For example, installing the Orchestrator on Windows 10, version 19.02, it's not the same process as it would be with Windows 10, version 20.82. Sometimes the visuals of the operating system change and it affects the installation too. This is well documented in the UiPath community. You'll find that many people face problems while working with the Orchestrator.

The deployment sometimes took me two hours. Sometimes I come across an issue and it takes more time. However, often, it can be deployed in 30 to 50 minutes if all goes well.  

With the installation for a Canadian company, I have a very simple installation experience. The environment was already prepped and ready and I just needed to start the installation. 

There is an IT team that does perform the maintenance as required, for example, if there are any updates or upgrades. I don't handle that aspect. I'm only a developer.

We might study potential ROI in the summer of 2022. We're still on the development part and therefore we still can't make reports. We don't have statistics.

There can be costs related to digital transformation. There are two ways this can happen. The first is when the robot is using an internal application, the application made by the company. There often is some modification to the interface of this app. There are some options that become available only for the robots. The second is when the robots use the websites of external companies. Internally, we made some changes to the robots to ensure they work well. In terms of the expense and how much it costs, the information is managed by another department. I don't have information about that.

I can't speak to the exact price, however, recently I heard in a meeting that one license for Studio Path costs 2,825 Euros per year. This price is approximate and may fluctuate.

The license is always per year. They don't show the pricing on the internet. You must contact the support or a seller. 

For the company I currently work with, I was in the meeting that chose the automation solution and they put the UiPath blueprint and Automation Anywhere on the table. The company wanted to choose between them. They found that, in terms of money, performance, and popularity, UiPath was the best. That is why they choose UiPath.

We are not resellers. We are customers and end-users.

For now, I am fine with UiPath Studio and I will likely keep developing automation solutions on this tool.

For the attended robots, we are not using them yet. We are only using unattended robots. First, we must make the financial employees understand how robots work. They need understanding or training as a first step before we can use attended robots in development. We are going to use attended robots in the future, however, for now, we're focused on unattended robots.

We don't yet use AI functionality. We're going to start using artificial intelligence and also the machine learning solution of UiPath via AI sensors. We'll use it to measure credit and to gauge the likelihood of clients paying, however, for now, we are not yet using AI features.  

We are also not using UiPath apps.

UiPath Studio has reduced the costs of our automation operations, although I don't have an exact statistic that reflects this.

Sometimes, when you come to a company and you tell them that you will make a robot to do their job, the first thing they will start thinking is "we're going to lose our job. They're going to fire us." With that mentality, they often aren't cooperative. 

For example, in a Canadian company I worked for when I was working on the process, the parts of the activity for Excel automation, I kept notifying them that they should keep using the same name of the file so the robots can read the file. However, I would get files in different names with letters off or symbols in them as if the staff was trying to get the project canceled by trying to show the robot wouldn't work. However, over time, as they came to understand no one would lose their position, they became cooperative. They weren't happy at first, however, they came to embrace the project.

UiPath has a huge marketing strategy, and they have been the first in the world with a lot of this technology. If a company wants to integrate automation into its processes, it will likely start looking at UiPath first.

If a company is considering UiPath, they should know exactly which process should be automated. When you know what kind of processes will be automated, they will understand better if they need attended robots or unattended robots, and then can proceed with a purchase. What one recent company did is they went and bought one studio and one robot. Then, later, after understanding which process was going to be automated, they figured out that they needed three studios and six robots. It's better to know which process to develop to make it automated, then later go to buy solutions for it.

We will still always need human workers. Of course, there are some tasks that can be automated 100%. However, in the end, and specifically in the banking domain, we always need humans to understand some things that make the work easier. if we combine automation, things like robots, and human intervention, then we can get great results.

I'd rate the solution at a nine out of ten.

I have worked on two UiPath use cases. The first use case is for the IT Infrastructure team for submitting server requests. They receive a request from a third-party portal through email, and then my bot reads the email and fills in the details in the company portal.

The second use case is the data extraction from Word documents. The team receives Word documents with some important contract information. I extract those paragraphs and put them in the CSV format given by the customer.

We are using UiPath Studio 2020.10.2, and the Orchestrator version is 2019.

I heard about UiPath RPA in December 2019, and I went to the UiPath Academy website and completed their learning plans. Till March 2020, there was free certification, and I completed the free certification and kept on practicing. I showcased my skills to the management in my company, and I got into RPA projects. The certification has helped me in getting good projects. It has also helped me with my work for the use cases. My position is now better as compared to the previous years, and my work is also good. 

They provide end-to-end solutions. They have UiPath Studio for the development, and they have Orchestrator for package deployment. We can also monitor the performance and execution in Orchestrator. All these are helping us in managing end-to-end automation.

All UI automation activities in UiPath Studio and REFramework are useful. UiPath Orchestrator is also valuable. These features help me a lot in my projects. 

UiPath Studio's UI automation activities help me in easily developing automation. It is difficult for RPA developers to write complex code because no one knows everything about all automation areas. For UI automation, it is not mandatory for a developer to know how to write the code for the element on the screen that needs to be clicked or typed into. The UI automation packages of UiPath provide built-in activities, and developers can directly drag and drop and indicate the element on the screen that needs to be clicked or typed into. 

REFramework is a template using which we can prepare quality workflows for the transactional processes. It has very good error handling, retry, and logging mechanisms.

We can monitor robots in Orchestrator. We can check logs, monitor the performance of each robot, and divide robots into different environments. These features are very helpful for me in managing my work. If I have two or three robots on a set of machines and I want to define my process only for these robots, I can add that process into the environment. My process will be executed only on those robots. This is a good functionality.

For every transaction, there is the queue functionality in Orchestrator. I can go to a queue and add each transaction item to the queue. For every transaction, I can check the logs. I can also check their logs based on the jobs executed. We also have triggers, so we can schedule our jobs with the help of triggers. These features are helping me a lot in managing the performance of my robot and understanding how my robot is performing.

They have UiPath Forum where I can ask any questions. Many UiPath Most Valuable Professionals are on that forum, and they help us a lot. We get quick replies. If anyone is having any challenges, they post their challenges on the UiPath Forum. I can go through them, and if they are already solved, I gain knowledge by reading those solutions. If not, I try to answer them. In addition to gaining the knowledge, I'm getting some visibility in the UiPath Forum. All these things have really helped me a lot in increasing my technical level and expertise and getting good work.

UiPath Studio supports three types of workflows: sequence, flowchart, and state machine. Flowchart and state machine are good. Sequences are also good, and they're for linear workflows. However, in a sequence, as we keep on dragging and dropping the reusable components, the size of the screen increases. If we drag and drop the conditional or looping activities on the site, the screen size increases in length and breadth, and it becomes too complex for a developer to navigate between activities. 

All programming languages, such as C, Java, Python, or Visual Basic, have script-level support. So, we can reuse their functions because they support scripting. For example, if we want to use any reusable components, Python has modules, and there is a way to import packages. For complex automations, if we can write a script, it makes it easy to manage and know the line on which we are getting a syntax error or a runtime error and how is the structure. If I want to modify the logic, it makes it easier to know in which block I need to make the changes. So, it is easy to navigate in the program. Instead of the drag-and-drop blocks, UiPath should have support for scripts such as VBScript and PowerShell. It should support scripting even for complex automation.

The user interface for logging should be improved in Orchestrator. Currently, the logs in Orchestrator show how many hours ago the execution is completed, but it doesn't say how much time it took for a particular execution to complete. It just gives you a rough idea that it started three hours or one hour ago. It doesn't tell you exactly when a particular execution started, and at what time, it stopped. To get a clear idea, I need to click one more button and go to the details of the log. I need to check the start time of the first log and the end time of the last log in the same job, and then I need to calculate the difference to know the exact time it took for completing the job. Instead of doing all that, there should be a column that gives me the exact amount of time in minutes and seconds. It will help me in understanding how much time each execution took and what I should do to improve the speed of the execution.

In my current project, there are no intelligent automation requirements, but I have learned it recently. Just today, I completed the UiPath AI Center course. I also have some basic knowledge of machine learning. They're giving us options to use the out-of-the-box models developed by UiPath and their third-party vendors. With our internal data science, we can also develop our models, integrate them through UiPath AI Center, and deploy them. They're giving us an option to use them as a part of our RPA workflows with the help of the UiPath Studio activity called ML Skill. So, it becomes very easy for RPA developers to integrate machine learning models into their automation workflows, which is very nice, but I feel there should be some more improvement. They should give more visibility into how much time a model takes to finish the training and on how many algorithms it is running. They should also give visibility into which algorithm is best suited for my requirement and which algorithm is giving the best results for my requirement. If they can also give such insights in the same UiPath AI Center, it will help me in picking up the correct model and algorithm for my requirements.

When it comes to intelligent automation, machines use machine learning. No machine learning model can reach 100% accuracy or give 100% accurate output, which is a limitation. However, there is a possibility to increase the accuracy by tuning the parameters. So, UiPath should give more visibility into their models, how the pipeline is running in the AI center, and which factors can improve the accuracy of my model. Such insights will be useful for me in improving the accuracy of my intelligent automation.

In December 2019, I started learning UiPath, and I became an RPA developer in November 2020.

Until now, I have seen good uptime. There were no disruptions in data. I've seen the services running properly 99% of the time. Their logging mechanism, job schedules are also running properly in Orchestrator. So, it is a stable environment.

We're getting good support from UiPath. I would rate them 75 out of 100. Most of the time, I get fast and good replies from the support team. Sometimes, I receive late replies, or they don't understand the question properly, and I need to explain multiple times, but they are mostly good. 

I have worked on different IT process automation tools in the past. Their support did not respond as fast as UiPath's support, and they put the tickets in the suspended mode for a long time. They also didn't understand the question a lot of times and took too much time to analyze the issue. 

I also have the advantage of talking to my Infra team because we've deployed it on-premise. They can act as the first level of support and check if there is anything wrong with the on-premise server. If it is related to UiPath functionality, then we raise a ticket with UiPath support.

It was already set up when I moved to this team. I was working in IT process automation, and I moved to the UiPath development team. The setup and licenses of UiPath Orchestrator are managed by our Infra team members. They provided me with the licenses and links to the UiPath Orchestrator. So, I make use of the resources already deployed by my team. I just build and publish the packages to UiPath Orchestrator.

I have not deployed anything in the live environment, so I cannot comment about the return on investment. I've seen my colleagues deploying it, and with the help of data automation use cases, they have reduced around 10 hours per month for each support team. For my use case, we will be able to reduce at least one or two FTE for the support team when it goes live. I'm able to predict this because I have developed and tested many test cases for my use cases.

I only know about the community version. They give us two robots as a part of the community version, and they are enough for my practice and personal automations. For the office work, my Infra team checks the licenses needed for a particular use case, and my management team manages the pricing and licenses. 

Nine times out of ten, I would recommend others to use UiPath. I have also worked on other IT process automation tools, and none of them provides the functionality, support, and community like UiPath. I had conducted a survey on LinkedIn and asked about the RPA tool that people preferred. I got 60% of the votes for UiPath.

From the development perspective, I've seen a lot of improvement in the UiPath services in the last one year. They're giving more out-of-the-box models for the AI Center, and they are also improving their courses. They are also introducing new functionalities such as the orchestration processes in which you can use persistent activities, and your robot can wait for the human task to finish, and then it can continue its job. If they make any enhancements required for our current automation, we will make use of new UiPath functionalities to enhance our automation.

They have released two new versions of their certifications. One is UiPath Associate Certification, and the other one is UiPath RPA Developer Advanced Certification. I have completed the Associate certification. For these certifications, we have learning plans. There is recommended training, and everything is given on the UiPath Certification Program website. We have the option to check their recommended training and do the practices. They also guide us about how to book the exam from the Pearson website. Going through the recommended training and doing the Associate certification has increased my credibility. I've gained more trust in the company. It has changed my career. So, UiPath has played a prominent role in my career.

It can reduce errors by 100% because a machine can give 100% accuracy and work faster than humans. Just like all RPA tools, UiPath can provide 100% automation accuracy for rule-based automation. You also get better speed because machines are faster than humans. When it comes to intelligent automation, machines use machine learning, so there is a limitation. No machine learning model can reach 100% accuracy in automation.

I would rate UiPath an eight out of 10. 

We are a communications company who works with a lot of clients in our country. Now, we started using automation when working with business clients. Many processes were being done manually, e.g., activation of numbers. In order to alleviate the work of our sales team, this process was automated.

I haven't automated any of my work because the queue for processes that need to be automated is large.

My company uses Studio for our developers and StudioX for attended robots.

It is very important that we can scale automations without having to pay attention to the infrastructure. After one year, we have already automated almost 200 processes. Since the number of automated processes was large, a lot of people's time was freed. This solution is very important because we have a large subscriber base in our country, so we have become very efficient.

UiPath enables us to implement end-to-end automation, starting with process analysis, then robot building, and finally monitoring of automation. This is very important to my company because in the future we will have contracts with UiPath to sell licenses and provide the same experience to other companies, helping them automate their process. Therefore, it was very important to implement the entire end-to-end process in our company.

Attended automation has helped to scale RPA benefits in my organization by automating department or role specific processes in sales and HR that require human robot collaboration. This is important to my company. The department who works on automation of internal processes has had a lot of meetings with our employees. They realized that employees could be against their automation processes and sabotage them. This didn't happen, but they have effectively implemented the attended robots for our employees' work by explaining to them that the robots are not a threat to their job. They would only be helping them, allowing employees to do something more important than doing repetitive tasks on their computers.

UiPath has helped reduce human error. We are working with clients where it is very important to provide them their necessary services. We are a telecom company, so we are providing activation of numbers, etc. If people are doing this manually, it can cause inconveniences for our clients, but it might also put the reputation at stake. For example, because when people do it manually, they can send out the wrong invoice. This is a huge reputation risk, because sometimes we are working not only with just a person, but with a business. When we work with other companies, it is important to do things accurately. When the robots do things, there is almost a 100% probability that they won't make any mistakes, like typos.   

The most important feature of automation is it can automatically detect things where people are doing things repetitively and spending a lot of time. So, people can actually do their real tasks, like making decisions and talking to clients. Therefore, people's time, which was busy with doing manual tasks, is free now. They can spend it on more interesting and valuable work where they can apply their valuable skills.

UiPath Academy starts at the very beginning with how to set up and navigate in UiPath. I noticed that the Studio and StudioX are both user-friendly. It is suitable for people of different existing levels of programming skills, even with those with zero background.

The process mining feature is not being used because my company had some difficulties with it.

UiPath could improve integration with other platforms, like the SAP platform. I heard that SAP has their own automation processes in their platform and they are trying to avoid integrations with RPA platforms. Sometimes, that can be difficult. UiPath's room for improvement is having the ability to integrate with as many platforms as possible.

I have been using it for about three weeks. I have been practicing some tasks and just started learning, but I don't have any advanced development skills.

My company has been using it for a year.

We have automated hundreds of processes.

There are about 30 people on our sales team who are using it. The HR team also uses it.

We didn't use another automation before UiPath.

The initial setup is straightforward, based on what I have seen from UiPath Academy. On the platform, there are videos which describe how to set up. You just go to the platform and download the setup package. You have to set it up on your PC, then open the application. Once the application has been opened, you need to sign in with your email. For the first step, you need to add your email to the application, so email is sent automatically to you when you sign in and the signup is complete. Then, you can start using the Studio and StudioX. It is very convenient because both of them are in the same application, like an all in one software. You don't have to set them up separately because everything is in one place. You can just switch between them in settings, which is very easy and straightforward.

We have people studying how to work on UiPath who are developers. Therefore, we have a whole department doing the setup in our company. I don't think that they are asking a third-party to come in and help. 

We freed up a lot of our sales team's time. For example, they can now spend more time with clients. We have successfully implemented attended robots for our sales team. They now spend half the time doing the job which has been automated. This has made our sales team happy. 

It is very costly to implement RPA. However, I think the benefits outweigh the costs over a long-term period.

Building automations is doable. I understand that it is hard. Some processes need to be adjusted to be automated. Even though sometimes it can take time to create processes for automation, it is still possible and useful to apply automation for many processes. 

I didn't have any background in programming previously. I chose the learning plan for beginners in UiPath Academy. It was very convenient that they divided their learning plans for people with different backgrounds, e.g., beginners or developers. The course is very well-structured and concise. It works perfectly for me and I have the ability to study in the solution without any background experience.

Because we managed to successfully implement it in our company, we now want to help other companies to implement their automation processes.

For my country, UiPath is progressive. It is important for people's mindset that they are able to work with robots and understand they are helpful.

A lot of companies in our country refuse to implement it, or they think it is very expensive, and they don't need this thing, but they should definitely go for it.

My biggest lesson was not to be afraid that robots will do my job. I learned that they are very helpful and can save me time that I can spend on something more useful, like obtaining new skills.

I would rate it as eight out of 10 because of its integration limitations with other platforms. It is also expensive.

We mostly use UiPath in the healthcare and banking/finance sectors. Our use cases depend on the different sectors we use it for. A typical use case would be an Excel file with lakhs (hundreds of thousands) of records that we need to filter and apply some business rules to. We may have to check whether numbers are in integer or alphanumeric format so that they can be accepted by a particular application, or whether date data is formatted correctly.

We use it for end-to-end automation. We take all the input from users, regarding the full life cycle of a process, and use UiPath to create a business solution. An end-to-end project can include taking an Excel file and putting the data into a data table. Based on that, we create some business rules, check things with validations, and then create some templates. We upload the templates for different legacy applications so that they can be automated. A bot will run these scenarios in the backend, in either attended or unattended mode.

We may take student records and place those records into a particular template which we then upload to an application, whether a web application or a desktop application. If a human was involved in doing this, it would take days to filter the Excel and create a template based on a particular record. But by setting up some business rules through UiPath coding, it automatically applies those rules to create the template and upload it to the application. We can then send a notification to the user by email, because we have connectivity with Gmail, Outlook, and SMTP.

A human being can work eight hours or nine hours per day on average, but a robot can run 24/7. With automation, we can save time and money by continuously running things on the same machine without any errors. The accuracy can be 90 or even 100 percent, depending on the logic of the code. It also helps the communication between clients, users, and our organization, improving the partnership. It definitely reduces human error because it's automated and well-tested. It increases work volume because it's very fast. In terms of the amount of time it saves, for repetitive tasks it can save 90 percent of an employee's time. Employee satisfaction has definitely increased.

UiPath is also helping us to increase the number of tasks we can do. For example, if a human being is reading an Excel, doing some operations and validations within it, it will take hours or days to complete. But using a UiPath robot, we can simply create the set of necessary instructions in our code so that it will run within minutes or even seconds sometimes. It is very fast.

We use every component of UiPath, from Studio to Orchestrator. It's very helpful and it is very fast. Orchestrator is very beneficial because we only need to create a particular robot once and then we can simply connect it to machines. It definitely saves time because we only need to maintain the versions of a package and the code, and that can be done locally or via Studio. Because there is a chance code could be deleted on a local machine, the fact that Orchestrator is in the cloud means we can definitely retrieve it from there.

Orchestrator also helps save time because there are scenarios where we have multiple stages of input, where something depends on a value. As developers, we don't need to provide the particular input and again publish the same package. We just go to the cloud, check the process, check the assets, change the value, and it will automatically update. It's a robust solution. Like its name, Orchestrator really does help us orchestrate things.

Also, non-technical people, the users, can see what is happening in their jobs. They can check the status of particular scheduled jobs and see whether they are running or busy, and how many bots there are.

Attended robots are also helpful because sometimes we have a scenario where a user cannot share credentials because everything must be secure. In that type of situation, we need attended automation that can be run on a particular machine in front of the user. While it's running, they can do other work on the same machine. That kind of implementation enables us to automate while keeping things more secure. This is important to us because security is a main concern. It allows users to keep their information safe, rather than making it available on other machines. It's their intellectual property and we respect that.

The most valuable features are some of the panels in UiPath Studio. For example, there is a debugging panel and a Designer panel. The debugging panel is useful because without it we could not solve any problems. The debugging panel provides functionality such as Step Into and Step Out, and we have highlight buttons. It helps us to analyze our code, what is wrong in a solution, and debug from the start to the end, to make the solution better.

The Designer panel is where we create a workflow or step-by-step process, the place where a developer develops the code.

Within UiPath Automation Cloud, we are using Orchestrator in which we can

• deploy the bots and maintain services
• create attended and unattended robots for different versions of machines and manage which robot runs in a particular environment
• use the queue to manually configure the times that bots repeatedly run. Using Orchestrator, we can simply schedule the target application. The queue also has a retry mechanism so that it will automatically take input, and we can specify the number of retries
• store a user's ID and password credentials in the Orchestrator database
• check the Orchestrator home page for what processes and jobs are running, and see any feedback on them, as well as the output
• see the logs in Orchestrator.

They are currently working on most of the things I have thought about that need improvement, such as connectivity with other software and AI/ML capabilities.

But one area for improvement is connected to the fact that it's completely based on Visual Basic .NET and C#. I would like to see some more basic activities that are particular to the VB.NET code, as well as activities based on LINQ queries because that is one of the fastest and most integrated languages. I would like to see pre-written activities so that we could simply drag and drop them into place and use them frequently. It would be better to not have to go into the syntax for that particular language code. I would prefer if we could use activities from the Activities panel, and just provide the input and output, and they would work in the backend.

I have been using UiPath for the past two years. I have very good experience in this particular tool, as an RPA developer. I have created enterprise solutions and business solutions from end-to-end.

The solution is stable because it has been developed precisely and it's already optimized. It depends on the user's input and on the architecture and the environments. We have very good stability.

UiPath is very scalable. It depends on the user's requirements and on the approach we follow. A modular approach makes it more scalable. For example, if we have different VMs, different accounts, or different licenses for the machines on which we are running, we can simply create one package and we can deploy it on the various machines, if we have the licenses for those robots. 

You can create one set of code or a package and run it anywhere, if it is suitable and the requirements are met. That's one reason the scalability is very good. 

We have a huge market and a huge environment. We can continuously run with a multi-bot architecture. If the code is developed that way, it will definitely increase the scalability.

UiPath is used by many users in our company. Their roles are varied. They could be in data analytics or they could just be doing some tedious task.

The business side is happy with the solution because it is decreasing tedious and repetitive tasks. They are happy with the time and money savings. As a result, they want to do other things via UiPath robots. They want to find other processes where the work can be done more productively.

UiPath support enables us to manage issues by creating non-production and production tickets. We can discuss issues in calls and show them examples of the particular issue or activity under discussion. They provide us with support. Sometimes, when activities are not working, we can upgrade and downgrade the version of that particular activity. We can even send logs to them so that they can analyze and troubleshoot issues. It definitely helps.

I have only used UiPath for RPA. I have read about tools like Blue Prism and Automation Anywhere,  but I cannot compare them. They all have their own advantages and disadvantages. I like UiPath because it's user-friendly and it has a very big community in the forums. We can learn from the community. And the UiPath Academy provides training, certification, and diplomas so that a person can learn and develop the ability to create a solution.

The initial setup is a little complex. You need high-end knowledge. You need to create the Studio setup on the different VM environments, deal with the licenses, and the Orchestrator setup. All of that requires good knowledge. You need to understand infrastructure and how things are set up. It's complex for regular users. The installation itself is relatively easy, but understanding the infrastructure is challenging. With guidance and training, it definitely becomes easier.

Licenses are costly, but, in the long run, UiPath will definitely help the business. Developing a solution is a one-time investment, which can be completed in a couple of days. But that work will be done next month, and again and again for the next 10 years. It definitely helps with digital transformation because it can connect solutions and create better opportunities.

UiPath is a good investment and return on that investment is very good. We can create robust solutions with UiPath.

Some licenses might be costly but it depends on the type of work involved and the turnaround time required. If you want to include AI/ML bots, it will definitely cost you more. If you want to use some of the latest features, like UiPath Insights, that will cost more.

But for low-level bots and automation and normal use of Orchestrator, the cost is per-bot.

Overall, pricing of the Enterprise Edition is pretty good. And for practice, we have the Community Edition, which is free. They also provide trial robots for two months so that we can use them for learning.

When it comes to implementation, we think about how to make a solution robust so that it can be controlled and configurable. That way, if something changes in the future, we can work on it accordingly. It should be a modular approach.

You need to focus on requirements-gathering so that you can focus on exactly what the user wants, how the application behaves, and what kinds of errors might happen. You need to check all the environmental factors. Those are all lessons I have learned from creating UiPath automations. You also need to analyze things from the business perspective and think about how much money and time is being invested and what the ROI will be in the end.

End-to-end automation, starting with process analysis, then robot building, and finally monitoring of the automation, is a very important aspect of UiPath. Rather than starting directly with the coding, we analyze the business process so that we know how the business is manually doing something and understand their problems and how much effort they are putting into it. We then start to think about how we can use a bot to save time and money. Each phase of the process life cycle is important because, phase-by-phase, things need to be passed from one to the other as input. After delivering the automation to production, we need to provide monitoring services so that if there is an error or downtime, we can make changes. That is why each phase is important in the life cycle of RPA.

From the business perspective, we check what kind of automation is involved and how much time and money we can save by automating, as these kinds of projects are high-budget. The main goal is to run the business as fast as we can. We analyze whether it is suitable for the business and how it can be profitable. We look for processes where we can save 85 to 95 percent of the time or money involved. We also consider how much human error is involved in the process as it is.

Currently, we are not using the AI/ML functionality. But because I use the Community Edition of UiPath in my personal work, and it has the latest features, I have attended the training for AI Center provided by the UiPath Academy. I tried some analysis with these models, as well as the checking of words by AI/ML, in the Community Edition, and it is one of the excellent features. It's very useful. ML models are amazing. They are using APIs which are connected to Orchestrator and they are running those kinds of models. We can also deploy our own custom models if we know the AI/ML tools.

UiPath is one of the best tools available in RPA and it's currently booming. It's the perfect tool because the UI is very friendly. It is widely used. I believe pretty much everybody in the IT industry is working on an RPA solution, many with the help of UiPath. It depends on the particular business and whether they have the capacity, but everybody wants to increase use of UiPath because it provides cloud-based automation and it's a robust solution. Everybody is happy with the solution. They want to create more automated processes so that they can decrease that time and costs in their overall projects.

I'm working on a supply chain management project, where some of the distributors are eligible for some of their stock to be returned. The beginning of this stock rotation, and the interactions, are through email. It was previously done by representatives, but we are now automating that process so that we interact with the distributors using email. Responses are sent based on the validations that the bot performs. It's an end-to-end process, all automated using the UiPath.

The project I'm working on creates a lot of availability for employees to concentrate on other activities. Human interaction is reduced. Instead of all the management representatives interacting with front-end people, UiPath is interacting through the API. It has increased the time available to our associates who were working on that particular process. If 10 people were working on a particular process, that number has been reduced to three or four, and the other people have been able to concentrate on something else. The stock rotation process itself would usually take a month in a particular region, but that has been reduced to less than 15 days.

We have also automated a few processes that have human and bot interaction, using UiPath Action Center. When there is human interaction in a particular process, it takes a lot of time. But when we integrated a process with the bot through Action Center, the time needed for the human interaction was reduced. It gives time back to the person who would be doing repetitive work. For example, if a value is different from what the bot is expecting, an Action Center task will be triggered and the human will submit the input that is needed. The rest of the process will then be taken care of by the bot. So the time spent on a particular validation is reduced.

Also, if you compare the situation from a couple of years back, when I started using UiPath, and the present, there has been a lot of change in the way UiPath comes up with new products when it comes to document validation, such as Document Understanding. That does speed up the digital transformation process, and I haven't seen any requirements for additional infrastructure as a condition for benefiting from that transformation process.

UiPath has also helped to reduce human error, and that reduces the time that a particular process takes to run.

For beginners, UiPath is a very low-code or no-code experience. They can get started with StudioX. The best place to learn the solution is the UiPath Academy. If they come across any hurdles, the forum is an excellent place to post them and get answers. As a community, UiPath is very encouraging for newcomers. People with no coding experience can automate processes.

Initially, because I was working with Automation Anywhere, the switch was a little bit overwhelming. There are comparatively more Activities in UiPath. The scope is very large; you can automate large processes. But eventually, I have come to feel that building automation is easier in UiPath than with Automation Anywhere.

Also, in my experience using UiPath automation, we have not had to make any changes to infrastructure. It has really been a seamless interaction.

We don't use the UiPath Apps feature yet. I did a PoC on it and it looks like a wonderful product. But when we are using Action Center with Apps, the Action Center stage is built in Orchestrator, but the same field is not built in the Apps. We have to work around that particular process, to make Action Center and Apps work together. Action Center waits for a particular input when a particular task is triggered. This stage is not built in Apps. UiPath Apps should be stepped up in terms of its functionality and integration with other UiPath products.

I have been using UiPath for almost three years.

I did come across an issue very recently where, when I had to update the version of the Activity package I used for a particular deployment, the Data Table Activity, it did not list the way it had been listed. I raised a question in the forum, but there was no clear answer. Apart from that, I haven't seen any other instability with UiPath.

UiPath is scalable. We have deployed bots across many regions. There was no limit in that respect. I haven't seen any issue; the scalability is good.

I work in the automation center of excellence in our company. There are 50 to 60 teammates there, working on UiPath and Automation Anywhere. In UiPath, they work on the automation of SAP. In addition to my work on supply chain automation, there are a couple of projects dealing with our customers' needs. Our organization builds products that are generic and we then customize them to meet those customer needs. There are also some projects where Excel activity is the focus. And we recently started using Document Understanding in a PoC. We generally have two or three developers working on deployment, along with one DevOps person. Not many people are required for deployment.

I haven't contacted UiPath tech support, other than posting that Data Table Activity question in the forum.

I was working with Automation Anywhere for a year or so, but because of the requirements of our company, I had to switch to UiPath. The switch happened because a customer we work for deploys UiPath.

I have been able to learn things like interaction with multiple enterprise systems, including OBI, using API calls. Unlike other automation applications I have used, implementing a process using UiPath is very easy.

In terms of end-to-end automation, there are products that are useful for identifying processes for automation. But for the process I'm working on right now, we did not use UiPath to implement end-to-end automation. Identifying the process for automation was done separately. Only building the bot was done in the UiPath. The process is not end-to-end, except for the bot development. When I think of "end-to-end," it includes identification of the process for automation. From there, you need to build up the process, the documentation, et cetera. End-to-end is important, as it means you aren't switching between multiple tools.

Our core business is BPO, which is Business Process Outsourcing. We have massive operations that we have to perform for our customers and we have a digital section of the company that is assisting with that. The digital section is relatively new, being no more than two years old. We are building a number of solutions and tools that our digital section is using, and RPA is one of these tools. The goal is to help our customers innovate and assist them with their digital transformation, ultimately making them more efficient and more profitable. This is possible because some of the processes are very repetitive and performing them with humans is a very bad choice.

We have a hybrid environment, where some of our functionality is on-premises and some is on the cloud. For example, we have some cloud-based automation, and we use UiPath Apps, which is on the cloud.

We had a successful use case at the beginning of the year where we needed to process a large number of invoices that had contained errors when they were originally sent to the customers. There were approximately 200,000 invoices and we had a deadline of four days to complete the task.

It began with us developing the bot, which was completed in less than a day. After that, we sent the bot to our production environment to start processing the invoices. We were successful in the task, through the parallelism of 50 robots, we could process 5 invoices per second.

We have some metrics that describe how long it would take the process to be completed manually. It takes a human an average of between 60 and 90 seconds to process just one invoice. We estimated that it would have taken approximately 125 days to complete this task manually, with between 250 and 300 people working on it together.

We don't use the low-code functionality. Rather, we use the typical development features. When you're talking about developing inside the UiPath, you have something very user-friendly, so you don't even need to use the low-code options. It is very intuitive and you don't need to know technologies such as C# or .NET to develop automations.

The use of UiPath has helped to increase customer satisfaction by a lot. Our main goals are to improve the average handling time that the customer needs to complete transactions, as well as to improve quality. Customer satisfaction improves not only with the financial benefit resulting from a better average handling time but also, from improved quality in transactions. Our human resources department uses tools such as surveys to investigate the quality and they have their own metrics and KPIs for customer satisfaction.

Our first-contact resolution rates have increased because as we develop successful cases and implementations for different customers, future customers benefit from this through faster service, which leads to better customer satisfaction. I estimate that our first-contact resolution has increased by 15% to 20%.

The time it takes us to create automations depends on what we assess the complexity of the bot to be. We have a methodology and metrics that have been developed by our Center of Excellence, categorizing the bots into small, medium and complex. A small bot, which has simple logic, is something that we implement in between one and two weeks. A medium-complexity bot has a timeline of between two and four weeks, and a very complex bot takes four to six weeks to implement.

The most valuable feature that we are using is UiPath Apps because it makes it very easy to implement tasks. It is very easy to scale operations, which is important because we're not talking about just five or ten agents. We're talking about 1,000 to 2,000 agents. The Apps feature helps us to scale very quickly and very easily. We only need to develop one or two bots and then link them to UiPath Apps to process everything. All of the integration between the bots and the human, along with any scheduling that needs to be done, is taken care of by Apps. In our situation, the Apps feature is the best solution to handle this scale.

Utilizing our bots is very easy, and it is done using the licenses that we have with partner UiPath. We can access our licenses, then distribute them to the customers and we can use them dynamically. This is all done in a very easy manner. We just have to navigate to the web-based hub, where we have access to everything that we need.

UiPath is highly customizable and this is helpful for us because we can develop models and frameworks that can be reused for different tasks and different customers. For example, if we have a customer with a process that is very similar to one that we have previously developed for somebody else, we can reuse the models to scale the bots. This makes the new development very easy and very fast.

The Agent Console is able to provide customer insight in conjunction with the task and process mining features that we use. We install the tool into the machine that the customer uses every day, where it will capture the manual tasks and processes into a database. The insights that we receive are related to whether a process is a good candidate for RPA. For example, if it takes the human a lot of time to complete, or they are having trouble with it, then it might be suitable for RPA because putting a bot in place can optimize performance.

Another reason this is important is that human operators work very hard with day-to-day tasks, and they don't have much time to stop and look for processes that can be automated. Using task and process mining, it starts pulling out those insights. For example, it looks for the number of screens that the human is accessing and clicking on. It looks at each click, as well as every navigation and extraction. In the end, it generates a report for us.

The Agent Console has helped to decrease the average agent handling time, which is our main goal when it comes to these massive business operations. Average agent handling time is the metric that we primarily work with and as such, everything we do is related to reducing it. RPA in our use case is not used only to reduce the HC or FTEs; but it is used to boost this particular KPI too. In one of our use cases, we have had an average decrease of 30% in agent handling time, which is very considerable.

There are some enhancements that can be made within Orchestrator, such as the addition of new dashboards that provide us insights into processes that are already running, which would help us a lot.

We have been using the UiPath platform since last year, at the beginning of 2020.

The stability of UiPath is very high, and this is a very important point. In fact, stability was the problem that we had when we were assessing the competition with UiPath. We evaluated several RPA tools and moved on with the UiPath partnership because it was the most robust. It is important to remember that we have a high availability environment, and the entirety of it must be stable. Our team is tool agnostic and extremely skilled in the largest RPA tool providers, enabling us to develop automation on any platform.

UiPath is very easy to scale because, in every part of our solution, we use the Apps feature. This accounts for high availability and automatically provides us with scalability. For example, if we have a process that is handling 100 invoices at a time, but in three months we grow and need to instead process double that number, there is a feature that we can use to instruct the bots to run on additional machines. The scalability is very dynamic in this regard.

UiPath has a function within Orchestrator for dynamic allocation, where it can draw resources from a pool of machines in the infrastructure. For example, if there are 30 machines available then an option can be set to dynamically use the licenses. If there are 10 or 20 bots that need to perform tasks, the licenses will be automatically used to run the processes. You don't need to look at these machines to see what is running because all of the management will be taken care of automatically.

We currently have 25 staff involved in RPA. There are 20 developers and five architects, just to keep the projects and everything with the customers up and running. We expect this to improve and grow, doubling our numbers this year.

In fact, our expectation for growth is very high. Along with each implementation or development that we do, new opportunities arise. I would estimate that for each successful implementation that we have, four to five new opportunities are presented. Naturally, we will need to have more licenses and more contacts to increase the total number of bots in our environment.

From end to end we have about 50 robots already developed and running in a productive environment. We have human operators, back-office analysts, supervisors and coordinators involved in the whole process of execution and monitoring.

After our initial deployment, we have rarely needed to be in contact with support. Our in-house team can do most things autonomously.

We have a premium support package from UiPath and they are very useful and very helpful. They help us with whatever we want and without any doubt support is one of UiPath's strengths. This is not just in a technical sense, but in terms of business and strategy, as well.

As mentioned earlier, our RPA team is agnostic to the tool to be used. We can give our recommendation based on the customer's needs but if he has any premise that a specific platform should be used, we follow his needs.

The initial setup is very straightforward. We have a very good team of architects and we also had some assistance from UiPath. It was not simple, but it was not too hard, either. It was okay and we didn't have any problems with the implementation. In total, it took between three and four weeks to complete the deployment.

In terms of strategy, I think for the best implementation, you need to first have the infrastructure set up. The infrastructure and architecture should be very well defined with UiPath because you have a bunch of functionalities that may or may not be useful, depending on the type of business.

Deciding what functionality is required is the very first step. Then, the second step is to have a methodology and a center of excellence for RPA, including frameworks and best practices. This will help to ensure that everything is implemented correctly and that you don't have problems in the future. Finally, you need to have certified developers and certified architectures because this is the most relevant part. You want bots to go live with the best quality to ensure customer satisfaction.

We now have the ability to provide this type of environment to a customer very quickly. We can configure the environment in between two and four hours, to have it fully up and running, and it is very simple to do. This is because we have an RPA infrastructure already built, so you just need to acquire the hardware that includes the machines and servers. Once they are up and running, we activate this section and we can develop and build the bots.

UiPath was a big help during our initial setup. We have premium support, and they helped us with parts of the architecture, the infrastructure related to servers and the cloud, and getting it all set up properly in our high availability environment. It was like a four-handed job and it was all done well.

We have many different projects and customers and I would estimate that it has saved us and our customers something between $4M to 5M in total.

Just looking for our success case of the invoices processing, we avoid a cost of $10M.

The price of UiPath is higher than competitors, although the cost depends on what functionality and tools you require. For us, we don't need anything extra in terms of functionality but our contract includes an extra charge for premium support.

We evaluated UiPath, Automation Anywhere and Blue Prism, all the best RPA tools providers in the international Market. As we are agnostic with the platform, we can develop using any of those three tools.

One of the cons of UiPath is the price. It's a bit higher than the other RPA tools. In terms of the pros for UiPath, it is more stable, it works in our high availability environment, the support is good, it is very agile and we can develop automations very quickly. Also, implementation was very fast and scalability is important.

We have conducted a proof of concept using UiPath's unattended robot capability to enable a self-service chatbot. Specifically, we used the unattended bot to speak with our S3ND (messaging) solution, which is a chatbot. The scheduling was done via APIs and the communication was done through the chatbot. This is something that we have tested, but not yet deployed. We do think that this is an important next step for us to look at.

We do not use the Document Understanding and AI Fabric features at this time but we are already testing it in some of our customers to implement them as soon as possible.

Another feature that we do not yet use, but we are looking into, is using the AI Center to drag-and-drop machine learning models into RPA workflows. We recently had some discussions with the technical specialists at UiPath about the newer features that are available, and we are looking into arranging for training and webinars that will teach us how to use these new features correctly. Once we have a better understanding of how to implement them, we will begin looking for specific use cases.

The biggest lesson that I have learned from UiPath has to do with our customers and their operations. The most difficult and important challenge that we have is changing the mindset of our customers such that it is in line with digital transformation, and this is something that UiPath helps us with. They provide us with everything we need in terms of security, implementation, and high availability. Really trusting that these bots are doing the right thing is the biggest advantage that UiPath provides for us.

There are three main points that I would make for anybody who is considering UiPath. The first is the cost, in terms of money. The price of investment is high but the benefits are uncountable. Next, it requires that you look into what you really need, and whether it is all of the features that UiPath offers or just some of them. It is also very important that you look at your infrastructure because it has to be able to handle all of the bots. For example, we know that our processes need a lot of computing power and a lot of memory, so the hardware is important. This has to be built in advance of purchasing the software. The final part is the team, including the developers and architects. It is very important that they all be certified by UiPath. There is training and courses available, they make everything clear, and it includes learning the best practices, frameworks, and models to assure that you're doing everything right. If the company is audited and you are doing it properly then you won't have any headaches.

I would rate this solution a nine out of ten.

We primarily use UiPath for end-to-end automation. We develop both attended and unattended bots and we use the Orchestrator module, hosted in Azure.

Some of our typical use cases involve automating operations like downloading files online, analyzing and capturing details, saving them in another location, transferring them, and uploading them in other forms.

The app studio feature has increased the number of automations that we create while reducing the time it takes to create them. For example, we have a limitation when it comes to transferring files from one server to another server. However, we were able to resolve it by using a remote desktop on the UiPath server. I don't need to log into another system or another server; instead, I log in and use the remote desktop from my PC. It's really cost-efficient and it saves me a lot of time. It's superb.

UiPath helps us to implement end-to-end process automation starting with process analysis through to monitoring, and this is very important to us. Whether we are automating processes for external customers or internal purposes, there is an automation lifecycle that we follow. The end-users do not have much knowledge about automation, so we have to complete it from end-to-end.

It starts with analyzing the process to see if automation will work. We then develop it by trying to replicate what the user does manually. Once it has been developed and the functionality replicated, we test and tweak it for approximately two weeks. If everything goes well during this time, the process moves to production. In production, processes are continuously monitored.

The testing is a detailed process that involves finding the problems, then implementing error handling using try/catch statements and other methods. It is done in a continuous, agile fashion where we develop, publish, trial, error handling, monitoring, and then it starts again. When a process is pushed to production, when a change is made, it does through this lifecycle again.

How UiPath has improved the way our organization functions is clear when we look at one of our use cases. We need to have notifications about documents that describe the release of products. Our bot will start by filtering documents online using keywords, download the appropriate documents, then check to make sure that each is complete. If there is a problem then emails are automatically sent to the appropriate department.

From this point, we transfer the file into another folder and upload the current version to the release team. They will only receive what they need, rather than having to go through the document themselves. Prior to this, they needed to check it on their own and analyze everything. With this work being done by the robot, it relieves us of two person's workloads. What used to take three people to complete, is now done with one.

In terms of saving time, for our use case that involves the release documents, we save between 80 and 100 hours per week, so monthly, you can multiply that by four.

The time saved by our employees sometimes allows them to focus on higher-value work or in other cases, when we don't need the persons, we can reduce the workforce and then hire people in different roles, such as new developers. Overall, this helps us to improve our workforce. For example, we can branch into more areas, rather than do the same thing for many different customers.

With respect to employee satisfaction, if somebody loses their position then they may not be happy. However, it is important to remember at the same time that we may open a new position because of this opportunity. This allows the person to move, find new opportunities, focus on new things, and develop themselves. To me, this is a win-win because we are more focused on generating new types of business.

UiPath has definitely helped us to reduce human errors. This is a benefit to us because, before this, we used to get customers complaining quite often. However, we have reduced the complaints. We still need to have the customer complaints section but now, we have reduced it from five people to one. The robot is not 100% error-free, but it's between 90% and 99.9% error-free. With so few complaints, we don't need as many people to deal with them.

Overall, UiPath's process analysis and optimization have increased our productivity.

The most valuable feature for me is the UiPath Studio.

It helps a lot. I wouldn't really say it's code-free; however, I would say that it's 90% code-free. It's very easy to use, with most of the actions performed using the drag-and-drop interface. When you do write code, it's a very small amount of the time.

The library activities are really helpful. With the help of the library and with the help of the forums, developers can focus and it is easy to learn. It helps in terms of time-to-value.

I also find Orchestrator to be helpful. The Studio and the Orchestrator together are like your body and your soul. Without both parts, it won't function. You need to have Orchestrator to run the Studio. Right now, today, we have a problem with our Orchestrator and it's not working. I can't use Studio because it's connected and without access to my Orchestrator, I can't do anything.

The academy courses help in the process of getting employees up to speed with the solution by providing them with the fundamental knowledge and the opportunity to practice. When you start doing it, you may face errors and again, with the docs, you may gain more knowledge. When you start to use the forums, you get more knowledge, and it all helps. But, if you only rely on the forums, I would say that it would help only 60% or 70% of what you get compared to taking the academy courses. In the end, you will only get better by doing it, and then going to the forums when you have problems.

The testing and release schedule for Studio should be improved because we find that with two releases per year, one of the versions is stable and the other one is not. It would be better to focus on a single release, but make sure that it is stable. We have had problems in the past with this and we don't need any unstable versions. For example, version 20.4.2 was not stable but version 20.10.2 was very good.

Technical support and customer care are areas in need of improvement. 

We have been using UiPath for between six and seven months.

We are in Switzerland and normally, we use local support. When they cannot resolve an issue then it is transferred to the US team and we get support from them directly. In our experience, the support in Europe is not sufficient and we prefer to speak directly with the UiPath headquarters. We find that here, the people do not have enough knowledge.

We have had a lot of problems and for example, we have an issue right now where our Orchestrator doesn't work. We have had to wait about a week for the ticket to be escalated to headquarters, and because of delays like this, we are not always happy with customer care. The product is good but the technical support can improve.

We had issues where the first person tells us one thing, but a second person says that it's wrong and it needs to be done another way. Then, a third person speaks and presents another idea. This all takes a lot of time before a fourth person explains that everything is wrong and it has to be done another way. A lot of the time when you have these kinds of problems, you just have to start from scratch.

It can be frustrating because we had spent almost three weeks upgrading our system to the 20.10.2 version and now, we face the same problem. We have not been able to properly run our system for between three and four weeks.

I have not personally used another RPA solution but I have colleagues who have experience with Automation Anywhere. We primarily use UiPath but there are some developers in the company who regularly work with Automation Anywhere.

We did not switch from one product to another. Rather, they are used for different reasons. For example, I have heard that when it comes to performing file transfers, Automation Anywhere makes it quite easy and they do not have the limitations that UiPath does.

On the other hand, I feel that the AI in UiPath is doing better. We have lots of workflows and activities in UiPath and I strongly prefer it as a product.

I wouldn't say that the initial setup is complex, although when you are just beginning with a new environment, it is not that easy, either. Because it is a new thing, you will need to learn in the beginning.

We followed the guide and found that the installation was not very tough.

UiPath saves us costs, but there is more to it than that. It saves us in terms of time spent on manual tasks, but on the other hand, we pay UiPath. On yet another hand, with the money we save, we are open to new opportunities and new business.

Overall, I am very happy with the ROI.

The price of UiPath is a little bit high, although there are no costs in addition to the standard licensing fees. Overall, it is not too costly, but slightly high.

We have not yet used the AI functionality but we are trying to. We have not developed any uses cases yet but it is something that we are working on. We will be taking some courses on it first and after that, we may try some internal use cases.

We have advanced our technical knowledge by using this product. For example, we now use JSON config files, rather than using Excel.

One of the biggest lessons that we have learned is that it is nice to have a good solution design before starting development. There were times where we tried to do something one way but a problem occurred, so we had to solve it by trying different features, then testing and running it again. A lot of time is spent during this process. Now, we have learned to focus more during the design, then start to develop it.

My advice for anybody who is implementing UiPath is that it works really well in Windows, so they have to have a Windows machine if they want to start developing.

I would rate this solution an eight out of ten.

We develop and deploy use cases in the area of the cloud. We have deployed over 100 use cases. Most of our use cases are related to SAP applications, web applications, and mainframe applications.

One use case example is related to mainframe applications. The bot monitors mainframe applications 24/7. If there are any new jobs, they are identified, then the bot changes the status of the job to differentiate it. 

Previously, we are using the 2016 version of Orchestrator, then we upgraded to the 2018 version of Orchestrator. Some clients are deploying the 2020 version. It depends on the client. We suggest using a version back to clients, i.e., the 2019 version. 

We automate retail, sales, and agricultural services.

There are a bunch of candidates being monitored 24x7. Automation Cloud monitors these jobs, and whenever new docs come into the application, it will then change the status manually based upon certain conditions. Once we deploy the automation into the production, our manpower has been reduced so there are only one or two people needed for the backup. The rest will be taken care of by the automation itself. So, there has been a drastic reduction in our workforce.

We schedule different jobs using Orchestrator only. We have a separate team who takes care of jobs that we apply in Orchestrator. So, if there are any failures, it will automatically send email alerts to us. 

Within Orchestrator, there is a tab where we can restrict roles from the admin level to the user level. Developers give only access to the jobs. Whereas, admins have a roles option to restrict access.

There are still some areas that need improvements. Currently, the tool is not 100 percent accurate with hand written notes and image based automation. It is also tedious using it with Word applications. 

We are doing automation to take care of all our processes, but we still need support people 24/7 to monitor these jobs. So, human intervention is still there. We have two people monitoring these automations 24/7 because there are still some challenges with the automation.

I have been working with it for two and a half years.

When new bots are developed, we definitely see some errors in the first few days, which are usually connector issues. Once the bot is moved to production and has a lot of enhancements and patches to the automations, we make sure that the automation is running smoothly. So, during the initial stages, it won't be very stable, but after a few enhancements to adjust to the automation as time goes, then it will become stable.

Once we deploy and release the automation into production, we will monitor production to see if there are any new challenges, different scenarios, or bugs that we need to fix. We have monitored the automation after deployment for around six to seven months, and the automation went smoothly without any issues. Because the automation is performing pretty well, we have deployed it to more of our workforce and their different jobs.

We have separate, dedicated test data in three different environments. Orchestrator has a database and email server, so everything is in Orchestrator. Apart from the servers, products, and services, everything has a separate operations team, which has eight to 10 members, who take care of everything.

Previously, they used on-premises services for the bots. Then, they asked us to migrate more than 20 bots from on-premises to our AWS environment. So, we have created a dedicated AWS environment for them.

The deployment process goes this way: 

1. Developers develop the use case in a development environment. 
2. Once that is done, then they will move the code to the non-cloud environment.
3. They will test the code if the automation is running fine or not. If automation is running fine, they will show the data which is running fine as a code to the client. 
4. Once they have the desired output, then we will move to the production environment. 
5. The operations team will then deploy that process. 

The first time, it is a bit tricky. Going to production, it will take around 20 to 30 minutes to deploy the first time. If there is already existing automation, we only need a patch to implement it in production, then it will take roughly five to 10 minutes to apply.

The process of testing and deploying code takes roughly one to four nights maximum.

For deploying UiPath, we need at least three to four RPA developers. In general, one person can deploy at any time. The other two to three people are just there on support calls. 

Post-production, we have an operations team of eight to 10 members who take care of the automation.

There are some automations that save us thousands of hours monthly. These are automations that we run 24/7 as well as some automations that we run every five minutes for installing backups. Depending upon the amount of time the automation is standing, we will manage the capabilities of the server. 

To some extent, it has reduced the operations:

1. The automation is sending an email whenever there will be an error. Automatically, it is not going to the user. The user just needs to verify their emails. 
2. Whenever an error is noticed in the code, the automation will fit the address and email the operations team members. 

In these ways, it has helped to reduce operation costs, but not completely.

There are three types of licenses: unattended, attended, and developer.

We also use Automation Anywhere (version 10) and Blue Prism automation tools, but I think most clients prefer UiPath. There are more activities available in UiPath versus the Automation Anywhere version that we use. For example, UiPath has database-related activities, but Automation Anywhere, version 10, does not have this feature. I have tried using mainframe appliances in UiPath and Automation Anywhere, and I found that UiPath is more flexible and has more options available.

The solution is single sign-on, so the authentication is done for us, because it is difficult to remember all our passwords.

We have a ServiceNow ticketing tool for reporting issues related to UiPath.

UiPath is very good for developing web-based applications, especially for SAP and the web. For these two applications, you can go with UiPath without any doubts.

I would rate this solution as an eight (out of 10).

UiPath is used to automate processes, eliminating the need to increase headcount.

There was an increase in both quality and quantity while not having to increase admin simultaneously. We have successfully automated the majority of our automation projects.

The UiPath automation has helped us to keep our bottom lines down across the board.

UiPath has helped our organization with its environmental and social initiatives.

It has freed staff time for other tasks, improved their work quality, and saved hundreds of hours per month.

UiPath is the best automation solution available today. The process and task management are the most valuable features.

UiPath's Unassisted Task Mining has room for improvement.

I have been using UiPath for four years.

UiPath's stability is reliable, especially now that we've moved to the cloud.

UiPath scales well. We have not had any issues.

UiPath support has been responsive to us.

Positive

UiPath has successfully met our expectations by reducing project costs through automation, demonstrating a strong return on investment.

I would rate UiPath ten out of ten.

I have used UiPath in my last three companies.

We use the solution for the implementation of automation for normal processes. We deliver use cases to customers.

The ability to automate everything is great. You can also do process mining and optimize costs. It can help save a lot of money in an organization. 

Depending on the business, and how you calculate the cost vs savings, the time to value varies. 

It's a complete ecosystem. It has everything you need. You can do attended or unattended bots. There's AI. There are document processes that you can do as well.

It's very easy to create any type of automation. It's the best solution so far in the market. 

We are able to implement end-to-end automation. It's important that you can automate anything with UiPath. You are not limited. You don't have to have any extra connectors. 

It has helped minimize our on-premises footprint. You can migrate to the cloud if you like. However, many companies, like banks, do not prefer the cloud. They prefer on-premises setups. 

I've used the Academy courses. I've started one and haven't finished it. My plan in the future is to utilize it more. The structure and details are great. If you are new to UiPath, it's very good. It helps effectively onboard new people. 

It helps reduce human error. 

We can free up employee time by 90%. 

If you are saving time, you are saving money, and therefore, it has helped save costs. 

Everything is working well. Of course, there can always be improvements.

I would like to see them integrate with generative AI like ChatGPT. It might make a developer's life easier. 

I've been using UiPath since 2019. However, I have not been continuously working on it.

The solution has been very stable. I'd rate stability nine out of ten. 

The solution is very easy to scale. 

I've never been in contact with technical support. 

We previously used a different solution. 

The implementation is very easy. The deployment is similar to other products. You create a file and share it with a customer and they import it. 

Through our methodologies, we define, design, deploy, and maintain. 

Pre-deployment, we need to do some testing. After that, once it's accepted, you deploy. You don't need much staff. 

There is some maintenance required for future changes in the application and any issues that may arise (like bugs). Typically, there's a business analyst and people from IT as well as someone from whatever department it's being deployed to. 

The customer deploys the solution. We take care of the design and implementation. 

I have noticed an ROI while using the solution. In general, a business analyst would do the calculations to see how much money would be saved if a robot was deployed. 

I do not deal with the licensing. 

We are UiPath partners. 

I'm not certified in UiPath, although I do have experience with it. 

I have not used the AI functionality yet.

I'd rate the solution nine out of ten. It's easy to work with UiPath. It has very good documentation.