Please share with the community what you think needs improvement with UiPath.
What are its weaknesses? What would you like to see changed in a future version?
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.
@snahta Your content has been moderated. Please avoid sharing any marketing content. Our community is for knowledge sharing. Thanks for respecting our guidelines!
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.
* 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.
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.
The emailing and integration with self-service BI systems are areas that need improvement.
The operations need to be improved.
They should expand on workflow type items and take another step up from the long-running workflows to offer more visibility of business processes within Orchestrator. The solution needs a better integration team, different versions of Orchestrator, and to make it easier to identify problems with versions, as well as to be able to fix those kinds of problems. It's hard if you don't keep up to date all the time as well, for example, to go from 2018 to 2019 versions. It's quite a big jump considering activities and things like that.
More industry-specific training and information would be highly valuable to us. We're a healthcare company, and it would be helpful to know where and how automation is being deployed within a healthcare environment. For example, what have we done that we could share with people, and what are they doing that they could share with us?
There are a lot of things that can be done to the product to make it better. The feature list that I develop between releases is often covered new releases of the product. That is good. But there are still a lot of enhancements that I would like to have within the Orchestrator and the queues. For example, how we manage the queues is an important thing. I would like to see the ability to have other ways to look for one transaction within the queue. If I am looking for a single transaction, it would be good to have a filter that you can use to specify a detail, like just looking for a reference name that starts with a particular letter — but not the entire reference, but wildcards. Those are the kind of things that can be enhanced and make a big difference. Maybe they are not on the roadmap for the company when it comes to upgrades at this point because those are tiny things within the tools. But even those tiny little things can make a lot of difference in the functionality of the tools.
Orchestrator needs to have better integration to include business users.
In future releases, we would like to see more drag-and-drop, and more out of the box AI.
As far as additional features, there doesn't seem to be anything outstanding that I can think of right now. Maybe some off-the-shelf "How To" features could be installed with Studio so that you can search for how to do something and pull it up directly in the Academy or on-screen without leaving the product. There could be room for improvement in the ticketing feature. It's kind of hard to find that feature sometimes.
We would like to see Studio made a little easier so that our non-technical customers can also implement the bots. For example, some of the features from the upcoming Studio X should be put into the original Studio, as well. I have trouble understanding the machine learning and AI components, so I would like it to be easier to understand how and what to do with them.
One additional feature that I would like to see included in the next release of this solution — and actually looking forward to — is more development in the reporting. The Insight piece that was announced was very good to hear about. We are excited about that and looking forward to it just so we do not have to develop our own reporting infrastructure. Instead, we can leverage UiPath's Insight platform to do reporting, deliver reports, measure production errors, and further simplify how we gather and assess information. As far as room for improvement, I would say that is my biggest missing piece.
I would like to see a biweekly scheduling option in Orchestrator. We've actually built into our automations a roundabout way to process every two weeks but it would be really nice to front end a biweekly schedule. Being in the financial services industry, we do have a lot of projects that run on weird schedules. We've kept some of our automations attended just because they're ad-hoc. They might need to re-run them. We don't want to have to wait for Orchestrator managers to kick those processes off. But, outside of that, there is no need for this one to be an attended robot. It's a perfect candidate for unattended automation, just the scheduling is the problem.
In the next release of the solution, my biggest hope would be getting more accessibility to test data processing information. I was told that this feature was coming already. Being able to see what my variables and my arguments look like when things are being passed and making the processes very clear to my customers when we are doing test cases for UAT (User Acceptance Testing). That would be invaluable. It would help the customer to see and understand the data flow more easily without having to go through training or being very tech-savvy. I think Studio has a little more room for improvement and could use a few more features. They just announced Studio X and Studio 2 which actually addressed many of the issues I hope to see resolved, but that is assuming that they come through in development and do what they say they are going to do.
We have seen a lot of benefits on the backend, but then the algorithm is constrained, which can't transform because of the older technology. Sometimes in their partner communication, they aren't consistent. This maybe is related to the fact they are growing as a company.
I would like to see support for native C# capability. I have a .NET background, so it's easier for me to write in that language.
I would like to have a guidebook of examples that help me to determine the feasibility of specific use cases, based on the tools and the features that are out there.
In the next release of this solution, I would like to see better scheduling options. Because of the schedule limitations, you can only schedule one process at a time. There are situations where I might want to build five processes that need to work together. As I can only schedule one at a time, it isn't currently possible.
They have added a lot of new features over the past months, and things are a little more complicated. In the interface, sometimes you just have the screen full of windows and figuring out what goes where can be a bit tricky. We would like to see improvements in Studio such as syntax highlighting and documentation functionality for audit purposes. That would be great.
When we deploy code into Orchestrator, sometimes there are macro activities that worked in Studio but do not work correctly in production. For example, I have implemented a Text Reading Activity that worked fine in Studio, but after deploying the code into Orchestrator it does not read the text exactly. I was able to create a workaround by using a split function in the code. It was reading the text fine because the data is being read using split functions, but this is something that I would like to see fixed. I would like to see more AI and natural language processing. Having chatbots available would be a helpful inclusion in a future release of this solution.
I find it difficult to set up the Orchestrator and it should be more user-friendly for non-technical people. I understand how we create packages and push them, but I find the maintenance hard to follow. As it is now, I have to contact our IT department, which takes two to three days. In the meantime, we just have to wait.
I would like to see more options in terms of configuration. More information should be made available on the AI Fabric features, and how it can be used as part of a larger ecosystem. Unattended robots could be cheaper.
I'd rate the ease of use of automating our processes at three and a half out of five at this point in time. That is because we've been on a journey over the past year or so and it's not been smooth sailing. There have been issues. I'm not saying that UiPath's support hasn't been great. It has been, but there is still a lot of work to do. It's still a relatively new product in terms of the grander scene of the industry. There's still a lot of work to do there to make sure that the integrations with existing software providers as well as new ones and API connectivities are as they should be. Often, you'll find yourselves using the workarounds in order to address issues that they haven't quite solved yet. I know that's constantly being improved, but that is the journey that we've been on. One of the issues is with the acquisition of new types of software and new companies. It's important to introduce process documentation and make sure that it's not just making it look like UiPath products, but making it feel and act like one to us. They need to make sure it's embedded and the integration is seamless. They should just keep improving how easy it is to use. I think it's very good already, but there's always room for improvement.
When you are tech savvy and been trained, it is a four out of five for ease of use. Having that automation recording feature operate better and capture more of the automation that you're trying to build would make it a five. With the new products that were announced, UiPath closed a few of the gaps. I can see how they could expand the products into other areas. There is potential there for some workflow capability. I know this would be going beyond RPA at that point, but having one platform that does a lot of things would be nice. Because as it stands, when you need to do a workflow or approval process, you need to send this out somewhere else. There are things the bot can do, but I can see some of that functionality already showing up though with the tasks and apps. However, I would like to see more. That would be good. Moving bots to the cloud would be the next good step. The new product has Orchestrator in the cloud. I think moving to bots to the cloud could also be next along with having Studio in the cloud where you can do everything in the cloud: Deploy and run your bots from the cloud.
We now have a functionality that is being released for web forms. It's more for attended. I would like to have these web forms exposed in Orchestrator to be able to trigger a bot externally. I know we have partners that provide similar functionality. I would like to have that same functionality where you could deploy a form, but instead of having it pop up on somebody's desktop, they could go through a URL through Orchestrator and trigger the bots via a web interface. This is instead of having to be tied down to an attended bot. For some of the Insights stuff, we have found that you have to be flexible on measuring your ROI. You have to be able to customize some of that because it's not as cut and dry as you think it is. I would look for the audits on the back-end. Performance-wise, make sure that it is still performing.
The Form Builder for back-end robots needs to be a web portal instead of a full desktop application.
Even though there are things I'd like to see, I also know that most or all of them are already being announced for new releases. As a developer, I would probably say the most important thing I would like to see is that the IDE (Integrated Development Environment) a little bit more fleshed out. It could use more debugging capabilities, for example. But again, we've been seeing that they're adding stuff like that. It will be getting in there and playing with it when it is released to make sure that it has got all the stuff I want and I might be able to be more specific after that as to what still needs to be added.
I would like to see some use cases and additional information on the process mining and the OCR features that are being released. There are other products that offer OCR features, and at this point, it is hard for me to determine the benefit of using UiPath for OCR rather than integrating it with another solution. This is not just from a business perspective, but from a development perspective as well. For example, I would like to see how you can connect UiPath to all of the applications to collect the logs and the data. Then, how we can put that information together. If there is a thirty-minute delay then how do you identify whether it was because the person went to lunch, or rather that they were working and thinking.
I would like to see more features included in the AI Fabric. This is the biggest thing that I am looking forward to.
I would like to see more support for the cloud in Australia. A tool that better identifies the processes, watches the computer and works it out for me, would be an improvement.
On a scale of one to five (where five is beneficial), I would rate the UiPath Academy as a four. There is some stuff that they could do better. I sampled the advanced, which is really difficult because it's just PDF. I had to use some YouTube videos to understand the framework that you need to pass for developer. They could do more videos on that. They have three parts. The first is the foundation, and they are a lot of videos. The third part of it (advanced), there are no videos except one. That's only those PDF files, which you have to look and read through. I was like, "Okay, I probably can't do it." Then, I fell upon some community YouTube videos from other developers who just demonstrated it. This would be great if UiPath offered that, because I found out later that the developers made mistakes in their videos. In the foundation, they get into much detail in the beginning. You're overloaded with information. You have to go through videos like three times to get it correctly. They could remove some stuff out of there. Those quizzes are really frustrating too. They are too detailed. If you sat with Uipath, you think it's really easy. However, it's not so much, if you get into those details. Studio is a bit overwhelming in the beginning. They could get add some details, but not so many, into the foundation training. I've seen StudioX and loved the colors. Please get the colors into Studio. I loved the flow and that you got all these activities and colors too. It was so much easier. It was visually easier to understand where to click. It was really user-friendly. I would rate the ease of use of the platform for automating our company’s processes as a four out of five (with five being very easy). I would rate it as a four because it didn't work in the beginning to get my bots active. I had to get into a lot of videos to get them running. I didn't understand how it needed to be designed or coded. The Orchestrator training was much better, but I still somehow missed some details which I needed. However, it's not just do it, then it's done. You need some time to get into it. Though, it's much easier than Studio. The integration with Outlook is not that good yet.
We do deal somewhat with Citrix. It depends on the client and how the bot has to be set up. We have some clients who do run through Citrix, then we have some who use a VPN tunnel to get in. So, we have it on both. The implementations or integrations through Citrix are really good. The only problem that we are coming across is just maintenance. If the Citrix platform gets updated and we're not notified, it breaks. So, we have to reconfigure our bot to the new updates. Unfortunately, that's just the name of the game, and that would be true if we were pulling them manually versus a bot. We would still run into that with the Citrix platforms.
We don't like the attended bot experience, where it requires the user to be hands-off. We installed it on the user's machine, and the user should not touch the mouse or keyboard because the moment they do, it crashes. It takes over the machine and cannot work in the background. For this reason, it is difficult to work out scenarios that are purely attended. For example, we have a process that downloads two files and then does some massaging of the data. Now, the data needs to be looked at by the user. An email is sent and the files are deposited into a common folder, and the user will address the task when they have time. After the user manipulates some of the data or makes decisions, it can proceed to the next step. They drop the modified files into the common folder, but the bot doesn't react because there is no feature in Orchestrator to trigger based on the arrival of a new file. Instead, we have to put in a call to check periodically, whether it be five minutes, fifteen minutes or some other interval. This is something that we don't find desirable. Creating a trigger that is based on either the arrival of a file or the arrival of an email is a common scenario and it should be built into the platform so that I don't have to code for it every time. As it is now, there are only two ways to trigger a bot. Orchestrator does not have a good filtering mechanism to look for jobs, and the table view needs to be improved. From the UiPath side, one thing that irritates me is that you cannot find the downloads to upgrade to the new version. I'm a paid customer and I log in with my credentials, but I cannot download it. I need to create a ticket, tell them who I am, and I have to give them a long list of things that I don't remember. They will address the ticket maybe today or tomorrow, and then finally I get a response. When I use other tools like Microsoft and SAP, as a customer or subscriber of the tool, I just download the latest versions and install them on my servers. When I have a mandate to do work, I want to be able to do it. However, when I can't download the file and have to wait for a ticket to be answered, this wastes my time. The integration with Elasticsearch and Kibana is a struggle. They are not UiPath products, but they are recommended by UiPath. Some documentation is provided, but it is an Orchestrator installer package the just installs itself. I had to do a lot of experimentation on Windows machines because the configuration is different for Linux machines, and this gave me some trouble. There is a lot of information about this in the UiPath forums and I spent a lot of time on it. Right now, I have a set of configuration data that I put into an Excel file. The users can change the file and my app will run using the configuration variables. A problem occurs if the Excel file is not closed properly because there are locking issues. This is a pain because the bot crashes when opening a locked file. There is something in Orchestrator called Assets, but it is kind of limited. It only accepts text and a credential. It would be nice if it had a simple database table, say to be able to create a couple of columns that I want to set up for a bot-related task. Rather than a single piece of text, there is a whole table of information. My users will be able to edit it, based on the permission that I assign. Then the bot will look at it and work according to what is specified. This would be a great feature to have. I would like to see the Studio web-based so that we don't have to install it on everybody's desktop.
In the next release of the solution, I would like to see the ability to grant permission to users at the job level. Some jobs or processes may need to belong to only one person. Right now, I believe we don't have that feature in UiPath and we can't assign a job to a user. We can give permissions on a tenant level, or we can give permissions on the environment level, but not at the job or process level. I would like to see the ability in UiPath to be able to assign each job or each process to a particular user and give that user some specific access and privilege. For example, maybe they should only be able to run or stop a particular job or a particular process, but they can not do anything else. That makes a lot of sense because all users may not need to see all the processes in Orchestrator in one instance or have access to administrative features. The same goes for a tenant or even in an environment. If UiPath can make that happen at the user-level or process-level for a robot, that helps a lot to enable customized bots.
I talked to the product team. They are very passionate about this. In my opinion, all the different components that they have now released should be integrated under a single umbrella, available through a single landing page. That way, everything integrates with each other and they are able to communicate data back and forth. To me, that would be the ultimate solution. I get it. There is a roadmap and it's a journey. Still, I would like to get to a place where everything integrates with each other. Now that we have all these different means that can help us enable a customer in their journey, making sure that they're integrated would truly add value. That removes the overhead of combining data from all these different sources.
There are a few areas where the product can be improved for our use. Invoice processing, for us, is a major use case. I saw some examples in our research that mentioned machine learning models and how to implement that in the new, upcoming version. It seems that the machine learning would solve some of our current issues in processing. That is one feature that I would like to see and experiment with when it is released. I want to explore that to see not only what it can do, but how efficient it is and how it affects the performance of invoice processing models. The other feature we are interested in that is promised to be in the next release is the VDI (Virtual Desktop Infrastructure) desktop. Those two features, for us, are critical. But we also need them to be fast and efficient for us to be able to use it in practice. Otherwise, we are going to continue struggling with the solutions we already have. The solutions are kind of already there in UiPath, and I think they need to work hard on the performance of anything they release. This is especially true for those two solutions. For us to have a good business case for deploying them for use, we need them to be efficient. A feature that we tried to use that clearly has room for improvement is the UiPath Computer Vision component. We have tried to use that but it was not efficient enough for our planned applications. It was a little disappointing. It needs to be improved in performance and in the design of the machine learning models. It is pretty easy to use for people considering the technology. I just don't think it is quite to the point where it should be.
It's really hard for me to get all the machine learning and AI parts. I think maybe that's going to get a little bit easier for me to understand how to really use it in the company. I don't really know what to do with it at the moment. I think that is something that could be improved. I tested the live sessions and we saw some parts of StudioX. There were some things that were so easy there. I think it would be good if they would put it also in Studio, for example. The carts they have are in color. We try to get people in the company, even if they're not technical, to implement the bots or processes by themselves. I think some parts they changed in StudioX could be really helpful in Studio skills.
I would like to have cloud in the next release. It's one of those things that allows customers to be able to have an easier access point. There are still areas for improvement for some of the drag and drop features and moving more to a bit of a lower code perspective.
In the next release of the solution, I'd like to see process mining to analyze business processes through event logs. It would help the end-users determine what processes need to or can be automated. As for areas of the solution that have room for improvement, the usability for the end-users could improve so that they will be better able to program on their own. Coupled with process mining capabilities, that could remove the need to involve programmers or IT in the automation of simple tasks. The cloud platform could be improved so we would be able to deploy through that with sufficient security.
Everyone has used the UiPath Academy training. I would rate it around a three or four out of five. While it's simple and you get a decent understanding of what's there, you still have to dedicate on an awful lot of time doing the automations to become proficient at them. While it looks like it is being addressed, getting the unattended robots to every person's machine in the company and executing on their machines needs improvement.
Areas of this solution that have room for improvement are a couple of activities that have issues. We would like to incorporate machine learning so that we can do some of the quality checks that we do automatically instead of relying 100% on manual quality review by humans. Additional features that we would like to see included in the next release are those they seem to already have planned. I am very intrigued by the AI capabilities that we saw in demonstrations. Having that capability would be absolutely fantastic.
More Excel activities should be included. We do have basic Excel activities, but we don't have ones to do things like add colors or formulas. For these types of operations, we always use custom objects and have to write custom code or pay for them.
The Insight product coming out in the next release looks interesting as a management tool, but I haven't dug into it enough to fully appreciate it. Obviously, the Studio can always be improved. Even though you can drag-and-drop, it's still cumbersome unless you are a programmer. I think the Studio X is going to help tremendously for the citizen developers. I think that is going to be a big benefit in simplifying the interface.
I'm not exactly sure what I want to see enhanced yet. I know that we do a lot of small processes. Depending on how good Studio X is and how easy that is to build and manage we could potentially do a lot of small little things inside of various design tools like Excel, Word, and Outlook and to be able to kick out the workflows from that. We like to do a lot of the design side locally for Excel, whether that be in a BBA or an add-in type environment. Being able to manage and deploy or build those will be helpful. Maybe we won't call them bots, maybe we call them processes that are centrally managed. In addition to the Microsoft stack, we use many other vendors like AutoCAD, Bentley MicroStation, Revit Inventor, BIM 360 and Autodesk Forge. To us, the CAD world is where we can see a lot of time savings and benefit ROI on a solution. That would be our next horizon. I think this solution has room for improvement in the area of ease-of-use. It does require a little bit of coding background to be able to get in and really build out the solution. After I get in and look at Studio X a little more, I may change my opinion on that.
We have been patching together a number of different solutions to try and create a more holistic automation solution. The newly announced features such as Long Processes, AI Fabric, and improved attended dashboard will go a long way in solving those needs.
I would like to see them improve the validation part of the data categorization.
In the training, between steps two and three, there is a pretty big leap in terms of how difficult the material is. Moving right from the basics into the framework is causing me to struggle a little bit, and I think that there is room for improvement here.
VM was on the service for high density. It is finicky at times. The latest release is a lot more stable. However, I've had a two week production outage where DLLs weren't registered and someone from Vegas had to login for eight hours onto the fraud service to work it out. Even though they uninstalled and re-installed it, all the different apps still wasn't working. So, I have lost a bit of faith in it to be honest. I would like to have cloud stuff back in Australia and hosted there. I want everything in SaaS, bots included. While it has eliminated human errors, it has created other errors. I would like something that better identifies the processes. If it could watch the computer, then work it out for me, that would be good.
I would like to see anything that can increase the reliability of the processes. It can be a really challenging task and there is certainly room for improvement. I would like to see more selectors included in the next release of this solution.
The licensing process is complicated and needs to be improved.
Several areas of this solution need improvement including insights, the dashboarding of results, and process mining. When it comes to scoring, you receive a score after the intake and a score after you build it, but you should also get a score after you build it.
I am looking forward to new cognitive and artificial intelligence capabilities. I would like to see voice recognition and better OCR capabilities. Today, we have to leverage other tools for this, so we are hoping that UiPath matures in this area.
It is sometimes difficult to work with the exceptions, which can cause us a delay. We have a lot to learn. I would like to see more options that we can quickly select to help improve the robots.
I would like to see more AI features with data classification and computer reason. I think it would be great to have more features in full monitoring robots.
We sometimes struggle trying to figure out what kind of a bot we need to use for what kind of work, and it would be nice to have more clarity on this.
One of the things we're struggling with it how to project how many robots we need to do these processes, so better documentation or assistance in this regard would be useful.
On the development side, more documentation on how to structure the setup for different environments would be helpful. Our biggest struggle had to do with questions like: * Do I need to have fifty monitors to run fifty different bots? * Do I need to have fifty separate computers around fifty different processes at the same time? There was no really good documentation to teach us how to do that, so there was a bunch of trial and error involved in figuring it out. We know that we didn't want on-premises computers, but we didn't have any documentation to explain how to set them up in the cloud. We went through several different iterations before we finally got that right. Ultimately, it took us about three months before we decided on the structure that we wanted, so better documentation on infrastructure would be very helpful.
Enhanced capability in the document management space would be a huge benefit to our organization. As part of our business process, we receive a high volume of returned documents. Managing that high volume, in the millions, can be a challenge. If we had inherent, out of the box tools to drive document manage principles, that would be advantageous for our business.
I would like to see more interconnectedness of everything, including making the APIs a little easier to use, and having bots be able to call other bots and get them to start things. Having all of this a little more seamless would be really helpful. I would like to see more seamless AI functionality built in to allow teams without data scientists or strong data people to be able to build and deploy simple models that will help enhance their bots further and let them do more. The technical support is a bit of a weak point for this solution, and ideally, they can improve turnaround time so that we don't have to figure things out ourselves as often.
I would like a better ability to connect and integrate with other software systems. An example would be integration with data and business intelligence tools. I don't think they have a native connector yet. So, just something that a user can connect, and have RPA in the middle, would be helpful. I would also like to see an easier UI for the user. It may have already been taken care of with Studio X, but I think if they keep improving that, it's going to get a lot of people interested because users are attracted to it.
I think in the Studio, as in building automations, it takes a lot of clicks and there's a lot of options and I think sometimes there's just too much. It should be more simplified on the user interface.
In the next release, they need enterprise connect. That's something we were wondering about. The solution could maybe use more artificial intelligence components or stuff we can start to use in the AI field. It could use an easy integration with SAP. Most of the processes of our company are in SAP. Sometimes it's kind of tricky to automate it.
I would like to see more of the AI Fabric domain feature.
We had some issues with instability for which we were never able to determine the root cause.
In future releases of this solution, I would like to see more packaged solutions. We would like to see intelligence built into the core. Specifically, we would like to see the recognition of human to human conversations. That intelligence would be great because we have some very important use cases in that space that we are seeing. Our focus is moving closer to one hundred percent in that space, as all of our new work is related to conversations. UiPath should offer an on-demand cloud-type model where you can get bots for five minutes, ten minutes, an hour, or whatever duration you need.
I would like to see more machine learning features and capabilities for more accurate OCR.
I really liked the insights dashboard. I guess that there is an additional fee for that. Being able to see your return on investment in real-time is definitely beneficial. We spend a lot of time manually calculating how many hours we saved and that would make it a lot easier. The improvement I want is already there. I have to look into implementing it. The area of the solution that has room for improvement is the stability of the bots. It just seems like we have spent a lot of time trying to fix bots that are down and whether that is our coding or the product. I think there must be a better way to diagnose the issues and avoid them.
The biggest problem that we have when working with this solution is the selectors. If there was a little more flexibility with the selectors, and they were a little bit more adaptive, I think it would be helpful.
Additional help with ROM and approach would be an improvement.
I have identified two issues that have to be improved: * It was necessary to use native PDF rather than a scanned PDF document to improve accuracy. * Templates had to be created for different formats.
Optical character recognition for hand written documents could be improved.
Better alignment of workflows for development is needed.
I would want UiPath to build as many activities as possible. The new machine learning activities in the UiPath AI fabric is something I am looking up to. There are many focused sets of activities and the ability to build custom activities is a great feature and can be made richer. Extending the UiPath studio in terms of UI and functionality would improve this solution. This relates to adding hooks to the workflow/activity execution and extending the UiPath Studio UI with more functionality like a handy tool for activities with icons etc. The orchestrator also can have set of APIs to work with.
I would like to see all a full-featured version for mobile devices. In some Activities, there are inconsistencies between versions where the most recent does not have support for throwing the same kinds of errors.
Making improvements in the processing speed would be a good idea. I have experienced that sometimes during the development of robots, it becomes prolonged and unresponsive. Also, sometimes errors pop out of nowhere for already working simulations. This is not a significant limitation, but it would be nice if these instances can be eradicated.
Active Roles works with policies and access templates, as well as workflows, which are really powerful. While it comes with a lot of example policies and access templates, there are zero built-in workflows. I would personally love for it to come with 10 to 20 sample workflows that achieve a certain task but are not enabled by default. In that case, I would be able to just look at those to see how it's done. I could clone them, copy them, and modify them to how I want them. Then I would be good to go, rather than having to reinvent things from scratch.
We used UiPath Academy RPA training to train 14 people. It was good. I think UiPath needs to do a better job of setting expectations and defining the skill level required. That wasn't very clear to us. We couldn't get a good answer. Therefore, it was trial and error. We were told that people just have to be motivated, but learned that that is not enough. The trainees need to have some demonstrated technical ability. We found that some people dropped out because it was too difficult for them. Other people picked it up very well because they had somewhat of a technical background. That would be my message for UiPath, to give better guidance on qualifications in the background needed for training. One does not need IT coding to learn this, but something within business operations that's somewhat technical. For example, writing Microsoft Excel macros, writing business objects reports, and SQL queries. People who can do those things, they can use UiPath. I'd like to see the ability to operate in a non-persistent environment. Other than that, I'd like to see more intelligence being built in. We aren't using any intelligence yet, but we'd like to.
Due to the sensitivity of my project, I would like a new feature like some sort of generic interface or input where other UiPath users can examine our product or our situations and help us fix them. Some sort of official UiPath community within, where everyone can kind of help each other out.
It was more difficult to use than we originally thought it was going to be. It's not as simple as drag and drop. You really have to have a background in IT development type of work. I suppose you could make simple automations but we definitely found it to be more complex, especially the supporting infrastructure beneath it. I think where the improvement needs to occur is within the federal government to put out the policy that it has been determined to be a safe product that can be put on any DoD network. That would be huge, but right now that decision isn't out there and every agency has to go out and make its own determination. Some CIOs are more risk-averse than others. That would be one thing, but obviously, UiPath doesn't have a way to influence that.
I feel like it's pretty good as it is. One thing I would change is when you're nesting certain workflows, it can get a little complicated as you start getting deeper. For example, if you have multiple blocks that need to live inside each other, and you're using a library to drag stuff or just insert it, it can be very challenging from a visual level to see what level it's in or how deeply nested it is. It's hard to roll it up into a parent level display. So, that's a little confusing sometimes. I guess, if there's any way to improve that, I think that would be helpful. I think UiPath uses VBScript. If there were some kind of library of common things that developers could use, that would be helpful, but it's not a big deal. You can just Google that stuff. Making something like that accessible would be nice, but I don't think it's crucial.
To exceed the expectations, it needs to be easy to debug, not only easy to craft. You need to be able to make it truly do what you want it to do. As a user, you have an idea of what you want it to do. However, when you hit run, it doesn't always do it, then you have to figure out why. That ends up being the majority of your development time. UiPath does pose a bit of a challenge in terms of easy to understand errors, where it's getting stuck, or what was the logic behind the process that we were trying to do from a UiPath standpoint. Making improvements to these would help out a more in terms of being able to make it more user-friendly. Looking to go from structured to unstructured data, then UiPath needs to be able to handle understanding natural language and scanning of documents which are not well-written or visible, in terms scanning quality. These are probably the easiest target areas to improve on first.
I would like more defined processes for around use cases. This might be helpful, as it is more general at the moment.
I have found there to be setup issues with Chrome. Right now, I am using IE. I am looking for more batching processing because of the ODI framework. While they have a process where they log everything into Orchestrator, then they process it. However, when I have 50,000 to 100,000 records being batch loaded and processed one-by-one Orchestrator, I am apprehensive about it.
* Navigating the directory of objects needs improvement. I would like a better way of finding the command which allows you do the thing that you're trying to do. This would help. For example, there was this one command that I was wrongly using for months. Then, someone told me, "You can do that by just using this one command instead of three jerry-rigged together." Therefore, I would like to be able to put in keywords that would allow me to figure out what command will allow me to do the task that I am trying to do. * The testing could be a bit easier. There are error handling steps in the platform tool, but it's not super robust. It's very user friendly from a development perspective. However, from a testing perspective, it is unclear what I am looking at. Maybe, they could add more commenting.
The product has met expectations in terms of ease of use. There is a lot of stuff going on underneath. In the Studio view, there is a right-hand side where there is a lot of configurable components of activities which are built. Some of those are exposed, and some are not. From a stability standpoint, it would be interesting if more of that was power user available. Some of the documentation that UiPath has around the technical specifications, from a security perspective, are very factual and comprehensive, but they don't have an audience, like CIOs who need to approve this solution. Therefore, the documentation is one area where I might smooth the process out a bit, since the audience is different from the way the documentation is written as technical specifications. In a Citrix environment, you can't directly connect to a lot of the applications that you can on a desktop environment, or in a server environment, where it is not a virtual machine and going through a pipe. However, that's just a technical restriction. I would like it if UiPath could watch someone do a process, then builds the bot, but not in a recorder fashion. I want it to watch someone during their day and observe the processes that they do, then provide an informed assessment of what parts of that could be automated. This is because some people do stuff that they don't even realize could be automated, like an interpretation of people's tasks. Technically, that would be hard to do, but it would make a killer application. This make it a product to install on every single person's computer at a desktop level, or every environment, wherever the process is taking place. There is some learning curve to using even the initial capabilities. While there are a lot of great tools to help you get up to speed and learn how to do it, I almost think there are two types of tracks which are only being addressed by a single product: * People who are technical and know the stuff which going on behind the scenes. When they use it, they want to have more access and more ways that they can tweak it. * People who have no coding experience, or low coding experience. In this case, it's great, but slightly limited, in terms of the activities which are pre-built and those are very extensive. It would be nice to have a medium between the two or power user concepts, where you can open up all of the back-end. I do know you can do this in UiPath to access the code and take advantage of APIs, when you get into some of the really complex implementations beyond just send an emails and copying and pasting data from one thing to the other, which takes up a lot of people's time. There are additional things behind the scenes that would be great to have access to with UiPath.
It takes a bit of thought to find the right thing that fits into RPA at this point. However, with the things that we are branching into with natural language processing and imaging things, there will be more possibilities and opportunities. UiPath should continue to grow and integrate with things that we can interact with, particularly with other enterprise solutions out there. They should continue to have out-of-the-box things that we can just take and work with.
It could be a little more aesthetically pleasing. I would like it easier to find things. How it works now: * You look up all the different built-in functions that they have. Most are pretty straightforward. It is click in an open access web browser. * If you don't know the name of what you are looking for, but if you want to be able to do something, then you have to scroll down the page and click it, if it's found. I would like a better way to find the little things that aren't simply named.
The security needs improvement, especially in regards to managing the credentials. I would also like to see better integration with Microsoft products. We still have to test the final product. UiPath's recommendation is build another bot to validate the other bot's work. That is the scary part: If you make a mistake creating the bot, how can you recover from that mistake? A lot of Elastic is not working, which is why the solution is not integrated. While the commercial solution is successful, the government solution needs improvement. Government has so many regulation and requirements that still need to be address by the product.
UiPath could use more OCR use cases to help with those features. I would like to see higher end AI type features natively in UiPath. Some native integration over time would help.
I would like to see some integration, or ease of integration, with APIs, so we can automate stuff faster. E.g., we go through a co-op, which is a card processor, and they have a very powerful API.
A lot of the features that I had been asking for have actually been released. We were using an older version of UiPath and we were having issues with Computer Vision and the OCR engine with UiPath. But now that we see that there's a whole Computer Vision activity suite available, I'm excited to use that. I haven't gotten to get my hands on it yet. But in terms of additional features, I can't think of anything that I would request. I see that they have the AI functionality, as well as the Computer Vision. They have a lot available that I haven't even been able to get my hands on yet. I think once I get some more time to explore the tool and exhaust its capabilities I can look for additions from there. There is some room for improvement in the area of error handling. I had to create a custom approach to error handling. If there were some sort of activity or workflow that could be easily dropped in to help support that, it would be good. Error handling and logging, as well as process logging, would be a big help.
My only complaint is that I hate VB.NET. If I had to pick a language, it would not be VB.NET. That whole .NET framework is just overly complicated. But I can understand why it's necessary for the use case of RPA.
The Academy Live that I took was only a half a day course. There needs to be diverse set of courses for those introduced to RPA for the first time. There are different people who show up to this course: * The developer who is interested in automation and automating different facets of the tasks that they have, either at work or for their clients. * Business managers who want to know more about what RPA can do for my business or company. They want the operational and strategic level versus the tactical level of how do I get automation to do the thing I want it to do? The course was only a half a day, and although we were able to provide two automations and build two bots, it would be helpful if that was extended to include the RPA story and pitch. E.g., What's the story that we need to tell in order to get people to say, "How do I get into the pilot phase now." I would like to have the course do an introduction, "Welcome to the course. This is what RPA is. Now, let us build your first bot." The sales elements of why RPA should be there too: * What is the value proposition that RPA brings to the table. * Here is the expected ROI for a menial task, saving an hour a week equals this in the long term. Even if you can cut a 25 minute task out of somebody's daily routine, this is the benefit in the long term. That wasn't there as much. I wasn't really expecting it to be there, but in the long term, if there are a number of different types of training courses which are offered, people will have different breadths of understandings of RPA can really do, e.g., it needs a hardcore developing training and a capture manager. It needs to explain what sort of things a capture manager needs to know. Maybe not necessarily how to develop the architecture for it, but what does that even mean? For example, how easy is it for me to get Orchestrator onto a server? How do I become a reseller of the software? These are the capture manager responsibilities, and it would be helpful if they were explained. While this is probably more of a day two of a training rather than day one. I would like to see a UiPath user group to discuss issues. I am unaware of all the activities and features, and this would help. Right now, there is just the user's guide and UiPath GO! It would be great if this feedback went back to the UiPath development team. We should also be notified of new features through an alerting system on UiPath GO!
I would like to see some sort of better implementation of the Python modules. Right now, any error code that Python throws up turns into a generic error that is difficult to track down. I would want to see some sort of integration that at least lets me debug the issue. Its pretty difficult to do source control through the typical Git functions because of the nature of the UiPath and the visual element. Some sort of method to bring source control home for us would be very helpful. A way to systematically track which actions or activities were added and subtracted from a given process before adding to a repository would be very helpful to us right now. Our team of developers is growing, so control has become somewhat of an issue for us.
I was providing feedback to one of the UiPath guys here at the UiPath 2019 conference. It relates to Studio, that it only works on Windows. It doesn't work on other platforms. I'm a techie by background. I don't hate Windows but I don't love it. It comes with the limitation that it is completely dependent on Windows. I would have loved if it were available on Mac or Linux or Unix. If it were a little bit more operating system agnostic, that would be great. I'm pretty sure they could be working on that. I used the UiPath RPA Academy. I definitely had issues with it. The quizzes were outdated. Some of the responses that are being rated aren't accurate. I've griped on the community forums as well with a few UiPath folks. That was about five to six months ago. I don't know if they have enhanced it or made any changes since. If it's still in the same state, there is plenty of room for improvement.
Being a person who has held every RPA role from developer to analyst, architect, and executive, one feature I think it needs - from a documentation perspective - is the ability to easily extract variable details and data. They do have a Variables panel that you frequently interact with, but I constantly have situations where those need to be adjusted or I want to be able to present those to a business. Sometimes it's difficult to extract those, and if you're not tracking them while you build, you can quickly get into 200 to 300 variables in use, especially using the RE Framework where you're passing workflow arguments in and out. I would like to see something like that. In addition - and obviously UiPath is aware of this - we have to continue to improve the OCR capability. Computer Vision is excellent. I've used it on Azure. I've created PeopleSoft environments and worked through the Computer Vision feature. It works amazingly in a Citrix environment. But I speak with multiple organizations and a lot of them have the same problem of processing documentation from the mail room or from vendors, etc. That's a huge component. If we can get that embedded in UiPath, so we don't have to rely solely on OCR vendors like Captiva or ABBYY, that would be a huge step forward in being able to service all organizations. There could be improved logging and functionality. But if you truly understand the software, adding logging to what the bot is already doing is as simple as typing on the right line. It's incredibly easy and you can embed it. Even though what it currently logs is limited, it's easy enough to create logs or reporting without a lot of effort. Outside of that, it's really hard to come up with other recommendations. The software is solid.
The stability needs improvement. Within Studio, if you are holding down variable buttons (50 or more), then our entire application slows down. So, basic performance could improve. UiPath could do some optimization of how you search through your process flows. Right now, you have like a small box in the corner, and you don't have an overview when you're searching. Then, you receive this list which you can click around in. That's fine, but it needs to be more visible when you are searching for your components.
I would like better stability and possibly some tools to determine why robots are failing.
We need them to improve the scalability, as we are still building up.
We tried utilizing the virtual environment, but we had some issues in that area. It's one of the areas that we haven't revisited over the last half year because our volume is that high for us. Thus, it is one of those things that we have sort of left on the side for now, but I do hear there is some great stuff coming with it.
While the product is easy to use, it is not easy for all business people to use. It needs to be improved to be like Excel, since everybody should have an RPA tool. So, it needs to be easier to use.
Studio needs to be more user-friendly, maybe it could be integrated with an AI. We want to see more ways that we can use the product. We want to see more actual cases.
We use UiPath only in virtual environments. If it came out of the box like a software as a service, it would be a whole lot better, especially in our case. All our internal systems are cloud-based systems, so we have no dependencies or legacies in terms of installed software in any way. We could be completely in the cloud all the way through. I would like to see direct integration with the Google BigQuery platform. I would also like an Orchestrator self-service desk.
With Excel applications, it is not able to handle a lot of pop ups. It should be able to do this automatically. We just change the format of the file from XLSX to XLS, but it should be able to handle this automatically. Instead, when something pops up, it gets stuck there. This type of thing are small, but still the process gets stuck. I would like to see better integration of applications to avoid these issues. We are also making a lot of manual changes in SAP. We are looking for a solution where we don't have to make manual corrections every time, similar to what UiPath did with some SharePoint websites.
They need to improve features around legacy systems. We currently lack in experience. Hopefully, after another year, we will be more experienced with the product.
I've seen the roadmap. It looks like some of my wishes are in there, such as the debugging of the last X amount of savings before the robot fails. I would also like more script access to the flow of activity, so we can try to see a text version of what we have in the user interface.
UiPath needs to improve Orchestrator and its back office licenses. For example, three or four people logging in on a license should be able to get in, but they can't, even though its Unattended. Why can't we just increase the capacity of the VDIs, so we can use capacity that is there?
There is a very steep learning curve for business users. From everything that I have seen, we still have stuff that we need to figure out on the inside: * How to spin up servers. * How to get compliant. * How to create A/B uses for the robots. It would help to have some guidelines, which I haven't found yet. It seems like UiPath is trying to keep out of the guidance part, because they want to leave it open for us to interpret how to use the tool. I don't even know all the features available yet. I would love to see the roadmap. I love that going forward UiPath is simplifying the roadmap, trying to make it available for development within the business, not only IT.
I would like UiPath to have a build-in method which informs the robot's process owner how it has managed its transactions and performed through the night. If the robot had a process that was set up for a 100 transactions, and two of these transactions had an application error, four had a business error, and the rest were fine, I would like a straight up method for the business owner to login somewhere and see what the robot managed to do and not do. There should be a method for accessing and logging into Orchestrator and see the logs for only one process, and this log should be presented in a way that makes sense for non-technical people.
We would like more API integrations, especially more API connections to SAP. While this is on the roadmap already, activities and packages with more automated API connections to other software or platforms would really help us. Documentation-wise, UiPath could get a little better.
We have looked at it with Citrix, and there are problems with it. Some of the new features coming will address it. We have been looking at Attended Robots, which result in the inability to lock your screen. That is simply a no-go for ever using them in most government agencies, as IT security will prohibit us from using them. If UiPath wants Attended Robots to be used inside a government agency, it needs to be applicable on a virtual desktop. A lot of what is coming is what we are looking towards: Both on the skill set with computer vision, but especially also on the enhanced identity management and security. The ability to debug and lock at a less complex level for us to look at.
UiPath should make the solution part of customer's everyday (more user-friendly). I would like to see the following additional features going forward: * Advanced scheduling * Easier implementation of the robots * Better analytics * Easier non-technical overview of the process.
The speed of development needs improvement. They need to make it easier for non-trained people to be able to develop alterations that work the first time. On the development side, the initial development processes should be a focus. The product is not easy to learn if a person has no interest in the product.
The reporting task needs improvement. The reporting is boring.
I would like UiPath to be more intuitive, so people like me could use it. Usability is its room for improvement. Until the solution is more stable, the robots need to be Unattended.
LINQ and Lambda expressions should be included fully.
* Community * Own software stack exchange platform * UiPath Go! should be more reachable to developers. * Incentives should be given on publication on UiPath Go!
* Linux environment is needed. * RHEL/Ubuntu support is needed * More academy and learning tutorials are needed on Udemy or edX.
As of now, UiPath is headed in the right direction, but in the future, it needs to introduce its users to the field of AI and machine learning. These are the new features that should be added in the next version of UiPath. As for the drawbacks, UiPath should really add an option to change the toolbar options which would make it more user-friendly.
UiPath Go! which is actually a growing store for RPA developers should be more popular and should have good acceptance rate for normal projects rather than industry based projects only.
In UiPath, they already give so many services, and they provide computer vision activity to work with Citrix environment. If they could improve those computer vision activities, that would help a lot for everyone who wants to automate a Citrix environment.
The UiPath tool doesn't provide an option to resize the activities as per wish, especially "if" the activity is a big box.
It could improve the service by resolving the bugs and providing the fixes as soon as possible.
* Everything is awesome; no improvement is needed at this stage. * One word to say about UiPath is, it is simply great.
Data extraction via PDF needs to be reviewed, although working fine with OCR, it still leaves a craving for PDFs with image source.
Unfortunately, the work with PDFs that contain an image still has very bad recognition and needs to be studied for a way to improve this function which is very important for anyone who works with files of that format.
I think they should give a review on the recognition of text in the PDF files. It can not read a whole file, and that delays the work it has too much.
UiPath doesn't deliver on the promise of 'no programming skills required'. It is possible for smaller tasks, but if you want a companywide robot that is a little bit complex, you need someone with programming skills.
When the process is to be automatized, they sometimes don't have specific samples of using functions and commands from .NET, and then, we need some help from an IT specialist.
* UiPath IDE error messages are not comprehensible. * Error messages can be detected by messages from the end user's understanding.
I believe that a better explanation of ReFramework and license costs would be something to rethink.
Due to the heavy load of robot creation, the system gets hanged while starting up the robot, as well as the application startup takes a lot of time, and the validation of licence can be bypassed if the user directly starts UiPath from the system.
Processing PDF images with the manual PDF feed does not work very well.
Improvement in the parsing of PDF files.
It cannot withstand in a situation like overloaded processes execution not up to the mark.
Orchestrator should be free of cost. Now the demo orchestrator gives to access to deploy one or two bots. It should be more. There should be a more graphical log inside it.There should be more click level reporting inside orchestrator
We have deployed the technology for six months. We are facing a major challenge in front of us. The invoice automation can only be done when the invoices are on the website. Usually, we fetch invoices from partner websites as PDF. Thus we are doing extra work of converting the pdf to RPA readable file. If we had dedicated channel of PDFs then it would have worked but it is not like that.
OCR is something which could be improved on to some extent as the result is not very accurate.
There should be some more activities that can replace others where coding is required. You can build a solution without coding knowledge, but I would recommend at least some prior knowledge of the .NET Framework.
They could really improve the advanced training. It is too shallow and makes quick jumps from concepts, and you cannot really learn how to work more advancedly with it.
The features of Citrix related activities could be greatly improvised. The version compatibility or stability issues could be fixed in the coming releases.
Our developers experienced some sluggishness while developing a very large automation. This only happened during automation though; the actual automation was not slow at all while running.
Unfortunately, some things could still be improved. The documentation of ReFramework is very confusing, although there is the advanced course of UiPath, where the focus is ReFramework itself. I believe this is the most difficult, since certification is mandatory in ReFramework, and it is the Framework indicated by the company for the solution of problems.
There is a lot of scope to integrate more AI-based features that will help improve the reading of unstructured data.
* To be more cost-effective since Orchestrator is costly for mid-level markets and poor countries. * To add more challenging automation tasks to overcome competitors.
* As compared to other tools in the market, this is a little costly. * Sometimes the UiPath Studio hangs while running complex processes. * Whatever flows I develop using previous versions, it becomes a little difficult to open the same in latest versions. We need to update all the package which was used earlier.
They should define a yearly baseline build version that would support the next features without having to upgrade all the time.
Debugging and intelligence window. Sometimes it's difficult to debug the code. It gets stuck and closes automatically, or the VDX stops. Might be better if you improve the debugging it has to advantage.
Lack of macOS support this far into the project lifecycle is distressing. While boot camp and alternatives exist, that's another hurdle to cross for client implementation. Additionally, it's hard to drive an open source community and not have the tools to connect with GitHub natively, while promoting paid corporate alternatives like TFS.
Even though the new features of OCR recognition have improved, they still are incomplete and do not recognize some elements. Fortunately, they included an error report system to notify these issues. Also, UiPath has to develop a better way to show us the errors and where are they located in our project files. Finally, it would be great if they add new and powerful programming languages like C# or C++, to have more options at the development time.
When you update to a new version, sometimes opening previous versions solutions become difficult. The packages between versions become incompatible, and when you install a package from another version, the previous one is not removed, causing a startup error. I need a proper guide for versions and compatibility.
UiPath overall is a better RPA tool. But when it comes to the testing and debugging part, it's quite difficult.
I miss a functionality similar to the "immediate window" of Visual Studio. The immediate window is used for debugging and evaluating expressions, executing statements, and printing variable values. The immediate window evaluates expressions by building and using the currently selected project. Therefore, this would be a great facility for debugging using UiPath.
It is not limited to any particular job areas; it can be implemented where the same repetitive rule-driven or data-driven jobs are going without any human intervention or human intelligence.
Debugging features need improvement maybe by providing a process and variable alteration abilities during the debug execution. Additionally, support with version control systems like Bitbucket and Git needs to be added.
UiPath should work to improve the scalability of the operation. While I have not directly experienced issues in this area, colleagues of mine have mentioned that this has been an issue for an accounting reconciliation report they are working to implement UiPath into. The data was very large and the bot ended up crashing while they had ran it.
Improvements from product portfolio could be a product installation in an automated fashion, and support availability should be quick.
I'm from Chennai, and here I couldn't see any classroom training or academy which offers the classroom course.
* Improve the documentation about the tool, since some frameworks adopted by the company/community are difficult to use. * ReFramework, which is the main framework adopted by UiPath to improve the use of the tool is explained in the advanced course of the academy in a very confusing way.
Despite all the good points, UiPath still leaves a bit to be desired with the documentation. ReFramework, which is an adopted community framework, is too nebulous to be understood and poorly documented and presented in the course, causing us to scour the internet for help. Another downside is that the passage of arguments and the number of native commands is not as vast as one of its competitors.
OCR and image recognition are already working quite good. But there is still room to improve when it comes to the accuracy, then scraping of scanned PDFs, etc.
In my opinion, the product could be improved in the area of scraping features like OCR. Sometimes, the success-quote is not very good with these features.
* I really like to see improvement in IDE for UiPath. There is still a lot of space where the user flow could be made more intuitive. * Enterprise support for UiPath is still spotty and is not fully capable of solving queries in a single session. They still require some time to get back on the issue. * I also have a suggestion: Don't try to overburden your product, with the early release of so much integration, with bugs. Do thorough testing, make sure it is bug-free, make sure there is proper documentation and make sure tech support is up and ready with known issues.
The first thing I dislike is it is not available in a Linux environment. I prefer to work on Ubuntu and would have liked if it is available for Linux systems. Secondly, There is very limited content on ReFramework on UiPath Academy. Assignments cannot be done just by reading the text. There must be a demo for ReFramework projects. Suppose you have to work on open source development or Open Source project for a networking community. It requires to have a Bash. You cannot do that in windows. If you are running a script on daily basis for checking malware or something like that on your home networks using Linux (with the support of a GUI tool), you could automate it using UiPath if you had a Linux version of the UiPath RPA. Secondly, when you learn for certification from the academy you have to pass level 3 in between. Which requires a good hands-on with re-framework.The academy lacks practice material for the same.
It could have been visually great and colourful. There are functionalities which need to be added to make automation work much easier like executing a test method by which we can test how the activity will work on that particular browser or stuff without running the whole workflow. For some of the complex activities, visual demonstration of how that activity works should be provided. There are some minor bugs like we could not find the voting option for Outlook mail.
- Arguing between scopes and activities is still confusing. The mode of argument transfer of a scope (or activity) is done by a screen where a variable is indicated as output to which the subsequent activity (or scope) is indicated as input. In large projects, these arguments need to be identified in an easy, fast and unquestionable way. Assigns a variable value to then assigns that variable to the output argument, and then assigns an argument as input to another activity. I think this transfer should be done in the panel of variables and not in the properties of the activity REFramework is good, but still very rigid. REframework is a good template but besides being very generic it is also rigid with respect to error handling. Basically follows the default entry> processing> output which does not encompass part of the applications in RPA, we must remember that the tool is for scripting and falling into the programming vices is a mistake. Overall it is a good way to start processes but during development it will be completely changed
Better documentation of the tool, since some frameworks adopted by the community of the tool is still very nebulous to understand. ReFramework, the main framework adopted by UiPath for better use of the tool is poor explained in Academy Advanced Course.
It has improved the Citrix environment with the introduction pre-release of computer vision which can manage the total control of the image to indicate as a text and all the content. But the OCR engine still needs improvement; it may be in the next release.
On any area, an additional feature that must be included is the AI, with the respective documentation and support.
Only one cons I have seen so far as No Login Authentication: Whenever we are opening UiPath studio, it is not asking for any login credentials. Disadvantage is any one can open the studio and update the code/ change the code.
I would like that in the official documentation of UiPath there were examples of the use of the various activities and that, on the forum were highlighted the resolutions to problems that really work, in order to find them more easily.
Whatever happens, happens for best. So far, it's going good. So, its going nicely to one of its goal to replace desktop support & IT jobs. One concern is robot failure. It may be due to any reason like improper scheduling of bots wrt orchestrator. If bot fails, it impacts business, as it does not meets the requirement in a timely manner, ultimately disturbing smooth functioning of business. (Ofcourse, its a good thing that bot is mostly 100% accurate)
Activities or any feature that can reduce or eliminate code stuff would be a great introduction to UiPath. Also, if more functionality can be added to queue management, it would be of immense help.
Nothing as such, but one thing that annoys me the most during development is, we need to capture images for clicking, and for that, we need to maintain the resolution of that image. UiPath should be smart enough to sync that whole thing up.
* The core product is yet to include machine learning capabilities. * Focus on solving domain-specific high volume use cases to target the major pain points in each vertical. * Simplify the knowledge requirements on .NET Framework for implementing complex automations. * Including additional visualizations on the reporting side would help.
UI automation is perfect, but the scripting part could be improved. Let's say we need to run some scripts on some server, so the command being sent and the response received over the activities could be improved.
There are different webpages for different uses: state, UiPath Academy, UiPath Connect, etc. They should bind all together into a single webpage. So having all in one place would be helpful. And also they need to provide another couple of robots for the community version user for enriching their skill and for learning purposes. And also they need to have sample projects available to help new learns to learn complete automated skills rather than bits and pieces while taking courses in Academy. And there should be a sample cheatsheet provided. UiPath is a simple tool which can be learned by anyone in less than a span of five weeks. If they have provided a sample cheatsheet, it would be easier to follow.
* The ability to search for activity lines in your code in the outline view would be great. Just type, and it would filter it in a way that you could click and jump to it. * It would be nice to have a centralized debugging tool for issues with arguments passing (missing/type) so as to easily detect problems.
* When automating complex projects, the application becomes sluggish due to the interfacing load. * Licensing model is too complicated and has a lot of room for improvement.
The tool is perfect as it is a full-on package, but yes it needs some improvements like when we use the OCR feature of the tool it works, but when we try to fetch the data from the image which is of low resolution, its accuracy of fetching the data decreases. Sometimes the data gets some garbage values added to the data that is fetched. This needs some improvement. Also, if the page has some dynamic background, then fetching the data becomes harder.
The licensing model is for me still a little bit confusing. There are a lot of different license types for the robots, which makes it difficult to comprehend in what case you should use which license type. Most error types are very clear, which makes it very easy to debug the flows, but from time to time some general error messages might pop up (Object not set to an instance of an object), without specific reference, which makes it a lot harder to find the error.
Pricing and addition of new cutting edge features which it misses from its competitors. If the pricing of the tool is reduced, it would be a big sell for the company.
* More training opportunities can be incorporated on UiPath Academy for users * Real life project examples along with Project videos/Tutorials can give a better glance on tool's capability/functionality * OCR interactions video tutorials in real time projects can be saver * Improved Customer support Platform on UI Path Academy . E.g. Ticket Raised Details, Ticket Status Updates, Email Updates etc.
Cost wise and other DB support for Orchestrator.
Selector fails in iterative action so the next release must focus on selector related issue, and also, improvement is needed in its stability.
Debugging has some room for improvement, but other than that everything seems to be just amazing. UiPath is clearly headed in the right direction.
Developers complained about UiPath becoming slow when developing complex processes. This only happens when developing, not when running the automation, so we solved this by boosting developers laptops with more RAM.
* For data scraping, the websites which have iframes are not extracting properly. * Also, the API generation in UiPath is not that much easy. It would be nice if we have an activity which easily converts a workflow into API.
Sometimes when working with operation leads, it’s hard to get them to focus on the concept, and also believe in the concept. For approval, it should run through all of your company’s major departments, ranging from investor groups to operation floor leads to finance to management. Processes that will be affected by the RPA should all be consulted as well, and all departments should be considered in the RPA implementation process.
It is very expensive to acquire a UiPath license, and this cost makes it not so easy to profit from the automation.
* Compatibility with old systems and Java Script-based websites could be improved: During my project, I sometimes encounter issues when Uipath runs too fast while our old internal website (which was written in Java Script, I believe) is running slowly and we need to handle this type of error. Besides, some function of Uipath "Select item from list" does not work with our website (not compatible). * More practical projects to be included in the training of UiPath Academy would help the business users to get used to executing the real projects (e.g. technical issues: why do we have to write the script this way, what errors usually occurred? and also project management - setting up timeline for the project, etc.)
It is not compatible with some of the old windows applications. I am dealing with the clients who still use 1990's power builder applications. The UiPath is unable to recognize the elements of the applications.
The product and its documentation are very easy to understand and helpful, but I found some difficulties when dealing with the licensing. I hope they would make that clear as soon as possible. Then next thing to improve is the option to add activities into the work pane without using a mouse — actually, via real coders like keyboards only. So, adding more shortcuts would be helpful.
Typically, the best improvement of Microsoft tools embedded (as for Excel), and SAP could be very useful (but in 2018.4 there is an improvement on SAP BAPI).
* Debugging mode has room for improvement * Sluggish to develop when several XAML files are open * Price for large projects.
* Price could be an issue for large projects, but that's where you'll get a high ROI too. * The collection of applications supported can grow, but we've seen it's happening in the last versions.
* Provide detailed and prescribe 'Debug Mode' i.e Run from step like other debugger and Very useful 'Simulate click' needs to make more stable in next version. * Cognitive and machine learning features should add to make intelligent automation in Uipath.
I think debugging is the worst part of UiPath. Compared to some different RPA tools, this is not the best, but it's still not a problem to troubleshoot any issues that you might have while creating a flow.
Image resolution affects Citrix automation. Means, the resolution of BOT system and development system should be same in order to successfully run Citrix automations. This drawback is getting resolved in Computer Vision backed selector automation feature for Citrix in 2019 version of UiPath. Also, unknown runtime errors mainly due to application integration issues can cause issues, although it's a very rare scenario. This issue can be resolved to a great extend by using RE Framework in your development, which is also integrated in UiPath in the latest version.
So far, UiPath has been good in every area. I would like to get more features in ML-related activities. ML will be the future for processing free text. Like for example , while processing free text from the customer comments, using uipath we cant extract the required data from the free text. Incase if you got ML related activities then it will be easier to provide the solution using UiPath
* I think it would be good to add more activities regarding operations on data tables. * The product definitely should be improved in the case of throwing more accurate description of exceptions.
Engagement during the proof of concept period could have been better in regards to the implementation and follow-up. Also, after completing the PoC, we should have done a review of the critical learning and aspects of the application to determine the next steps based on the objectives of the company.
* It should add the feature of intelligent automation. * Also, to interpret human decisions using Amazon Alexa as well as machine learning.
* Adding a "goto" feature * Adding "run from this activity" * Logging events/warnings to log files in order to follow the execution * Simplify Orchestrator.
While running the code, if we want to pause it we can't, so it results in some exceptions for attended bots.
What I really don't like is some bugs in UiPath appearing from nowhere. In the new version, I see most of them, like when you are trying to change your variable name, it gives a very long error, etc. But still, there is one area not fixed: importing Outlook templates. I had an issue with implementing ".oft" files reading with "Microsoft.Office.Interop.Outlook" library. It was a real disaster; I couldn't define anything. I spent quite a lot of time implementing it, and I reached the conclusion that it is very close to impossible to use. They should direct activity for outlook messages and "oft" files. Except for that, UiPath is a great tool for automation. Also, debugging is not very convenient. It is hard to debug with UiPath if you are running a very big process.
I think that a great, nice, must-have feature should be to allow other languages to invoke code blocks beside for VB.NET. I'm confident that this feature can empower more developers to perform tasks and activities that other tools do not support.
There are still a lot of things that could be improved, like the identification of elements on the screen, the error handling, etc.
The abrupt updates have been an issue for me at the time of developing my bots. I've been getting errors every time an update is made, slowing my developments and automation. It will be good if they could start sending an email to the users letting them know about future coming updates so they can be prepared. Also, having up-to-date training material would be really awesome, we have found that some documents inside the Academy are pretty old (maybe 2 yrs already?) So it would be awesome if they could have those up to date.
Some areas where this product can be fully implemented is finance, invoice generation, and the work which has repeated tasks.
* UiPath’s reluctance to add the support of C#/.NET code till now. * The UiPath tool doesn’t provide an option to resize the activities as per wish, especially if the activity is a big box. * Non-availability of maximizing options in the property edit box, argument value edit box, etc. * No option to mark a set of activities as favorites in all projects done in a system. We have to set favorite activities separately for each project. * The comment option could be better. When an activity or sequence is commented on, there will be two wrapping sequences which are unnecessary. * Also, the display name is always the same, the display name of a commented section should be the display name of the sequence or the display name of the activity itself.
I would like to see periodic updates to activities and maybe new packages of activities. I also like the mobile Orchestrator, but I think it should be made in such a way that the user can create/update robots, processes, and queues.
* Citrix automation * Work management * Repository of authors for implementing any changes in the code * Improvement while navigating in Orchestrator * Include export job records option in a different format.
Handling if-else statements for schedules. It would be great if it had elements which could take care of running the job.
* Some features feel a bit buggy, and older versions are prone to crash. * Double screen support would be nice. * More AI and ML support.
* Third-party version control is very important and needed. * Better support for invoking code could also be used to enhance development. * Cannot go wrong with adding inbuilt data analytics.
* Financial. * It should be improved in such a way that the objects used in the designs should not be updated with the installation of new versions of UiPath as it happens right now.
Making variables easier to find, perhaps integrating a "recommended variable" section for functions, and to filter variables better.
UiPath is experiencing some growing pains in their support at the moment (some of this is due to the rapid progress of the tool, I suspect). From our timezone (GMT+10), support expertise has always been a bit of an inconvenience, with the best staff only coming online after our work hours.
User access management - to be able to set up user rights in a more sophisticated way. In the current version if you grant e.g Execute access to a user it can execute all robotized process in the given environment, you cannot specify the right on a process level.
There are no cons I found in this tool. A free license would help everyone to learn about this tool.
The solution architecture should be reviewed to offer more opportunities to small companies or small entry level projects. For example, they could accept SQL Server Express Edition or other open software database engine; and allow all components installed in only one server, at least up to 10 robots.
In the next release, I believe it should include cross-platform features. Like if our product is developed on Linux, then it should be capable of running shell scripts.
* An easier way to use object-oriented languages * Better version control with different features * Git integration if possible.
* The UiPath could improve in the AI part so that we could build more powerful robots. * It will be helpful if we could have a diff for better version control.
2018.3 and 2018.4 releases made a huge leap in terms of functionality — we're not missing anything currently.
UiPath comes with an infrastructure suitable for development. It may be a disadvantage that the simple coding sections in the studio environment are with Visual Basic. Nowadays one of the most widely used languages can be supported with C#. Furthermore, it is possible for robots to interpret the information obtained from repetitive operations by machine learning. This is a situation I believe should be directed to the field of artificial intelligence.
* Image recognition could be improved with more AI that identifies what objects are in the pictures, as example if we think about future about uipath, captcha reading , like if we given few images and find what are the picture that cantain with car * also If we scan any images , possibility of identifying this image contained pen, book,tea,cupboard, cake ....like that * Also, speeding bots may be good for some companies because some processes don't need to be viewed while executing, so if the bot can run faster than we see, it might be helpful.means that generally bot can run with their default speed and the application speed that its interact with, if the application support any speed eg(typing speeds) uipath should perform or having facilities to speed up the bot that its processing
While doing Citrix automation, the image identification and accuracy should be easier. Easy work-related activities for Citrix is the one thing we are requesting for in upcoming releases.
Some more features for the newly developed mobile version would have a great effect on the future of the product.
When using UiPath Studio sometimes I felt lost when trying to locate specific activities, so probably will be a good idea to improve the icons beside the activities, so I can remember easily.
* The product could be improved in managing clients from Orchestrator. * I'd like to find in the next solution the managing of Studio license from the Orchestrator server.
* Provide a robot as a service model (subscription for the platform services) for partners to provide more chances to SMB to compete enterprises. * More cognitive services from Google, AWS, Microsoft, integrated into the platform provide wider capabilities for developers and service providers.
More support for certification is needed to attract professionals. The certification process could be made more interesting.
This solution needs improvement, especially in terms of continuing the process that is left in case of any kind of disaster that happens to the trimmers. If there is a state that can be maintained to removing the machines to another location and continue from there, it would be helpful. Right now, this is lacking.
We are not able to extract the data from the same type of PDF which is bulky in number, and scrapping is not so good.
I think the only issue we have faced is with the upgrade compatibility.
I met a lot of customers that didn't have big business processes. Some of our customers are rather small. They have fragmented processes, and they need to automate some tasks. Sometimes they are not big enough to justify the investment of the infrastructure and everything around it. Attended automation will allow them to target smaller opportunities. This is something which is very appreciated by the customer, to do something small, to grow incrementally. Then you can scale. Attended automation is definitely something that the customer wanted. I think UiPath understood that. Attended automation was possible before but was reduced and not focused on. If you look, even on the academy content of UiPath, there is not much attended content. If you look on the Advanced Training, the Advanced Training is about having back office robots, I really looking forward to seeing enterprise grade attended content. I think this will be really something interesting. The feature was existing, but I think now it will explode.
I think from a feature functionality point of view, it's an evolving product. There will be more features added. Every product is going up. I think from a UiPath perspective, it is evolving as we speak. But I think where it could really improve is being able to create a development platform that is easier to use. Today, as an end user, if I have X number of developers, each of them have to have a studio environment to be able to use. Typically, that's not a license model. But if that is more easily accessible to the development teams. Without constraints, it would be easier for us to use this platform more widely among our customers. So, I think, from a licensing point of view, studio environment should be more easily accessible. But other than that, from a feature functionality point of view, I think it's pretty comprehensive.
We've had some serious issues with clients that are running in Citrix environments, and we've got a couple clients that have moved away from other competitors to UiPath and to us because they just cannot do that screen scraping technology. Yeah, we're finding a lot of it in a Citrix environment, and a Citrix environment, on an Azure cloud, on a virtual machine. So there's various steps, and UiPath's the only one we've found at the moment that will actually enable us to deliver that. I think the AI question is being raised everywhere, and there certainly needs to be a lot more intelligence involved in that. The ability for the robots to start thinking for themselves is coming out in the later versions. There are very few limitations at the moment, because we tend to pick relatively mundane, tedious, repetitive tasks, and it's all about number crunching. Really, RPA globally is all about number crunching. But in the next six to 12 months, there'll be more intelligence added, and there'll be more stuff going on that brings it closer to the AI environment that everyone's spouting about at the moment.
One of the major things that we've been looking forward to is around project dependencies. Previously, it's not been possible within a product to take a reusable element and deploy it as a live based piece of content, but that's now been chipped within the product. So, we're extremely excited about seeing that in there because, from our point of view where we've got many clients, that re-usability of our own intellectual property across them is going to really see some benefits for us.
We have seen issues in the past, but we've also seen the actions that it can do to correct them. For example, it's just one color change or the place of a button in an application change and so on. I'm looking more at the potential of this product, so looking back, we had support for everything that was needed, our small issues were fixed, but now I'm looking at the roadmap that UiPath has for this product. I can say with confidence that is a future proofing investment. I mean what other technology would come out and then bring business value.
I think it's a little bit early to say at the moment, I think UiPath are ahead of us in our thinking at the moment, maybe in a year's time we might have areas where we see gaps but at the moment, everything we need I think is there, out of the box.
* Linux support * Better cloud integration and stronger auditing for governance. But overall, this product is excellent.
I would like UIPath to improve the OCR visuals. Also, I wonder if one day the automation tools will be able to make simple decisions by themselves.
* HR and finance in IT and telecom business * Improve the ability to change the user interface or application functionalities.
There are a lot of solutions in UiPath where we have to know some programming languages. I'd like to cut some of that out, with features that perform those tasks without having to know programming languages. I work a lot with my team members who don't really know programming that well, and I have to walk them through how to do different coding things to effectively develop their RPA.
The new release broke everything, so I'd like to see that not happen next time. All of our automations broke. It happened to one of our centers of excellence. They just upgraded, pressed next, next, next, and probably didn't really go for the due diligence that we put in place, which is to do a controlled release. I'd also like to see more machine-learning functionality. I'm really excited to see what's actually on the agenda. There's some really strong stuff about machine-learning being adopted. Unstructured data, robotics being able to read unstructured data, is really one of the strong cases for us. That's likely where we'll be going.
The Citrix automation - the way that it's fragile right now - if that could be made stronger and more stable, that would be icing on the cake for UiPath.
One of the things that many of our clients ask us about is security. Some of them are really struggling with how to do multi-factor authentication. A robust and solid approach for dealing with multi-factor authentication would be one of the things we would like to see. Also, some of the IAM tools have features that have somewhat segregated duties. For our clients, this is a big challenge in terms of how they do SoD. If there were some features related to SoD that were added to the tool, that would be really great.
I would like it to better handle updates from other systems, whether it's SAP or a website. That's the thing that we struggle with. Anytime a system changes, we have to go in and modify the code.
It's easy to use but I think it will be a lot easier as it continues to develop. Right now, we do need some development capabilities, to understand certain computer languages, to put in the bots. They're on the right roadmap to make this even easier to engage so that anyone, even people without programming language experience, will be able to use it. I would like them to continue to build and make Studio easier to use for non-technical people.
With every product that we have, there are still improvements needed in some areas. There are certain areas that we need to see improvements: performance, efficiency, and complex environment. We need to work with the product manager on these, and say, "Now that everything has met the industry standards, there's a way to go." We need to be able to span across a bigger complex network. Right now, the decision-making is based on a five step rule. It would like to see this increased, so we can take on bigger productions and work more efficiently. Also, the performance has to be improved in some areas.
Once we've taken the data that the robot has done something with, we want to send it over to a human a lot of times. However, they need it formatted in a fashion that makes it a little more readable. It would be nice to have some activities without the developer having to do a lot of effort to make the spreadsheet look prettier. Instead, we should receive a list every time transactions are performed, and it would be nice if we wouldn't have to format it every time the robot sent us a spreadsheet.
Ease of use could be improved. The newer features are easy to use and positive additions, but there is room for improvement, specifically of the UI console for the developer. There are also other features that could use improvements. I would like to see the OCR, machine learning, and cognitive package that is being discussed in the next release.
I would like to see more integration with solutions, like SAP, especially because the biggest companies have a lot of SAP implementations going on. If they would have more packages to support native SAP activities or perform connectivity to some of those SAP clients in transaction codes, it would be awesome.
* We would like to know the prerequisites when installing bots. * A bot that could provide feedback would be nice.
We would like the RPA app that we developed to fall back to one of our APIs and Visual Studio and have that take off. However, I was talking with one of the guys at the conference, and he says, "It'll do that."
Managing the infrastructure UiPath is running on is a lot harder than it seems. In the app development world, there's things called Docker containers that sort of help you containerize what your thing is running on, then it is in code. If we could get that, it would go a long way. Otherwise, I will have trouble scaling, because every time I scale, it's another manual setup of the infrastructure. I could automate that too, but the right solution is to have this working in containers, not a bot running around getting rid of pop-ups, and installing and uninstalling Chrome. Working at an enterprise is harder, because we have security concerns, infrastructure, and governance. So, how do you create these virtual users? Because now someone has to own the credentials, but that's an anonymous user who has access to the credentials, and they have access to systems. All of this stuff is hard.
I want to improve machine learning.
You can't write small snippets of code. If you want to do a single code snippet, this is not available by default. For example, if I want to do some date conversions, and that date conversion requires different variables to be available in the context, but they are not there. A small snippet of code change should be available out-of-the-box. This will help me in the long run. I can create activity out of it. Support for a little bit of in-line script should be there.
What is the bottom line?
Let the community know what you think. Share your opinions now!