UiPath Studio Reviews

One of the main reasons for using UiPath Studio was that we have a very decentralized IT landscape in our company. The IT teams we have are mostly busy, especially for operational tasks, because we do a lot of operational work in the finance domain. More often than not, we do not get the capacity from the tech teams to perform integrations or automate operational tasks. It was easier to establish a citizen development center of excellence where we could enable business users to perform smaller automations by themselves. With UiPath Studio, we could also do scalable automations, and with StudioX we could do citizen automations. The flexibility of being able to switch between a tech person and a business person was smoother with UiPath Studio for us based on our understanding and testimonials from a few other companies who had used it in the past. That was the reason for adopting UiPath Studio.

We utilize the drag-and-drop feature with UiPath Studio, which is very useful in simplifying automation. We were working with a few business users from a different entity in our company and did not provide them extensive training. We simply guided them to use the training material available on the UiPath portal. The videos and training certifications or courses that UiPath provides on its portal were excellent feedback we received, as the videos and courses are really useful and very simple to understand. By going through some of those materials, our business users could use the drag-and-drop feature and perform simplified automations. Without any training from our end, our business users could be enabled to do that, which was valuable feedback for us.

There are some weaknesses, though nothing on the top of my mind at the moment. From a process and OCR point of view, for example, we are currently doing a use case about e-invoicing. We feel the accuracy that the OCR provides from UiPath Studio was not as high as we had initially anticipated. We had to not go with that module that UiPath Studio offers. UiPath Studio has an a la carte mode where you can buy specific functionalities without having to buy the whole package. We decided to test out a few other tools in the market and bought a customized tool specifically for OCR purposes because UiPath Studio's accuracy was not as great. It comes more on a use case-to-use case basis. Certain use cases that we try show that certain functionalities could be improved, and there is definitely a scope for improvement. That being said, the functionalities that we bought UiPath Studio initially for work pretty well. We wanted a centralized automation hub, an Orchestrator, and maximum license utilization for the bots we were purchasing. They are basic, but at the same time, they are easy to use. The ease of use is one of the main reasons why we still favor UiPath Studio. The AI and OCR parts are something we are looking to explore more in the coming year, and that will probably give us more insights into the functionalities and their value.

At the moment, we use Oracle as our ERP. We have not had much success integrating with Oracle so far. UiPath Studio offers a lot of customized integrations for SAP, but not much for Oracle Cloud. We had to leverage our internal ERP in-house team to build integrations. We used Oracle Cloud integrations rather than UiPath Studio integrations with respect to ERP. Every conference or event that UiPath Studio organizes, when we have a chance to speak with someone from UiPath Studio, we bring up Oracle Cloud integrations. I believe that in Europe and the US, Oracle Cloud is growing in usage, so we would appreciate more effort focused there. However, with Salesforce, we used a couple of cases with customer service in our company, and we integrated with it very smoothly without any blockers.

At the moment, we have not explored AI and ML capabilities of UiPath Studio as much as we should have. We conducted a series of process discovery workshops in our company, and the use cases we received did not require AI or ML functionalities because they were core finance operations, and we did well with just the regular functionalities of UiPath Studio. We are still looking forward to finding a case where we could leverage AI and ML capabilities. We do not want to use AI functionalities just because we want to use them. It is more of a situation where we ask if it is needed, and we are still looking forward to finding a case that demands the need for AI functionalities or a nice-to-have feature. At the moment, we still have not used or explored those things of UiPath Studio.

I started using UiPath Studio way back in 2019, and I used it for a couple of years before discontinuing because I switched to another company where it was not used for a couple of years. We started using UiPath Studio again at the end of 2022, and since then, I have been using it.

We did try the recording capabilities in the initial stages with UiPath Studio, but the scope of recording is quite limited. Recording is more suited for one-time or very simple process automation, but it does not work in a scalable sense. We being a very mature company in our business model prefer automations that are scalable, something we can create once and use it across entities and other countries. With recording, that is not as easy unless the use case is straightforward and simple. Normally, we do not have many straightforward cases. We used recording once or twice at the start for some very simple automations to explore the feature, but it is not something we use for our typical developments.

So far, the support has been good. We have never had many big complaints about support with UiPath Studio. We had an implementation partner offering some support services on the side, so we do not have too much experience or too many issues that we faced with UiPath Studio support, to be very clear. The team is very responsive. Even from a sales manager point of view, the sales support is very quick and responsive. They provide us frequent reminders about license expirations, any bugs, and any upgrades we need to perform.

The implementation of UiPath Studio was very straightforward. Deployment required one to two days. We got support directly from UiPath Studio as well as an implementation partner in the initial phases to support us. We had high-level project management overview, but we had support on the ground from the implementation partners.

Three people were involved in the process of deployment for UiPath Studio. In addition to that, we also have support from implementation partners, which we still leverage every now and then to help us with developmental activities if we are running out of capacity or do not have as much bandwidth to develop certain automations.

At the moment, the licensing cost for UiPath Studio feels reasonable, but I anticipate that in the next two to three years, licensing costs will increase. I agree with the regular trends or regular opinions that companies have about UiPath Studio licensing. We still choose to have it because of the convenience and ease of use and because it is difficult to migrate to another third-party application. In general, licensing costs go up very quickly if you scale at a good pace. The rate at which we are building new automations is not that high. It is more of a project that is positive for the company, but it is not that we have a dedicated 15-member team focused solely on automations. If you have 40 automations that consume a lot of bot utilization, and you need to purchase 10 bots that need to run in parallel, the costs could very quickly escalate exponentially. As long as you plan it ahead of time and plan your bots so that they work at different times and you utilize the capacity tactically, the costs could be reasonable.

At the moment, we have not explored AI and ML capabilities of UiPath Studio as much as we should have. We conducted a series of process discovery workshops in our company, and the use cases we received did not require AI or ML functionalities because they were core finance operations, and we did well with just the regular functionalities of UiPath Studio. We are still looking forward to finding a case where we could leverage AI and ML capabilities. We do not want to use AI functionalities just because we want to use them. It is more of a situation where we ask if it is needed, and we are still looking forward to finding a case that demands the need for AI functionalities or a nice-to-have feature. At the moment, we still have not used or explored those things of UiPath Studio.

One of the positive aspects we also have is a very good marketplace in UiPath Studio. We have a lot of predefined templates available. In addition, we have support from implementation partners, which we still leverage every now and then to help us with developmental activities if we are running out of capacity or do not have as much bandwidth to develop certain automations. The fact that with UiPath Studio we can build reusable modules that we can use across automations has been specifically very useful to us as a company and team driving this project. Our overall review rating for UiPath Studio is eight out of ten.

I'm working with UiPath Studio currently. I utilize the drag-and-drop feature of UiPath Studio, but apart from that, we can customize our code. We can use Python, we can use LINQ query, we can use JavaScript. So we can customize our code up to 80% of our project. It's up to us whether we can use drag-and-drop or if there is a possibility to use LINQ query, if there is a possibility to use Python code, if there is a possibility to use JavaScript, that also can be done.

I am familiar with UiPath Studio. I have almost eight years of experience in UiPath. I'm leading the team and functioning as a supervisor here.

I have used the recording capabilities of UiPath Studio, but not extensively. It's a good feature that gives us a quick solution and after that, we can go and modify as per our requirement because we do not have to drag and drop. So it gives us a good solution, but I have not gone through much inside it, so I have not used much of the recording.

We are using AI functionality, AI, and ML capabilities in UiPath Studio because we are using Autopilot as well. So Autopilot for developer, we are using Autopilot for Test Manager, test automation. So it is helping us. But we have just started using Autopilot, and we'll be using Autopilot for test automation going forward. Because there will be a lot of test cases that have to be developed. So we'll be using Autopilot for test automation that uses our object repository to download any similar test steps that are there in the object repository. So what I can see is it is helpful. It will reduce at least 30 to 40% of our test cases.

The improvement needed is that UiPath Studio is getting upgraded every time. And then there are different dependency packages. For example, if you want to use Excel, then you have to install the Excel package. If you want to use API, then you have to download the package. Some of the recent upgraded versions, the package sometimes create problems. So that has to be tested first and then it should be available in UiPath Studio. Because everybody wants to use the latest package, but sometimes when we are using the latest package, it creates problems. It will not give the result as we wanted or it will create some problems. So we have to test the lower version of the package and then accordingly we will have to work. So sometimes that takes time.

This improvement should be implemented because persons who are not experienced, they do not have much experience. For example, if any freshers and persons with one or two years of experience want to use it, it can be time-consuming and then they will take a day or two, then they will come back to us, to the senior person, then the senior person can guide them to downgrade the package and test whether it is working or not. But even if the package is downloaded, in the description it will be mentioned that this package will support this version of Studio. But even after the written Studio version is used, it creates problems. So that has to be fixed. But it comes rarely, but sometimes it creates a problem.

I have almost eight years of experience in UiPath Studio.

UiPath Studio support is helpful because we have recently created a few cases, and we are getting responses on time. But I don't know for what reason they want to upgrade our package so they can come on the call as well. I have asked my functional head to connect with UiPath because if some organization has more than 10 plus licenses and then more than two bundles of AI unit for Document Understanding, this should be there to connect on call whenever we required. But I'm not aware of that, so my functional head will be talking because we are connected with our UiPath member who is an account manager for us. So he gets our things resolved also whenever there is some difficulty resolving some of the issues. So support-wise, it is good from UiPath.

Negative

It's not difficult to deploy UiPath Studio. It's simple.

It's not only me who deployed it all by myself because we have a team. So 100 processes, we cannot deploy by one person. But different processes are done by different team members. But across my eight years, I have worked in different organizations, so I have developed more than 60 plus automations.

I'm using UiPath Studio as a tool because this is our enterprise tool in my organization. And apart from that, we are using Tosca for Tricentis Tosca for test automation. That also we have recently acquired the license for our SAP testing. So these two tools we are using in our current organization.

I work with the on-premises version of UiPath Studio. And because we are starting to create some of the agent feature from UiPath, we have started Studio Web as well, but mostly in our organization, almost 100 processes are live. So those 100 processes from different locations across different departments, we have developed in on-premises Studio, but going forward we'll be utilizing Studio Web as well for agent building and all kinds of things.

Once the code is ready, it depends. Deployment can only be done once our code is ready. So code development depends on the use case. If the use case is complex, then the development time will be more. So once we are ready with development and testing, unit testing, deployment is a five minutes thing. We can easily deploy within five minutes.

We have started integration with third-party tools such as SAP in our organization, which is divided into two parts. Tricentis Tosca will be used for SAP and then for other applications such as Coupa or our DevOps team creates multiple applications for our organization. So those we have started doing testing by UiPath Studio itself. I have done the setup because we use ADO as an ALM tool. So I have integrated Test Manager to ADO to sync in the test case, test set, and the requirement created in ADO to Test Manager. And then test result, defect from Test Manager to ADO. So earlier it was directly getting done through Test Manager only, but now Planview has come in between. And it is simple, but earlier logs and assertions used to sync in from Test Manager to ADO, but now it is not there. So the feature that has been removed. Because people want to see. Let's suppose I am running the test case in Test Manager and earlier all the logs and assertions, such as a screenshot, it was getting reflected in ADO automatically, but that is not there. So I think if that is coming to the features, then that will be helpful for us. Because accessing Test Manager requires a license. But let's suppose for one test case, there are multiple people who want to see the result. So we cannot give access and license to everybody. So if assertion and logs are getting reflected in ADO from Test Manager automatically, then that will help the team.

It's quite reasonable in terms of pricing. But as I said, test case management is done through a team. So we can't have those many licenses and assign them to everybody. Only one admin will have a license, developer named-user license, that gives all the access to Test Manager. So compared to other tools, UiPath Studio licensing cost is low. But if the assertions and logs syncing from Test Manager to ADO is there, then that will be more helpful and then it will create a good impression. Because I have seen Tricentis also has one management tool, called QTest. And they are also integrating ALM tools such as Jenkins and ADO. So compared to Tricentis, integration between ALM tools is very much easier in UiPath Studio. But I believe assertion and all, that is there in Tricentis, but in UiPath Studio we do not have. So the only thing I feel is assertion and logs should be synced from Test Manager to ADO. So everybody can go there only and then they can see it. I would rate this product overall as a 9.

I am using UiPath Studio for automation.

Drag and drop simplifies automation in my organization and definitely helps. The extensive library and pre-built activities help speed up the automation process.

What I like most about the product are its best features. UiPath Studio is good for automating business processes and repetitive tasks within my company. We have multiple features added in UiPath Studio, such as Agentic AI, LLM, and Maestro. Multiple features have been added, including document understanding, which are all very useful.

Before Agentic or document understanding, it was definitely complicated, and you cannot be 100 percent sure if you can automate a process or not. For example, handling an invoice and extracting a signature was a challenge. However, I am now able to extract the signature through document understanding. As of now, I can definitely say I am not facing any challenges or difficulties, and we are satisfied with the current features in UiPath Studio. However, small improvements can always be made because in each and every tool, something will be there.

There are features or functionalities I would like to see in UiPath Studio. For example, I am currently using version 24, not the latest version. In the current version, there could already be improvements. For new users, finding the properties in UiPath Studio could be difficult without guidance. As I understand it, this issue is already fixed, and new users can now easily identify properties and how to change them.

I have been using the product overall for more than six years.

UiPath technical support is responsive and helpful. Whenever my company and my UK client need UiPath support, they are always available when we expect them. However, support is dependent on business hours only.

There are no difficulties with deployment of UiPath Studio. It is quite easy for me to deploy. It is a simple step that needs to be performed.

I do not need any assistance from consultants or third parties to deploy UiPath Studio. It can be done in-house. In 2020, I discussed with the UiPath team and started the installation process. Now we know the process very well, and without any help or support, our team is capable of installing Studio.

For the process of deployment, two people will be enough. One person will handle the installation, and the second person will validate the orchestrator if something is wrong or for validation purposes.

I am satisfied with the current price for the product and overall licensing costs. Whatever price is given is provided by the client. We can definitely suggest the amount, and if the client is ready to pay and if we can create a good product for them, then obviously it will be acceptable.

Using the recording capabilities of the product depends on the situation. If it is a Citrix application, then there is no option. We have the option, but if you try to record the steps, it will help for automation. I have already used recording, but not now. Before three to four years ago, I used it. It depends on whether you are a new developer, then obviously you will use recording, and if you are an expert, then it will not be required. We have multiple options in UiPath Studio.

Regarding integration support with applications like SAP and Salesforce, for SAP, we need to change or implement some settings, such as client and server settings. After changing those settings, we can start our automation. For other applications, in the current version of UiPath Studio, you can easily integrate with third-party applications without any issues or complicated settings.

The AI and ML capabilities of UiPath Studio impact my workflow depending on the context. I have started working with the LLM features, and I am a self-learner. In my system, I am doing small POCs and creating agents to see how the bot will begin the automation. That part is still something I am learning. However, whatever I have learned about UiPath Studio's features is very good. You can create agents in UiPath Studio and interact with your implemented processes and third-party applications easily without intervention. For example, if something requires approval, waiting for my manager to approve is also a feature available in the new Agentic AI.

The primary use cases include multiple applications related to insurance, finance, ticketing, IT, and HR. I have worked on multiple use cases across these domains.

The ticketing system is useful as it helps with manual assignment, closing, and creating tickets. All of this work is now done by a bot, which will save a lot of time and resources. There are multiple use cases, and there are a lot of benefits by using UiPath Studio automation.

The drag and drop feature is very beneficial as it is very user-friendly. Anyone can work on UiPath Studio with maybe less programming knowledge, and it will also be helpful.

Regarding the recording capabilities of UiPath Studio, I usually do not use recording, but it will be useful for those with a non-programming background. They want to record and perform some action, but since I am from a programming background, I am using the activities and not recording directly.

The integration support with applications such as SAP and Salesforce may involve multiple components to integrate one system to another. There may be direct HTTP requests, APIs, and services and connectors. There are multiple things we can use depending upon the requirement, and through a database as well.

The AI and ML capabilities of UiPath Studio have impacted my customers' workflow in a fantastic manner. I have not used them much, but they are very fantastic. In a few of the use cases, they bring a lot of benefits with decision-making.

The benefits I have seen from using UiPath Studio are numerous. I am providing a lot to my customers.

To improve UiPath Studio means it is already improved at the current state of the version. People have to explore more because there are a lot of new features coming up. The Agentic feature is helpful, and AI Center has multiple things that have come out. I think we have to explore all these features as it will be beneficial.

On the improving side, concerning costing, I am not sure because the cost of the new product is very high. People are not able to explore more on that part. If they were to reduce it, I could suggest it to the client. That is one suggestion to UiPath: if they could reduce some costing from their product side, particularly the LLM model and agent response, it would help.

In the future, I would like to see additional features where most things are already present. Maybe there are some webhook features. As of now, there are a lot of connectors directly inbuilt. A few of the things that are not compatible may require some digging into the studio side to add that feature. I am currently creating some Agentic features from the web. However, sometimes I am struggling in the studio figuring out how to add that feature. If they could come up with some easy drag and drop capabilities with the Agentic feature as well, that would help a lot.

I have been familiar with UiPath Studio for five to six years.

I would rate their technical support a seven because whenever I face any problem, they help me through email. I have to raise the ticket, and I got the response. Sometimes it is delayed, but they definitely respond back with any ticket.

Positive

There are a lot of great things in UiPath Studio. Whatever is required for the development is there. I do not think I face any difficulty during the development of any use case from UiPath Studio's side. I am satisfied with their activities and libraries.

Overall, I would rate UiPath Studio a nine because as per my understanding, it is awesome.

I would definitely recommend UiPath Studio to others because UiPath is the market leader and I have been working with it for the last eight to ten years. I have given UiPath Studio an overall rating of nine out of ten.

RPA is something which we deployed to address some of our documentation requirements or document management related requirements. That's what we are using it for.

Right now we have it deployed, and it is dealing with about 50% of our document volume. The rest of it is done through another tool that we have developed.

We do have some RPA solutions deployed. They are all UiPath Studio-based.

I've been in the service industry for almost 25 years.

Any RPA is never straightforward. It needs a lot of maintenance and it keeps requiring updates. There is a lot of maintenance required. Besides, the cost itself is not where it used to be six years back.

I don't think my feedback is going to be any different from what you've been hearing. It is constant maintenance. It keeps breaking. You need to continue to evolve it and maintain it. The cost is another element which needs to improve because it's increasing and it is becoming prohibitive in some use cases. At the end of the day, you put in so much effort and the licensing and all those things are becoming expensive now.

We are not seeing improved ROI because the bigger chunks of use cases we have already addressed. When we take it down to the medium size, the cost of development and deployment is something which is prohibitive and it doesn't make a good financial business case.

I think it's been about five or six years.

It is constant maintenance. It keeps breaking.

Right now we have it deployed and it is dealing with about 50% of our document volume. The rest of it is done through another tool that we have developed.

I haven't heard anything about support being an issue ever. There is a need, but I've never heard that there is a challenge with support.

Any deployment will take probably six to nine months.

We do have a dedicated bunch of people who do this on an ongoing basis. Some work in maintenance, some in development. The overall team size is somewhere around 12 or 13 people.

We are not seeing it because the bigger chunks of use cases we have already addressed. When we take it down to the medium size, the cost of development and deployment is something which is prohibitive and it doesn't make a good financial business case.

The cost is another element which needs to improve because it's increasing and it is becoming prohibitive in some use cases. At the end of the day, you put in so much effort and the licensing and all those things are becoming expensive now.

We are not seeing improved ROI because the bigger chunks of use cases we have already addressed. When we take it down to the medium size, the cost of development and deployment is something which is prohibitive and it doesn't make a good financial business case.

Probably we'll look for another solution, maybe in the next couple of years to see whether we can consolidate everything on one platform.

A costly and possibly more efficient solution which could be self-learning or could be easy to maintain or is not so heavy on development resources would be ideal.

More internally, I would say it's not related to UiPath Studio, but it's something more internal than just UiPath Studio.

Right now, we have some deployed in some areas not related to this particular document management side of the world. It's more on the data side, but that is something which we'll probably be exploring next year to see whether we can look at an AI-based solution or maybe a little more robust solution than what we currently have.

We typically integrate with our own platforms and our own tools. There is no issue. The way our own platforms or our own systems are structured, they're pretty diverse. There is a little bit of pain to do that, but we live with that.

It's all cloud. It's AWS.

I gave this review a rating of 7 out of 10.