What needs improvement with UiPath?

We use intelligent automation for things like document processing. There is a validation center where the ML model extracts some values, and we can validate if it's correct. That aspect could be improved a little. The percentage of values extracted without validation could be increased. It's currently an attended process, but they should give you the option of making it unattended.

The community version of UiPath has a limited feature set, which can make it challenging for users to fully explore its capabilities without purchasing the enterprise version. Offering a trial period for all features could provide a more comprehensive evaluation experience for potential users.

It should have better integration with Microsoft applications such as Excel, SharePoint, Outlook, etc. Power Automate is better for communicating with Microsoft Office applications. With UiPath, we have some difficulty communicating with the Microsoft Office applications. This is the only weakness that I have come across.

Computational text recognition has room for improvement as it is not 100 percent accurate.

One area that could be improved is how we access the UiPath Academy courses. While it's fantastic that each course provides an assignment, it would be more convenient if we could view the solutions directly within the platform rather than downloading them each time and opening them in our individual UiPath Studio applications. Ideally, there would be an interface integrated into the course platform itself where we could access and review the solutions directly within the browser. This would save time and streamline the learning process. In Automation Anywhere, each line of code is displayed in a list view, offering clearer visibility. In contrast, UiPath condenses everything into a boxed view or flowchart, which can become cumbersome when dealing with numerous intricate conditions. Pinpointing specific segments for modification within such a condensed format proves challenging. Therefore, UiPath's UI design could benefit from an overhaul to enhance clarity and ease of navigation, especially for managing complex workflows.

I'd like to see the accuracy improved. Sometimes the development works fine. Other times, it requires some small changes in the development. They could add enhancements in AI technology that could be helpful for everyday developers.

We sometimes use the AI functionality mainly for document scanning but at the time it was poor and had room for improvement. The operation costs have room for improvement.

While doing web automation, I am facing a selector issue. In the web portal, we need to capture a screen element. For capturing the screen element, when I run the job the next time, it fails because the limit is not recognized. It is very difficult to make the selector stable. It is not easy.

UiPath should expand its coding options and reduce its dependency on third-party resources. There should also be more flexible licenses for smaller businesses. It's hard for small companies to estimate the cost of adding users in their final budgets. UiPath could also improve error handling and capture a little more information about the execution of your processes.

For UiPath Orchestrator and Studio, if I want to watch the performance of my machines at a specific time or time range, there is no option for that. There are options for one day or week, but there is no option to specify a date such as from Nov 1 to Nov 3. This option should be there for queues and monitoring.

If we want to learn something new about UiPath, we sometimes cannot learn it directly from the UiPath Academy. We have to go and search on the web. It takes a few searches to find the solution. We do find it, but it takes time. UiPath should give the solution in one area.

UiPath is expensive, and its cost could be reduced to make it more accessible to small and medium-sized businesses that could benefit from it. The orchestrator and licensing cost should be flexible instead of hard-coded licensing. UiPath is limited to one application at a time and cannot process two applications simultaneously. This functionality could be improved to support dual browsing, making it more efficient.

Assessing an AI center's role in orchestrating various elements of AI capabilities is quite constrained.

There are instances when the introduction of new features or concepts can be a bit overwhelming for users.

In Action Center, saving progress in data validation, specifically for table content, is currently not available. There should be more clarity around the feedback loop along with the auto-update feature when you deploy machine learning packages. They should give some rule-based options so that if the confidence is returned higher than the previous model trained, then it would auto-deploy. If it is less, then it should send you an email rather than auto-deploy. With task assignment, if there was a round-robin feature within the bucket to automatically assign it to a certain group of people, that would be helpful. There should be the ability to add custom fields to validation tasks because there is a lot of potential for it. It would be helpful when somebody needs to identify a scenario. For example, we have a customer who is processing rate sheets for trucking, and sometimes, depending on their customer, they have an all-in rate versus an adding fuel mileage rate. If they are able to specify that, even if it does not say it on the rate sheet, it would allow them to process more documents successfully. We use UiPath's AI Center, but some clarity is missing around when to use AI Center versus when to use the Document Understanding module within Orchestrator. We are trying to figure out the benefit of one versus the other. We have also seen that the out-of-the-box models that we train versus a custom model that we train with the same data end up with the same output result at the end. We are trying to see where these out-of-the-box models are providing value if we are going to take the time to train them.

Simplification and adaptability for smaller businesses would be a welcome enhancement.

The hardest part is popularizing UiPath among our employees.

The support team could be more responsive and helpful.

There's room for enhancement, particularly in the support department and in the area of reporting, to provide a more robust product for gathering insights.

Integrating with tools such as Asana or other service and project management platforms would be a valuable enhancement.

There is room for improvement in browser automation, particularly regarding access and success rates. Success and failure recognition are key areas to focus on.

Improving financial and recording operations through the use of charts would be advantageous.

The concept of process analysis would be helpful. Having a tool that can assess the entire workflow of an automation created by someone would be highly beneficial. This tool could identify areas where enhancements or improvements are feasible, simplifying the process of refining and optimizing automation workflows. In the case of case number categorization, we encountered an issue. While creating the automation, the system was designed to detect and categorize cases into various specified categories.

There are several areas where I see room for improvement in the tool. One of these areas would be a more solutions-oriented pricing structure. This is because the platform requires a multitude of building blocks even for the simplest use cases and when dealing with newer clients, this can be challenging. One area where I'd appreciate additional or new features is in the realm of insights.

Updating the tool across multiple virtual machines can be time-consuming and somewhat cumbersome. It would be more convenient if this process could be automated.

The UiPath Academy Orchestrator training needs to be updated to reflect the recent changes.

Its pricing changed again this year. I do not know why it just went up, but I do not like that. This is something that I would like them to improve for sure. It would be nice to have the possibility to change the values in the middle of the debug. For example, I am debugging a process, and I write at a place. The value of that level is one, but I want to see the results of it if I change it to two. It does not seem possible in UiPath. It is possible in other software, but in UiPath, it is not yet possible.

An area for improvement I saw in UiPath is API integration, particularly with Microsoft. If you compare my experience with Power Automate in terms of integration, it is seamless, and you don't have to create trust with other applications. Integration via Power Automate is easy, more of dragging and dropping and then starting, which is still not the case with UiPath, so that should be improved.

Currently, we have a lot of data extraction models in UiPath. Still, sometimes the data extraction model needs improvement. For example, extracting the data from various kinds of complex documents. Still, compared to the other automation tools, this works way better. The solution needs to offer more integrations.

We have two versions of UiPath: on-premise and cloud. With the on-premise version, we have good control and flexibility. However, the cloud version is less flexible and we often receive errors. We would like UiPath to make some enhancements to the cloud version to provide more flexibility for OCRs, email models, and AI centers. This would allow us to provide better service to our customers.

I would like to see improved support and cost management for advanced certification. The cost is too high for many people to afford.

UiPath's built-in integration with Python scripts could be more robust so that I do not have to depend on another technology and I can do everything on one platform. Each program you write on UiPath contributes to bot consumption and utilization. As you add more bots, your costs will increase for more actions. Python is open-source, so it is totally free. Depending on our automation needs, we go back and forth between these two technologies. Better integration between these two tools will help organizations cover all areas of automation without more cost-effectively.

UiPath can improve its AI and optical character recognition or OCR. Currently, reading digital images or PDF documents by UiPath is a huge challenge. I request UiPath to improve the OCR recognition.

Sometimes, the company's processes are very complex, and it's very hard to implement UiPath. It also makes mistakes. Understanding your systems by yourself and implementing UiPath into your company processes is the hardest part. This could be improved so that the companies can easily implement the solution.

I see UiPath as a practical product that is trying to achieve end-to-end automation or end-to-end processing. They are playing in this space and bringing their AI connectivity or components into their product. However, I think the only downside is that, as we have seen recently, for some of the processes we have automated, we have documentation on the technical elements that we have automated, but people have forgotten the business rules. UiPath has a task capture product or a process mining product but it could be improved by capturing the business process and then how the automation that we have developed feeds into that overall business process, and making that available to the business so that they know what the business processes are. UiPath does not have a delivery product. For example, when we go into Microsoft DevOps, UiPath does not do that. Once we have identified the process and have coded it in UiPath, there is nothing to tell us about how we deliver that process, and who is assigned to a task to build the components. There is no project management or DevOps delivery pipeline model inside UiPath, so we cannot manage the development.

I want UiPath Data Service to be expanded. It must include many more features as an online database. Many online databases like QuickBase and Force.com are 100 times better than UiPath Data Service. Not sure why UiPath is not adding such features to Data Service. The product does not provide features for chatbot development. It is one of the reasons why people do not use UiPath because they have to use a different tool for chatbot development. Competitors like Microsoft have all process automation capabilities in their Power Platform. They have RPA, attended bots, unattended bots, application development, databases, and chatbots. UiPath has not gotten into chatbots for several years. They are doing many things except chatbots. I express the need for chatbots in every insider event I attend. UiPath’s team says it will take it to the product management group. But nothing happens after that. I want a product for chatbot development from UiPath without having to purchase licenses from a third-party company. The documentation needs a lot of work. The documentation is "boring". They just mention a feature and add one line about what it does. I wish the documentation had examples. The document should be associated with a video or sample code. The documentation is too minimal. People give many sample codes and links to their YouTube videos in the forum. The uipath forum is much richer than the documentation.

Saudi has two calendars. UiPath does not support the Hijri date. They should add it in future releases. We also face regular issues while parsing from right to left and left to right. The Arabic language is not related to the platform. We have Arabic scripts which are sometimes difficult to understand. Also, the license is complicated. The add-ons are not well documented. When we offer and pitch to the customer, sometimes we get confused about which one to offer based on the third-party tools. The solution must focus on microservices and web-based platform building. It would be fantastic if they could produce web applications connected automatically to UiPath. OutSystems is a low-code platform for building web-based and mobile applications. If such features are available in UiPath, it will eliminate the need to integrate with different applications. We can directly build applications using UiPath.

UiPath should be able to adapt to other operating systems like Linux or macOS. The tool must reduce the activity required for workflow design. It should be made similar to Visual Studio. It should provide a better way to analyze the recursion functions.

Unfortunately, I used to be a lover of their Slack channel and people don't seem so responsive there anymore. Unfortunately, I've gotten away from using their Slack channel. That would have been a really good way for me to get some help from the community, yet I don't find it helpful anymore. They're working on integrating their version of a chat. They're starting with Studio Xpress or StudioWeb. I don't use StudioWeb and I don't use StudioX, however, I would love to have that type of feature in Studio. I could use it across the board, not just in Studio, but in Assist. Their error messaging could use some improvement. More times than not an error that you receive is accurate or not clear. In terms of missing features, I can't think of any. They are always ten steps ahead.

One functionality we would like to see is OCR.

UiPath helps with digital transformation at the outset, but I focus on the amount of runtime support needed for managing bots. If a bot is going to save four to six onshore resources, at least one offshore resource is needed to support it. That is one area where UiPath, Automation Anywhere, and every automation software has to focus. A lot of bots are highly sensitive. Even the slightest change in screen behavior or a small change in the process and, many times, they are not intelligent enough to run on their own. That means there is a high level of dependence on the support team. Automation software providers need to improve on this. Also, UiPath could bring in a type of low-code or no-code automation so that it can be used by the masses instead of only by technically proficient people to develop solutions. Low-code or no-code automations would be really helpful. In addition, for intelligent automation to become really robust, a lot of features need to be added, and the accuracy of the model has to be improved. Right now, if I am going to implement any UiPath or AI solution, in the beginning, it will only be 30 to 40 percent accurate. It doesn't get to 70 to 80 percent. These are the types of things that need to be improved in UiPath.

I would like to see the setup improved. First we install it, then we log in with Orchestrator, and then we have to log in to the UiPath website. I would like all this to be merged into one setup.

We cannot utilize the UiPath community edition license to operate any bots that we have created using that version in an enterprise environment. This is because we are obligated to employ UiPath Studio, which necessitates a distinct license for professional use.

The UiPath Community does not provide version control for the community edition. Let's say I'm currently using a specific version, and then it automatically upgrades the community version to the latest version without the user having the option to decide whether to update or not. Consequently, we cannot use the older versions in the UiPath community edition. I encountered some issues with my local machine. I created one of the bots using a different version from the community variation, there were problems with compatibility between different versions in UiPath. While those issues used to exist, currently, it has been a long time since I last modified any of the workflows and migrated between servers and my local machine. I'm not entirely certain at the moment, but previously, there were instances where a particular activity in one version would not work in another version and would result in failure. Additionally, sometimes the select task would not identify the select areas in the actual application, even though it worked on the validators. These scenarios are rare but they do occur.

UiPath's price has room for improvement.

The document understanding has room for improvement.

On the investment side, it is a huge investment, especially with the current situation in Sri Lanka. If they can reduce the price or provide affordable packages, it will be very helpful. On the development side, there are already so many new capabilities. They are also adding more AI capabilities. I have seen some of the users using AI tools, but I have not worked on them much.

I would like to have the ability to make changes at different stages of the development process without having to start from the beginning each time. Automating with UiPath is not as easy as it appears in the advertisements.

UiPath is not easy to work with, as a vendor, from a partner perspective. They are difficult to deal with.

There can be technical issues, but it's rarely about a server quitting. They are more like connectivity, platform, and software version issues, but there are no issues with UiPath performance. I would also like to see UiPath assist clients in scaling up their usage of the application because most of our clients had trouble expanding their usage into other departments. It was hard for them to calculate the exact value they were getting. Some of our clients were flying blind. Some of our clients hadn't really seen enormous impact from implementing and using automation yet. They had just started, and they saw the value in it, but it was hard for them to expand or add more value to automations with UiPath.

It would be beneficial to have the capability to track defects during the regression testing of applications.

Although AI functionality has improved in its ability to automate more complex or involved processes in the past five years, there is still ample room for further improvement. The APIs are predominantly on-premises-focused, and there should be greater availability of cloud-based APIs. There are workflows in which we use AI to take screenshots to assist us in making decisions, and these workflows need improvement.

AI machine learning has room for improvement. We use Google and Microsoft services. In some ways, Microsoft is more straightforward when we need to train a model compared to UiPath. There comes a point when we integrate UiPath with Microsoft Cognitive Services. For instance, we will also pay for these Microsoft Cognitive Services, not only for the UiPath license. It has an additional cost. However, in terms of usability, my impression is that Microsoft Cognitive Services are faster to configure and provide quicker results than UiPath document understanding, for example.

We would like to use several modules of UiPath, but they are very costly. All the additional features that we need are there, but they are in the modules that we have not bought. Its stability could have been better.

On the Orchestrator side, I would like to see more controls and conditions for RPA managers. If they advanced in those areas, it would help.

For some of the cognitive features we have to learn the integration side. Other than that, everything is fine.

We have used UiPath Academy courses for process mining. For RPA, we have some KPIs for developers to complete their education. In UiPath Academy courses, they have an option for the Turkish language for videos, but they are always in English. They should correct that. UiPath should integrate more machine learning and have more machine learning processes. In their development system, they have some machine learning tools, but they should increase them. With robots and structured data, in my opinion, we can use machine learning. The robots should also use machine learning to create some AI models. Its price should be reduced.

The artificial intelligence and machine learning features are good, but there is some room for improvement.

It isn't clear how to use UiPath to implement some use cases like chatbots, so we need to spend a lot of time searching for documentation on the web. To discover how to do these automations, you need to read and figure things out through trial and error.

The data team support that provides the UI and the chat services has room for improvement.

In the UiPath Community, a few questions get resolved and a few questions remain unresolved. UiPath has a big user community, but it needs to grow more. For example, during development, we might face some hurdles or hiccups while doing some of the tasks that we don't do on a daily basis, such as executing some API calls and getting some data. We faced some issues related to that, but when we searched for or asked about such issues in the UiPath Community, out of 10 questions, five to six questions remained unanswered. We had to resolve them on our own. So, UiPath needs to improve its community. They can offer some kind of reward for answering the questions asked in the community. It would be helpful if UiPath could provide developers to help us with the on-premises setup. Without that, we have to figure out how we do the setup. Its cost could also be better. We need to have a license for every robot, and it isn't possible for us to be able to run UiPath in our on-premises environment based on our usage. Even if we need to run a robot for an hour, we need to get a license for one year.

The user interface needs a little bit of improvement because it looks a little cheap due to being a very old tool. Otherwise, it works well. I would also like to see the ability for applications to work offline. Currently, they only work when online. If that is possible, that should be included in a future release.

Sometimes, UiPath becomes a little laggy when we move from one page to another.

The interactive selection could be more accurate. The customer support could be faster.

Handling unstructured data is challenging because UiPath works best with structured data. It could also be better at handling complex tasks. UiPath doesn't work as expected when automating tasks that require a high degree of decision-making.

UiPath can probably work on improving the AI features. We tried UiPath's AI functionality in our automation program. We did some research on that, but right now, nothing is in production. When we did some research, we weren't getting the expected results. We weren't completely satisfied with the results, so we put it aside. It could be a drawback on our side in terms of learning the tool. In terms of additional features, UiPath already has a plethora of options. All our needs are fulfilled by the features that are currently available.

It sometimes lags when internet connectivity is poor. It depends on the location. Otherwise, it is the most fantastic tool ever.

The main disadvantage that I have identified in the Document Understanding is in table extraction. If the table size is large and goes to the next page, we are unable to extract it with Document Understanding. I hear that there is a solution for that but I have to find it. There are other extraction features that Document Understanding doesn't have and clients go for ABBYY Vantage or Google document AI and it becomes expensive for them because they have to purchase a UiPath license and the other solution's license. With the competition in the market, they have to improve. They can't settle and say, "We are at the top." They have to improve invoice processing, that is the most important thing, and that's where Document Understanding comes in. We need to get to the point where a customer does not look at any other OCR engines. They have to improve Document Understanding for invoice processing.

We have used it with Windows and it has been perfect. But recently, we tried it with Linux and we faced some issues regarding this automation. The auto-recording didn't happen as much as in other operating systems. They need to add more user-friendly automation and templates for that. They don't have many templates for other operating systems.

For small use cases, it would be great to have independent runner licenses with costs that are comparable to those of Power Automate. Then, UiPath would be a better alternative. The AI functionality was not that effective in complex scenarios when I used it some time ago. I would like to see a universal recorder feature added so that we can record Excel macros. You could then click a button to record the screen, and then all the actions across applications would be recorded. This functionality is available already in Automation Anywhere, but the last time I checked, it was not available in UiPath.

The reporting part of Orchestrator could be improved. For example, UiPath could automatically email us if there are errors. Adding this feature would help us.

The dashboard view could be more visually appealing. Dashboards in any software should stand out with colors, numbers, and other things, but in UiPath, the dashboard is not that visually appealing. The UiPath team could make it more visually appealing for us to get more insights. Another improvement area is related to product updates. Earlier, we used to get monthly updates about the product, but that has stopped now. If they could bring that back, it'll be very good. We have recently tried the AI functionality. There is a lot of learning that we need to do with regard to AI. It's good, but it's not as smooth as Orchestrator or Studio. The AI aspect of the product could be better. We're currently working on allowing the AI to automatically detect areas where automation can be brought in and efficiency can be improved. That needs some more refinement. It's currently not straightforward. Sometimes, it just repeats whatever it said previously, so nothing new comes out of it. The AI aspect of the product can be much more refined. Apart from that, I don't have anything else. It's a well-thought-out and complete product. It's very easy to use and easy to understand.

A task capture feature enables you to capture the workflow from a process and record it. This feature isn't as specific as I would like. It should be able to capture every detail. The same goes for process mining when it comes to system loads. It's already the best, but I think it could be better. I need all details of a log file from every software and ERP to discover the pain points and bottlenecks. It usually understands where the most automation value is delivered but could generate more valuable information. Sometimes it's the same data from a different ERP, but it doesn't generate the same insight from it 100 percent. There's a slight difference, whereas they are supposed to be practically the same. I also think the UiPath community needs more attention in terms of how they engage with the community and what they recommend. I find that they hardly engage with the community compared to others. To be clear, I think they are doing well, but they could do better at engaging with the community and encouraging community members to engage with one another. I feel like it's not the most active community with the most active management. At the same time, there's also much information in the community, and they're always sharing information with us. Still, I think UiPath could achieve a better experience by putting a little more effort into the forums.

Their licensing is poorly constructed. It's too complicated and not well thought out. They also outsourced their support model, which sadly has become less friendly and more automated. It's very much in the early days, but another area they can continue to look at is bots building robots—the ability to take a task capture and turn that into an automation. There are always concerns over that: Who's going to police the police?

Our solution is on-premises so we are unable to utilize phone apps.

Most of our automations have been without a user interface and we need the ability to interact with users directly. That should be coming in the next release for us.

Initial deployment is very complex and some integrators need better training.

While it is the best tool ever, we decided that the user interaction might not actually be the greatest thing ever.

I have been working on UiPath Apps for the last six months, and there are a few things to improve. The tables are not working properly. There are issues with the table display and the filter function in the tables. There is also an alignment issue. You can't edit the alignment of buttons. There is also a lack of tutorials. They have a lot more functions, but there aren't enough tutorials to know how to use all the functions. They have free training in UiPath Academy, which is good, but the way of training is not impressive. They're using the textual format. They are providing lots of documents to read. It would be more effective if they were in video format. It takes more time to read and understand the content in text format.

What I'd like to see is more tutorial videos on YouTube. Maybe they could have a YouTube channel, and the community could empower more content creators to make how-to videos. When clients call us with issues, we wouldn't have to explain. If a client using Azure has an issue, we assign an engineer. Let's say you still have a problem after the engineer has consulted with you and referred you to the official documentation. It would be helpful if there were a content creator on YouTube to explain the problem in an accessible way.

The developer studio could be improved. There have been glitches, but it improved from year to year.

I faced a problem when a new version of UiPath Studio didn't work with an older version of the packages that were part of our project. The problem is that when I have to change something just a bit, I actually have to rebuild the automation with new versions of these libraries. There is no backward compatibility. This question was addressed to an engineer from UiPath in the Community but I haven't gotten an answer. This is quite a hard question. So, I just create new automations with new approaches, which takes some time.

The product could be made a little less glitchy. Specifically, when too many users are working at the same time, it hangs a little bit here and there. In a future release, I would like to see drag-and-drop functionality in the robot creation process within Orchestrator. As of now, it is not available there. It would be helpful because from there, it is easy to create a process flow. Instead of switching between multiple menus and multiple tabs, we can do it from the Orchestrator or the main menu.

UiPath's interface and user experience could be improved. The name is UiPath, but their UI is not that great. It's outdated. It seems like a 2014 or 2015 software. They should look at other products on the market. Another thing is that UiPath lacks online training resources. Maybe they can start their own YouTube channel. You have to rely on the documentation to learn. There are some resources, but they aren't available on the official site.

The pricing could be more friendly.

It can be improved in terms of platform integration. It is platform-independent, but it should be easy to integrate with different platforms, such as Windows, Linux, Cloud, etc. If I am using AWS for my server response, I should be able to integrate that into UiPath. If I can get some manuals along with the product, it will be good to see all the features that are available in it.

When I started working with UiPath, there were no activities for SAP, but in the version that I'm using right now, there are SAP activities or SAP modules. Previously, I had to code everything from user login to user logout, but now, all the activities are available. I just have to drag and drop and give the username and password. I don't have to do it from scratch. It would be great if they can include activities for all of the most common CRMs and ERPs. They can integrate it with different activities for the most common systems.

UiPath is adding new features every month, and most things are disseminated through the community, so users can give feedback. A few months back, I recommended that UiPath adopt an actions platform for downloading and exporting documents for two or three extensions. This is not enough. We're using more extensions consistently, and they change within one or two hours, but the details are set within the application. It would be better if we could customize Orchestrator more. As enterprise users, we need more flexibility to customize and filter fields so we can monitor everything.

Sometimes the automation task doesn't work so well. When we have to capture some text from our invoices and from our notes and do some manual work, sometimes the tool doesn't extract the data in a precise way. This happens in cases where we have some big data or some large amounts of text that we need to convert. Sometimes the data extraction or patching of the data from other sources takes time. This is a challenge that we have faced. Sometimes there are bots, which are not responding properly. We have to reconfigure them accordingly. Otherwise, as compared to the other software solutions like Blue Prism, Automation Anywhere, et cetera, UiPath works well. The bots are not responding according to our requirement center process. They were not given the right accurate address and we had to monitor and then manually configure the bots to the requirements. If we ran the bots for any mathematical calculations, occasionally, our results were not as expected. We have to check the results. Higher internet bandwidth is required since it is a cloud-based system.

I like most of the UiPath tools, but the UiPath Academy, in particular, wasn't my favorite part. It didn't have enough onboarding guidance when I started. The learning curve for the courses in the Academy was very difficult in the beginning. I had to turn to Google and YouTube to learn from other people, experts, and the community. The community was friendly, but the academy wasn't that helpful for me. I think it needs to improve on the information it provides to make it easier for beginners to learn, to help decrease the learning curve. Also, the user interface needs to be more customizable, and the debugging tool doesn't work well enough. It needs some improvements.

A weakness with Academy is that, with the current updates that they have, the newer updates, the courses are not up to speed. Nowadays, Academy does not feel that intuitive and does not give sufficient information about the product to the customer. In our current use cases, we do not need much user interaction. One shortcoming with UiPath Apps is that it cannot directly integrate with the orchestrator platform itself. For example, if we need to fetch any assets, values, or cue data from the orchestrator itself, it's basically a web platform. Even if we develop apps and want to do something based on that data, they do not have direct integration with the orchestrator. We need a separate bot, which will then interact with the orchestrator and then pass it back. If we need ten to fifteen users who might simultaneously use apps, and we want to run a process for each of these users, then we might need fifteen licenses to do that. That is something that has been holding us back from using it, as it does not have direct orchestrator access. We need a separate bot to get the data to perform some actions. Scaling and licensing need major improvement. I know that they have released something called Serverless Cloud Robots, where the bot machines do not need infrastructure. However, we do not generally want to run the bots or the data in the UiPath cloud as well. There are some hiccups that do happen when we run bots on another machine. That said, it might be a good feature and we can scale up and scale down more effectively.

When it comes to REFramework, we need more training videos and tutorial documents for beginners. And while there are a lot of videos to learn about basic activities in UiPath, we need more documents and key points on how to connect third-party connectors. That would be very helpful for beginners and for quick implementation.

Monitoring and statistics need improvement. It's quite hard to export if you want a long, clear report. It's quite hard to do that based on the style and functionality. You have to feed in your own functionality to do this.

One of our clients is using the UiPath Apps feature, and although it is easy to use, they are having some issues with it. For example, when they deploy an update, it is pushed to the cloud and then it will break an hour later. There have been two or three such issues and ultimately, they result in a high priority ticket to fix the problem.

I don't know if I was doing something wrong, and I did get assistance from the UiPath guys on this, but sometimes UiPath wasn't able to find an element on the screen. But that's what UiPath is for, and we wanted to make sure that our workflows were working correctly. Sometimes it was able to find an element and sometimes it was not. UiPath support did give us a solution, but it was not helpful enough.

UiPath updates its software every year. The problem is the support for the old code. For example, right now I'm using the 2021 10.3 version. If I have developed a code three years back and I want to update the packages, it won't work as expected. They do not follow up with support for the old version. Therefore, a person has to exclusively work again with the old robot to make it compatible with the new version.

* RPA AI capabilities - UiPath is leading in this area. * UiPath should focus more on recommendations of process automation based on ERP Applications like Oracle, SAP etc. They should also provide a list of possible RPA cases as per departments, processes and based on various industry domains. * More on RPA Governance features to be provided out of the box. * RPA Capabilities with IVR Channels to address voice commands will be a game changer for Customer call center cases.

These are my best 3 upgrades for the item:

Improved Dashboards from Orchestrator - we need simple to make SQL questions, preferably not using outsider programming, this ought to permit following of cases, memorable patterns, time to measure and so on I know there are some essential dashboards yet they are not incredible. Kibana is fine for logging however I'm more inspired by the Database - is it conceivable to point Kibana at the DB, if so that could be a pleasant arrangement as Kibana is an exceptionally beautiful apparatus .

Orchestrator should come as an installer bundle. The entirety of the setup choices ought to be alternatives inside a GUI installer. Introducing Orchestrator from Powershell is certainly not a decent choice and it looks excessively disengaged from the Studio Package. I don't think Studio and Orchestrator should be joined into a similar item (a la Blue Prism) however the installer for Orchestrator should be simpler.

The originator ought to be upgraded for certain fundamental custom exercises to improve the visual perspective. I figure it ought to be quite simple to a few additional shapes which duplicate the succession and allot exercises. These ought to be more modest and interactive to grow however at an undeniable level ought to take after a work process guide like Visio or Adonis. The Sequence and Assign boxes are too enormous and they make a fundamental cycle look untidy. I realize you are confined by WWF yet I am certain you could several custom exercises to supplant these.

They could work to improve the user community. For example, having a common place to discuss items. They could improve user forums. That way, we can share knowledge and experiences across different industries.

They can certainly improve their Automation Hub, which is their centralized place to gather new opportunities. The improvement could be, in part, in the capabilities. For example, it would help if there were a centralized dashboard. Maybe they could combine Insights and Automation Hub into one solution. And they also need to revisit the pricing model of Automation Hub. It is an expensive functionality that clients don't really want to pay for. They feel that it should be part of the program and available out-of-the-box. Because it's not, clients just do things using an Excel sheet.

I have used the AI functionality for PDF automations. In these processes, the bot is able to capture the data properly about 70 to 80 percent of the time. But if a document is not proper or it isn't handled the right way, the bot struggles to get the required data. UiPath has to work on this aspect so that the bot will be able to completely capture the data. There is also room for improvement in the area of third-party integrations. In the last week I have gone through a video for an integration service, but it did not show things end-to-end. Rather, they just explained the connection details only. After performing the steps they showed, I was not able to get things working properly in my process.

It took quite a bit of time to understand some of the document types. Some of the documents were already pre-built, but some of the documents were new, and it took us quite a bit of time to get it to train on those documents. If there was any variation, we had to re-train it. It took longer than expected.

Features are on track, however, service and cost models need to be reviewed to be market sensitive and related to the industry. Providing a great product at the wrong price without consideration to the economic conditions of the markets within which it is being offered, creates barriers and another product is sure to fill the void. Closer integration with machine learning frameworks and matrix processing can be improved and will benefit low-cost/entry-level uptake and activation for some clients. Although pass-through options exist and have been activated, this is not sufficient to create encapsulated learning within the organizations and serves to improve third-party algorithms with added exposure to privacy (information systems security management) risks.

The database connectors I found are not fully free and expire after 30 days. That is something I would like looked at for MongoDB specifically. With regards to this, I was working on a project that needed a robot to read data from a MongoDB database. To achieve this, I used the CDATA ODBC driver because I couldn't find a direct Activity to achieve this from Studio. See the link to the CDATA ODBC driver for UiPath here www.cdata.com It would also be great to have UiPath Insights included in the free Orchestrator. The Insights module is currently only available for paid licenses. It would be great for developers to have it included in the free version because then we could try it out.

There are some external dependencies. When we have APIs available, UiPath does have that option that we can hook into APIs. That's really where I'd like to be down the line, more like hooking into APIs, data warehouses, so that you don't have to worry too much about the screen scraping functionality, even though that's a great big part of what it does. I would really like the ability to bring OCR connectors into StudioX, if possible. Right now we're only using OCR and Studio as that's where the plugins are available. I don't know enough about the back end of what makes this feasible versus not feasible. However, at the moment, with StudioX, you can only really read and digitize PDFs. If they can bring in the OCR connectors, they'd allow citizen developers to be able to read in a larger breadth of documents that they would generally need Studio to do.

It's been four years of practice and we've matured with the traditional RPA candidates. We have a strong foundation with what we have showcased to our business folks, and we are good with the healthy background that we are building. However, when it comes to the roadmap of what's next, that is where we are not clear. While we get the concepts, bringing them to reality is looking to be quite a challenge. We are unsure as to if UiPath can actually bring our vision to life. UiPath is very clear in defining items such as this is what the high automation needs, this is what the process planning needs. We are getting clarity into those concepts and we are able to explain that and take that back into leadership to get other approvals. They are able to understand what UiPath is talking about within these different concepts. Really, it's just figuring out whether we have the right arrangement at this point and if UiPath can get us there.

The forum's a great place, however, for a new person, it was better some years ago. It's grown too fast, and it's not that nimble. Previously, if you asked questions, the response time was quicker. Since I've learned UiPath, there's so many more people rushing and getting into it. With the demand for RPA jobs, the ratio of expertise to novices is very, very low. Before you had a small community and you had a lot of experts and just a few new people trickling in at a time. The influx of new people, it's just growing factor by factor. Where previously there was one person that only had a few questions to answer, now maybe that ratio is now 20 or 30 people. You're not going to get the answers that you need as fast. Luckily, the quality of the Academy is so good, if you look around, you can eventually figure things out. The issue is that, with so many people, a lot of questions are getting asked before anyone even looks to see if an answer is already there. It tends to make it harder to find relevant, real questions that need to be answered. There are people who are not doing the due diligence and looking at the tags and spending a little extra time before throwing the question out. It makes that part hard to manage. With people that have already been up-skilled, or already been skilled in the past, UiPath needs to find a way to send some sort of notification to them when items update or change. They need to send out a message to experienced developers to say: “Hey, look at this and push it out." If you're not going to the Academy and looking for something new, there needs to be some sort of way to say: “Hey, you've been certified. You haven't been in this course. You should look at these things.” I started looking at the Academy and found new elements. When I mentioned something, like, "What's that?" the new guys were aware due to the fact that it was in the Academy from when they started and was not there when I finished. Basically, just having some sort of mechanism for spreading awareness to existing developers, or pushing something out to them, maybe even through the interface, would be helpful. Whether it’s a little highlight or a little icon to alert users to “hey, here’s something new, something pushed out.” And it’s not just something where you have to go in and read some boring five or six pages of notes, to know that this thing is there. It needs to be visual.

The license model changing every year can be a little bit frustrating. It's hard sometimes when things go from being robot-based to being runtime-based. Some federal users are still on the 2019 orchestrator or even a 2018 orchestrator. However, by being on them, they can't take advantage of modern folders. This issue is, once they get upgraded to 2020, and they start using modern folders, essentially you shouldn't really be using plastic folders anymore. Some of their frustrations aren't really long-term frustrations. Orchestrators have gotten really popular over the last few years. There are certain things that have made it so much better. That said, we're still in that transition where clients have been using classic folders and then they upgrade and they're going to have to change everything. Hopefully, they don't have to do it more than when they upgrade past 2020. One of my clients upgraded their production environment from the 2019 orchestrator to the 2020 and everything was in plastic folders and I advised them to switch to modern folders and it was a pain. Once it was taken care of, it was great. It's just that it took a lot of convincing to tell them why it was better.

The solution needs resource locking. This kind of leads toward scaling which is one challenge. It's not major. However, it is when you have multiple bots running the same process and they need to access the same piece of information to read and write. There's not a strong capability to manage the lock and have the capability to say "I have ownership of this file. No one else can touch it" and then release it, allowing the next one to pick it up. That's a key differentiator that I see between them and Blue Prism. That one feature is lacking. The studio design is a little different. If you go from one tool to the next, you might be a little shocked at how things are organized. I don't see them changing that any time soon. However, the design could be improved upon.

UiPath could work towards more engagement on the community practice side. Some of our people are having a hard time understanding how to make sense of the data that UiPath puts out. There could be some guidance as well on how to calculate ROI. ROI is how much money you have spent and how much you are getting back. But, how can I know how much money I've spent? Do I calculate the cost of infrastructure? Do I calculate the cost of the team I have? Where do I begin? What is the right way to look at ROI? What are some of the analytics I should be looking at? Utilization, the success rate, business value, and ROI have to go hand-in-hand. You cannot tell a whole story with just ROI.

UiPath has done a good job coming up with the broadest use cases. However, I would like to see them dive into more industry-specific use cases. For example, checked OCR and brokerage statements are common. Anything unique to the financial industry would be useful for us.

We are leveraging the UiPath Academy for our citizen developer program. We are asking them to train at their own pace. The courses are straightforward. The adoption rate for this program is low, however. Out of the 150 citizen developers that started, only 10 decided to continue the process. One way to improve the UiPath Academy, I think, would be to add some real-life use cases and take the students through the automation process. These would be good for citizen developers to start with.

The pricing could be more transparent. Overall, I think the pricing is fine, but they keep changing it. It should be more structured. They don't have to tell us what their pricing is, but they should publish how the product is broken down. Also, as a customer, one of my frustration points is that I'm not sure the customer success team is engaged at the right level with the customers. There's too much focus on selling more product versus helping to evolve the COE. There are many partners out there that have kind of learned over the last two years like this is what we need to get it off the ground. There are so many customers out there that I've talked to that have bought UiPath and it's just sitting on the shelf. If they can help them get it off the ground and get it going, then they can increase the community. Another issue that we run into that is not necessarily a reflection of the solution is the fact that our IT operations team does not want us running automations during business hours. This is because they don't have a good understanding of what the true impact of automation is on the source system. It would be great to have UiPath help us educate other members of the organization that automation is no different than human interaction. This could help people like me communicate with stakeholders and increase our ability to run even more automations.

The licensing model is sometimes very confusing and could be simplified for customers. That would help us understand, gauge the offer, and work it into our existing infrastructure.

In terms of payroll processes, HR processes, onboarding, operations, filling in maintenance on equipment, and doing the routine things out in the field will require adoption and interest. You can't get the response that you want until the people in the field decide that they want to change and adopt it. That will be the challenge. Managing the change is huge for us. It's always an obstacle. It's not that, can you automate something, it's more of a question of, internally, will they let you automate something? I'm looking for more of the analytics to make sure that we can properly report on how they're doing. That's what's going to make management invest further into this. I actually come from a reporting background. That's what I focus on in the other financial packages that we have.

Governance has room for improvement but that's more of a cultural thing. It depends on your company. We have the reference architecture that we have in place, but it's easy for someone to say, "Okay, I need to make an adjustment here outside of that reference architecture." Because it's so easy for them to do that, they leave the company now that a non-compliant bot is out there running a production process, we need to be able to rank that in. There needs to be footwork that we have to do as an organization for my team as opposed to a true problem with the platform.

In exception handling, wherever exception occurs, the out arguments are not being passed. It would be good if there is a way to pass the out arguments. Sometimes, when an element is not there, UiPath gets stuck, and it doesn't even throw an exception. It stays stuck for hours until we go and check the logs. When this happens, we have to kill it. It happens in some cases, so an improvement is needed there.

I would like to see more AI-related features added. Improvements could be made to the models so that they are more compatible with data science and machine learning. Better support for databases should be included. For example, interacting with SQL Server and SQL Developer would be beneficial features.

I'm pretty much happy with all of those tools. I don't have anything in mind that I could see improvement. While UiPath Studio helps speed up the cost of digital transformation, in a way, it requires expensive or complex application upgrades or IT support, as it needs an entire setup. That setup requires support from different departments, and that comes with a cost. I came across one problem while upgrading. We were upgrading from the 2019 version to the 2020. There was one thing that was not mentioned either on the website or documentation, and we had to take support from UiPath. The documentation needs to contain each of the scenarios which could occur while upgrading the solutions. As it is now, this is not the case. That said, when we ran into issues, UiPath Support helped us through it.

The AI Center area could definitely improve. The StudioX model could also improve just a little bit so that the introduction of variables is better and would make it possible to pass on a similar kind of data in between multiple activities. This is a very simple concept, however, this kind of feature is not available within UiPath. From the business perspective, a little bit more insight on the dashboard that is currently available in Orchestrator would be ideal. I agree with UiPath having a dedicated tool for insights, however, right now, it's a paid tool. If I can get a little bit more data and a little bit more customization on Orchestrator, that would be really great.

While the solution speeds up the cost of digital transformation, doing so requires expensive or complex application upgrades or IT app support. You will need IT. That said, I haven't had a chance to explore mine in any detail. There need to be more warnings for when there are issues within the automation especially when it comes to exceptions. We're not easily made aware of problems. The sooner we understand what the exception is, the sooner we can adjust things.

The new features or functionalities that come with UiPath upgrades don't work perfectly in the initial days. Their new releases are not stable. We always find some set of issues. I have to work with the UiPath team for a week or so to resolve the issues, and then I'm able to use it. The stabilization should be there. We expect UiPath to reduce the number of errors before rolling out new features to end-users or customers. In addition, many times, the apps or activities that we use within UiPath for designing are no longer compatible when a new upgrade happens or the version is changed. We want UiPath to look into it.

Licensing is one area where UiPath could do better and can be more competitive. It is a little expensive. Their bundling of products is a bit confusing. For instance, if we want the UiPath Apps license, it is bundled with Action Center, so you also have to procure the Action Center license. These bundles are not tailored as per our company's requirements. If we reach out to the UiPath partners who deal with the accounts, they usually take your request into consideration and see what best they can do, but it is still not easily customizable.

The only thing missing is something to track the development cycle. We use third-party tools to do that. That is the only gap in UiPath. Also, scheduling of UiPath robots could be improved. Scheduling is a feature for defining in what sequence, and on what machines, you want your automations to be launched. That area could be improved.

In the future, I would like new services that can utilize robots as a service (RaaS). Our legacy applications are a bit old, so we get issues sometimes in automating those. However, modern applications are very compatible with the UiPath tool. We have seen that UiPath doesn't have the capability to identify unknown pop-ups. This needs improvement. The API needs a lot of improvements because it does not give proper results. There are always some issues with the logs. When it comes to real-time scenarios, we see in production that Citrix automation always crashes. This integration could bring a lot of value to UiPath. Our business could save a lot of time and money if we could automate Citrix effectively. All of our code resides in GitHub, which is our central repository for managing the code. There was a performance issue using GitHub with UiPath; it was slow. They have recently upgraded the performance so we are happy with it now.

Many of the features that UiPath has are good, although better documentation is required for them.

The AI and machine learning capabilities need to be improved. The task mining and process capture methods are capabilities that we use, but they sometimes miss part of the task. For example, let's say that for one of my tasks, I need to open my email 400 times a day. This is something that we can automate but for some reason, probably because it is related to email, it is not accurately evaluated. In this regard, the process mining could be improved and lead to better results. The built-in OCR is only 60% to 70% correct if you're analyzing a PDF that has images in it, so this is an area that can be improved. Different companies use their own OCRs; Google has one, and Microsoft has one. The UiPath one requires that we use a validation step between workflows in order to improve the accuracy.

You do need some coding experience. AI is not available on older versions. I don't know if it is available in the latest versions of this review. Most enterprises, I'm working with still are at the previous version of the UiPath studio. UiPath needs to enable more of the features which are available. For example, today, if I have to implement an automation path for the mainframe application, I cannot do the mainframe application without the client. I cannot just do a trial. If UiPath could create dummy applications for the developers who want to try new features, that would be helpful. The should be more out-of-the-box models if UiPath keeps adding on. Recently they have added a model in their AI section. However, it would be useful to have out-of-the-box models direct themselves towards plugins. You need to continually update the solution as, if you don't, after a few months you won't recognize the product due to all of the new releases. It will be like using a completely new device.

At the moment, I'm pretty satisfied with it. Thinking about UiPath, I can't see any downsides and the downsides are in like companies' infrastructure. At this point, debugging, for me, is lacking the ability to edit on the go. It lacks the ability to stop the process on a breakpoint and being able to edit or even go a step back. This is something that has been there from the beginning and it's something that could be improved if possible.

I would like them to have a chatbot where we can highlight our issues, and that issue would be solved instantly. As of now, they have been using the customer support model where, if you have any issues, you are sending them an email. If you send them an email, then they will respond to that within a day or two. However, if you have a chatbot, they should instantly reply, which is more helpful for us.

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.

For me, it was quite an effective tool because I hadn't used any automation tool previously. It was quite new for me and it took time to adjust to it and understand it. At times, some processes took longer with the tool, initially. But when you do them on a regular basis, you understand it better and it takes much less time. Setting up the systems could be difficult initially. It would be better if it were more user-friendly for non-technical users.

UiPath needs to improve some additional new activities. For example, I have already discussed with UiPath's technical team that the image clicking and image processing are not that accurate. There is just one image clicking most of the time and it is not compatible with other platforms. There is a very common bug from UiPath with the Google Chrome extension. We would like them to help us to remove this issue going forward.

UiPath Apps is available only on Community. So, this was a best case scenario for us. It was pretty good. The only thing is that it has to be more advanced. Now, it is very basic. I would like more integration with the UI elements. It should be more user-friendly, especially if we go for any other application development. For example, in other UI development platforms, you can easily drag and drop to develop in a UI. However, it is a very initial phase for UiPath Apps, and maybe in the future, they might improve this. We have used the Picture in Picture functionality for a few attended automations, where the user is monitoring or we are installing a new interface. Sometimes, in my experience, Picture In Picture is a bit buggy. It takes over your control, then the controls get mixed. That is one of few issues that I have found. Other than that, Picture In Picture works pretty well. I had an instance when UiPath crashed on my computer. Then, the code that I was working on also crashed. This was a very crucial process for us, but we apparently didn't have a backup. UiPath also didn't have any way to recover that code. This was something which I found very strange, because ideally the source company should have a mainframe where they can recover a code. Or, if I give them a corrupted damage file, then they could easily recover that code.

The click image functionality could be better. If the interface has been changed or your web application has been changed, sometimes image clicking is not working. This is one thing I hope they can improve.

We would like to know how to implement the artificial intelligence (AI) feature because we are working on some activities in this area. The bank knows about UiPath, but not all people consider UiPath something they really trust, which is why there are just two of us working on it full-time. We do teach people about UiPath, but they are not 100 percent involved with it.

There are challenges raised by the fact that UiPath is coming up with different versions almost every quarter, and at times almost every month. We plan to upgrade almost every quarter. Recently we were trying to add AI Fabric into our production Orchestrator, but we faced a lot of challenges. We had to involve the UiPath support team in the upgrading process. We were quick movers to upgrade to AI Fabric, as not many companies have done that. There were some bugs that we discovered during our upgrade journey, and that's how UiPath came to know about those bugs. It was little tricky, but UiPath's team is always present and helps along the journey. They have been coming up with a lot of new services and products and there are a lot of announcements on their Portal as well. But it's difficult for customers to keep up with their announcements. Another area for improvement is version control functionality, particularly for Git. So far, for a lot of files, especially Excel, we are not able to compare the differences between two versions of a project. File conflict resolution could be improved.

One area that needs improvement is monitoring. I know there are tools that let us see what a bot is actually doing on the virtual machines. If we could get that kind of offering from UiPath that would be great, because when a bot is running on the machine, we don't know what it's doing. Although we have programmed it, there are times when something causes a bot to fail. During such instances, the bot behaves differently when we run it in attended mode than it does in unattended mode. It would be great to have a feature where we could see, on a screen, what the bot is currently doing.

Automation Hub is an immature product. We have only been using it seriously for about a week and have already seen some things that will give us a few headaches down the road. We are committed to using it and will continue to use it, but I have some suggestions for improvement. We have been in contact with our local UiPath office about that, and their initial response was positive. We would like to see more detail and refinement. It is still a young product, and we are confident that the product will improve a lot over the next few months. We are hoping for some integrations between Automation Hub, Orchestrator, and Insights. We are missing a way to quantify that money isn't everything with this solution.

An area which the UiPath team is rapidly working on is machine learning and artificial intelligence. At the moment, it is a little difficult to understand. If they could add some more training on it in their Academy, it would help customers to learn about these features.

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.

If websites are made in a recent programming format, it is very easy to automate them with the help of UiPath. However, if that technology is based on legacy applications, then it is very fragile and hard to do that. So, we have to choose the technology first, and if the technology is new, then you can easily automate it with other applications or the help of an RPA tool. The process can be complex if an application is a legacy application or the data is unstructured. The analysis of some bots is lacking. If a customer asks for analysis of a particular bot, you cannot just get the data from the UiPath and give it to the customer. It is not that easy. I would rate this process as a seven or eight (out of 10). The Document Understanding feature should be more developed and advanced. For example, you have to make a template with their ML model. Currently, we can't use our own ML model, and we have to use the UiPath ML model. UiPath has only a few ML models right now. They should come up with more ML models or make it easier for us to use our own ML model. While they are working on this, I have felt much difficulty in extracting data during our last process for Document Understanding. We had to go with the Python language. So, I think they are lacking in this feature.

We are moving from single sign-on to no password sign-on. As we are moving ahead with technological advancement, maybe that feature can be added. This totally depends on how that technology is accepted by the people. If people in big enterprises are not willing to switch and don't want to move away from the single sign-on, then it will be very difficult to digest this. However, whenever there is a change, it is very difficult to digest. Eventually, people will like it. I believe if it is implemented as part of UiPath, who is a technological leader in terms of RPA and new stuff when they roll out every release, then this would be a good area that they can look into for enhancement. They could add more features in order to get that dashboard more intuitive, e.g., how easily can we visualize everything being reported. I believe this should be improved as part of our Orchestrator offering. Now, we have different visualization tools being used, like Power BI. The data gets flooded into those kinds of tools and the dashboard is easy to understand. So, someone with a non-technical background can see the dashboard and understand what has happened. However, to provide detailed analysis, there has to be some improvements so we can provide drill-down data to developers showing, "Hey, this has gone wrong." If they could also incorporate that as part of the reports, then it would be very quick to view on the dashboards.

There are a few features that could be improved, and one of them is good integration with the Microsoft ecosystem. For example, Microsoft launched Power Apps as its platform, and even though its capabilities are not as good as UiPath, it has the advantage of being so well-integrated with Excel Online, Word, and everything else. We don't have to perform a lot of development work, and it's pre-approved in our organization. Applications like SharePoint are another example of pre-approved solutions. But with UiPath, we have to prove that it's a secure process. Simply put, a stronger collaboration between Microsoft and UiPath in a lot of areas would be helpful because it would ease the development process for us. Another example is with the Automation Hub. At this time, Automation Hub does not allow you a direct login process or single sign-on option using Azure Active Directory. This means that you're limited to going through either Gmail or something else. This is true for the on-premises solution, not the cloud one. Although we had decided to purchase the Automation Hub license, this lack of functionality held things up because we did not want to manually go in to update all of the new users again and again. We wanted the information to be picked directly from Active Directory whenever a user wanted to sign up for it.

The licensing system is something that needs to be improved. I think that if they are trying to push for a SaaS solution, with respect to the way they license their individual products. The robot licenses and the Studio licenses should be something closer to a pay-per-use, rather than a year-to-year license. Right now, the licensing model and the pricing are the only stoppers for us, in terms of escalating our use. The bottom line is that the licensing system is not as modern as the tool that we're trying to implement.

They should include new machine learning and AI algorithms for better forecasting and analytics.

Need more AI and Machine learning build technology and integration of 3rd party applications. Need some improvements in orchestrator

The documentation can be a little bit lacking. I think they improved it a little bit last month. Last time I checked, it seemed like they spent a bit of time trying to improve it. Sometimes some of the processes are nicely documented. UiPath offers training, which they provide on their website. They teach you how to use it, but for some processes, it just seems like the documentation isn't really there. It makes it a little bit difficult when you're using a specific process from the first time. If you're trying to invoke a method in UiPath, if you're trying to write a C# in there directly, or if you need to do something which can't really be done in UiPath, but it can be done in C# or Python or something else, sometimes it's not that intuitive. It can be a little bit more complicated than it needs to be. I think that integration with other languages could be a little bit better.

As things become more and more data-heavy and accessing other people's products and managing things, like obtaining the data through APIs, it feels like there could be a lot more for them to do, to make interacting with data or manipulating simple things like text strings. You need quite a strong development background or a reasonable level of understanding to achieve that. I think that could be made a little bit more achievable.

I could use more standardized features, retail-style, things that I could use off-the-shelf. Right now, all this requires quite a bit of adaptation in bespoke work with UiPath, which they've done very well. But looking at it after having used it, I would get stuff that is prepackaged from them, if they were any.

The pricing for Orchestrator and unattended robots could use improvement. If we plan to roll out and implement more robots, then perhaps lower costs on Orchestrator and unattended robots would make adoption even easier.

We have not seen it do OCR, and that would be helpful. Right now, the tool will not read a PDF file, and we can't use PDF files. We want it to able to take an image, then take that image and put the particular field out in the right spot in a table. We have not seen it where you can scan a document in, then it reads fields and places those in a table.

What we have in mind in terms of what the robots could do for us is significantly more than what UiPath does now, but it takes more work. From my perspective, there is just a wide scope of implementation that goes beyond what we're starting right now. That is essentially the improvement. While I have nothing negative to say about our experience with them so far, I think we can work to develop more complex products with them. They are already working to develop something for our use cases, but what I would like is if we could develop more things for more complex needs, e.g., where we start with simpler stuff, then we can add things to what we're doing now.

The platform that shows the reports and errors is not too transparent. I experienced it at my workplace when showing the reports, where the platform looks unfriendly and it is not very transparent, especially compared to the other features of the product. The monitoring period should be shortened as soon as possible, as most companies won't have one to two months available to implement and test the RPA. People want results instantly when talking about an investment. I would also like fewer errors, please.

UiPath support needs to be a bit quicker than it is currently. They need to be very quick when they see a customer is struggling with something and taking the step to contact support. The UiPath team needs to put some effort into improving the support section online. They should also improve the UiPath community forum so that beginners can receive help with activities that they require.

As more and more organization units are trying to use RPA, there might be a need to have separation of data within multiple tenants or organizational units. Not only on the front-end but also the ability to have a separate database for each Tenant. This will leave no room for the enterprise security team to raise questions on data separation. I feel that a Host Admin, being a master Admin, should be somehow able to login to different tenants.

I would like to see some artificial intelligence for UiPath that would help us with OCR and other things like computer vision. AI would be helpful for us to implement those kinds of solutions.

It's a very powerful tool but it can still be improved in many ways. In most cases, the results from the software are the same and not variable. This means that we have to define the variable by editing the flow chart. This case happens when we are recording the navigation from the web. Moreover, sometimes there are lots of screens in the process and decision making is required. I believe in the future this process will be handled by the click of a button or automated in a better way, with minimum human intervention.

The Studio can be improved by adding certain features like color-coding the activities. By letting the user change the color of the activity box (or by having different default colors for each type of activity), it's easier to identify activities especially when they are nested together. The Orchestrator can be improved by making the landing page dashboard customizable based on what information and stats we want to see as an organization. The stats shown in the Orchestrator dashboard are very basic. Today, we had to make a separate web app that uses the Orchestrator API just to see the data that we want to see in a format that we prefer. Our business needs visibility on which country the failed/pending bots are servicing and how many jobs were completed based on tower assignments. These stats are not available out-of-the-box in Orchestrator.

They should provide more features in terms of robot debugging and image automation. If you are a large organization then try the community version first to get a hang of it. After this, move onto its enterprise version. They should improve their document and support in terms of actual errors or problems the user may face.

Possibility of improvement: * Exception handling and exception details can be much better and more user-friendly. Many times, details of exceptions are not understood by somebody with a non-coding background. Example "Object Reference not set to instance of object", this is the exception message that we got and log from UiPath. For a developer it makes some sense and meaning but for a SME or User it is very complicated to understand the meaning if this exception * User interface in the coding area can be better and more compact: Some times expanding seq. cause the code to look very big and difficult to undertsand the scope of container

There are some problems with selectors and in PDF extraction so it could be improved a little bit. There is a bug in UiPath that occurs when the URL of the web page changes. We are unable to scrap the data from that application page. The Community Edition is not stable, so end-users working on the Community version may find some errors or issues when using this tool. Also, debugging is not as expected. A lot of issues occur during debugging.

Definitely, the machine learning engine should be improved so that we can process more invoices and purchase orders in PDF format with ease. There is a beta version but it is not stable. This is the only place where UiPath needs to improve because their competitors have this option and it is useful.

StudioX could use some improvement to broaden the range of automation projects suitable. At this stage, it is limited in terms of the functions that are available and I would like to see a lot more options added to this tool so that our business users can get even more benefit.

As in my opinion, debugging needs more improvement. Also, if we get any other tool or technology which helps extract information from the scanned or handwritten document than that will be really helpful as a user and for our clients as well.

The area that must improve is while releasing a new version, it must be capable of running the bots developed in the older version. It would be nice if we can develop an intelligent bot that can make the right decisions. Please include the option to select the time zone while scheduling the Bot in orchestrator.

OCR-based activities should be improved to handle larger amounts of text. UiPath does not recognize Google and Microsoft OCRs. Sometimes UiPath will not work properly, even though it worked the previous day. Also, it may suddenly not work when we switch environments from development to QA. This happens approximately one out of ten times.

I would suggest that UiPath be released for use on other platforms.

1.For example: If two members are working in one project but different xaml files. In one xaml file suppose i did few changes and if any more changes are required to do in the same xaml file the next member can see what changes has done in the activity and do the required changes. Basically i mean the changes whatever we do there should be some place where we can see the history like Modified By, Modified Date and Modified Activity. Which makes easy to track who is the last member to modify the xaml files. 2. There should be a global search mechanism for variables in the process flow and if the search is found then it should indicate that activity. 3. There should be activity/some mechanism where we can revert back the code of that particular date.

The user access management could be improved such that we are able to set up user rights in a more sophisticated way. In the current version, if you grant, for example, Execute access to a user, it can execute all robotized processes in the given environment. You cannot specify the rights at the process-level.

One scenario where it is not great is on remote desktop automation, where applications are not directly accessible. It does, however, have some features to facilitate this kind of automation and definitely stands out from the competition because of things like that.

I would like to see the computer vision activity updated. There should be a click-event-update activity present in the UI Studio where we can click a link and the result should act as a button. Right now, this feature is not available in such conditions. The OCR should be made faster to save more time. If I am buying production licenses from UiPath it should provide at least two or three nonproduction licenses for further use. The Studio should be made interactive like Orchestrator. The debug option in Studio is not working on breakpoints, which is an issue that I have already highlighted in the forum.

I would like to see improvements made in OCR, Captcha Automation, and PDF extraction. There should be a clearer way of performing web scraping, such that it is simpler to do. Overall, more add-on features would improve UiPath.

Robotic process automation should mold and grow into intelligent process automation where a BOT can handle more than just robotic and simple tasks. I'm sure UiPath is working towards it. A self-coding robot can be a very useful tool in the future.

There could be improvements made in in terms of debugging. Troubleshooting is hard. I hope there can be more major improvements in Orchestrator, such as the ability to have session variables other than assets. Being able to filter work queues, just like what Blue Prism has, would be a helpful addition. There are some limitations like the UiPath Executor becoming stuck when running 10GB text files, which is something that really needs to be fixed. The training is difficult and should be made better.

They still need some improvement in their new version of UiPath Studio, called StudioX, to improve design for Excel and email automation work. The OCR functions need to be improved.

Having the ability to run the bot from a single click will help to democratize the RPA. Currently, I am running the XAML file from command prompt mode and this is causing inconvenience every time I update the XAML file. The regular update of the Community Edition means that the UiRobot path is constantly changing on every update.

More quality of life improvements like automatic argument inheritance would be an improvement. Also, have more courses, maybe for more prominent packages like enhanced REF, and the others released together with 2019.4. I also hope that UiPath can be closer partners with us.

The setup and licensing process are somewhat cumbersome. Additionally, the Studio publishing is somewhat antiquated within Orchestrator. Overall, it should be a much simpler process to move a process from Studio to production, specifically as an attended Robot.

Below are the three features that need improvement: * Allow "Wait for task" to be used in XAML files other than Main. * Allow mail-type variable to be stored in Orchestrator queues. * I would like a way to add priority to the outgoing mails from UiPath studio.

Since I am not an expert, I am looking to the training lessons. The training could be improved by clarifying more and more at every step. We would like better integration with custom environments and external inputs like forums or integrations with other robotic frameworks.

The attended bot functionality is in need of improvement. The use cases are rare and the licences are quite expensive (in relation to the use possibilities we see) for attended bots - Therefore we are currentlying neither using or planning to use them.

I work in a highly regulated field and so many of the features offered by UiPath are not allowed because of one reason or another. I would definitely appreciate efforts to be made to build useful tools that meet regulatory standards in different fields so that we can all get the most out of automation.

Improvement should definitely be made in the area of screen capture, where Adobe Flash is still being used. Trying to 'read' a screenshot (vs looking at HTML) was a challenge, and even when Flash goes away, there will always be a need to do a screenshot and then get data from it.

The ease of sharing the bot to different users is something that should be improved. Something of "cloud" capabilities would be a useful inclusion. We live in a time where remote work is essential and we should be able to access and run the bot from anywhere. Typically, you can run these processes in the background but it slows down the computer.

One of the problems with UiPath is that it doesn't interact with some programs, such as AD and Chrome, and it would be great to have even more included!

The aspects that we feel can be improved are: * Sometimes the tool is not stable with the selectors that are used to identify the different windows within the Windows operating system. * Backward compatibility is missing. After upgrading to the new version, some activities won't work. * It would be nice to have this tool support other operating systems too. * C# is missing and it currently supports only VB.Net. We would like to see C# support in the next release.

I would suggest that they improve the UiPath Connect Enterprise because the planning stage is the most crucial in the RPA life cycle. Right now, the UiPath Connect Enterprise has little analytics on computing the ROI and the complexity of the automation idea. Maybe there should be more fields on the form to fully get all the details to really compute for a concrete ROI or complexity of the idea.

The machine learning module can be made more usable, including the latest improvements in the field. Technical support needs improvement because it takes too long to escalate when necessary.

I would like to see the replacement of VB.NET with some more popular programming language as the program's backbone.

The user interface can be improved and the version control can be better. Document linking can also be improved, and also the searching could be more user-friendly. Better integration with AI would also be an improvement.

Dynamic Selectors should have a specific chapter apart, as most of the tools are currently driven as such. It is still a bit difficult to decide which selectors must be used based on current descriptions and documentation. My view is that overall content and story line could be reviewed for a more impressive experience. That is the only thing I have to raise, as all of the other features and functionalities are pretty good.

The performance could be improved, and it is especially noticeable on older hardware.

They should add chatbots functionality for Microsoft Teams and not only for Slack. They could give more information about beta / pre-releases so more people can test them and give their feedback. Keep updating the documentation because sometimes you get redirected to a non-existent page or an old version of the activity.

The product should be made more friendly to non-programming users, as some functions require a background in VB.NET. UiPath should also add activities for the Excel application like formatting Excel columns and rows.

I would say a better layout or interface between the Studio and Orchestrator tools would be nice.

I would like more incorporation of Artificial Intelligence (AI) features to allow for intelligent character recognition which can account for different formats and unstructured data. Specifically, the ability to not have to create templates for various formats to account for variation and rather intelligently extract key data regardless. There are some AI-like features in beta, but we are very interested in deploying now.

If I were to talk about the improvements, I think that reducing the cost would be the first thing on my list. The dashboards for statistics would be great if they were more complete and more easy to integrate. If I could also see all the statistics on a mobile phone with a special mobile application and manage all the bots, this would be helpful. I think that they must continue to integrate more digital intelligence tools in order to increase the capabilities the product provides for the users of their solutions. I know that they provide some of these tools, but they must continue researching and improving them.