The most valuable aspect for myself was access to the .net framework. If I couldn't figure something out using the objects that they had provided, I could bring in the .net objects and do so using similar logic that I would in a .net or C sharp coding language. Having that familiarity was helpful.
Robotic Process Automation (RPA) Framework Reviews
Showing reviews of the top ranking products in Robotic Process Automation (RPA), containing the term Framework
Pega Robotic Process Automation: Framework
Automation Anywhere (AA): Framework
It depends on how you develop it predominantly. Because it's not judged just by saying that it's not stable or anything like that, it's how you develop a framework and how you do it. That's how. From my experience, we have a good number of developers. On my team's, we have around five to six members who are working on this process. We have created a framework in such a way that we don't miss anything. For the past one to one and a half years, we haven't had any post-production issues. The amount of human errors that have occurred have been reduced to around 15 to 20 per person.
The solution is pretty stable, we didn't face many issues. Once the instalation is done the control room core architecture wont face many issues.there are quick fixes like service restart if anything goes off. but most of the time we hear AA support suggesting us to reinstall with the new version of software for performance issues, but with my experiance i hardly see that making huge differnce in fixing the actual issue.
Monitoring can be done through email alerts for the core infrastructure. Issues mainly in HA(High Availability) with cluster sync issues still not monitored at the dashboard level, which might be a concern if the cluster goes out of sync. At the bot implementation lot of things are dependent on the way we code so it's additional work for the developer to get the code keeping in mind all the events which might happen. I would have been impressed if the solution had framework at the control room level to keep track of the overal execution and transactions, hope they can bring that feature in future releases
reviewer1452870 says in an Automation Anywhere (AA) review
Associate Director - Projects at Cognizant
Sometimes the tool is timing out, which would be a good thing to have resolved.
It will be good if we have a framework that is created with the package, so we can leverage those for the multiple processes. As it is now, we create a base framework.
When we have more packages for each of the basic operations, it will be more user-friendly and easier to complete, rather than starting from scratch.
Ideally, when we have those packages we can leverage them for overall project development. Adopting the cloud platform will be more convenient, as opposed to depending on the on-premises setup.
I would like the AA tool to be more proficient and a single entity tool that does not require DLLs or some script to be written separately where it is not capable. It should have more commands, which should remove the dependency on MetaBots or other scripts so that everything is available in the tool itself. This would save time.
All the time working on the tool requires internet connectivity, and it will be great if we can work offline. Offline development would be helpful.
More features like AI and ML should be included, as well as additional features to automate Citrix applications and mainframe applications.
I would like to see more Excel commands available.
Introduction to dictionaries and other data types should be included.
I would like to have a ready-made framework available so that less time is spent to develop the whole framework for the processes.
In terms of robustness, the bot should be efficient enough to deal with the code breakdowns. This could be done with more exception handling features and a ready-made framework.
More tutorials with complex scenarios and ILT training would be an improvement.
I am sure AA is pretty stable.
Now that it's on its own framework, I am positive about the stability. At any point in time, I would preferably suggest sticking to the initial platform and framework that people like the most providing an overall package.
I believe Automation Anywhere is working perfectly and it is the best in the market. However, some points based on a development perspective I would like to add are:
- Universal search.
- Creating a variable from anywhere, including from the properties/attributes of commands.
- I would like to have the ability to delete multiple variables.
- It should be possible to delete multiple parameters for the API.
- I would like to have commands to link with the respective knowledge base.
- Having a refractor in the code would be an improvement.
- A predefined framework for Bot Development that includes an audit log and error handling would be helpful.
- It would be useful to have some updates for the control room in terms of analytics.
Automation Anywhere is the best automating tool on the market and it's very difficult for me to think to suggest something to improve the tool.
Here are my few suggestions:
Automation Anywhere can include database commands like insert row, bold row, etc commands in 11.x
They can also include features like API integration features in the command panel.
They should create a standard framework like re framework in Ui Path.
As it enhances the capability of the developer to create an automation project.
We have use cases that include cognitive as well as non cognitive requirements. IQ Bot is widely used across all the use cases. We are also looking forward to make use of the Excel ribbon and AARI framework.
One of our use case needs is to extract data from KYC documents and then do the validations to submits the rejection reason.
Another use case is to read customer information for FD booking and validate the customer data with the system's data and book the FD in the specified amount of time.
Similarly we have around 12 use cases for the development/UAT.
reviewer1681449 says in an Automation Anywhere (AA) review
Software Engineer at a tech services company with 501-1,000 employees
The most valuable feature is the SAP application and the DLLs that Automation Anywhere provides. These DLLs help automate the SAP application. In A360, the latest version of Automation Anywhere, they provide many connectors for the different frameworks, like Office 365 or any other APIs, so those connectors are useful.
Blue Prism: Framework
Blue Prism is lacking in document processing capabilities.
The addition of better testing tools, or some kind of test suite, would be an improvement.
If this solution had a framework for exception handling then it would be very helpful. As a developer, we have to put exceptions in as the first step.
This product does not have AI Fabric or process mining tools.
reviewer1542615 says in a Blue Prism review
RPA Solution Architect - Lead Developer Individual Contributor at a tech services company with 51-200 employees
It's beneficial that the solution is object oriented so you can create objects. In larger projects, where multiple developers are involved, it's hard to develop tasks and RPA platforms. With Blue Prism you can create a process. For example, automating data validation, which would be a framework where you can assign an object developer so they can work in parallel, enabling project completion in a shorter space of time.
I would rate its ease of use as about four out of five. It's not so easy, but it's also not difficult. We have a great UiPath Academy and it's really useful and helpful. Sometimes we need to do difficult operations and use other frameworks, through activities in UiPath. I think this mechanism is very nice, but in implementation, the customers are pretty close. Sometimes we must do it.
This solution helps to eliminate human errors. The amount depends on the process and the customer. Even unattended robots don't provide 100% automation. Sometimes a robot interrupts and waits for a human to make a decision. There is a process when unattended robots do fewer steps and after ten interruptions are waiting for a human to go on. I would say there is about a 70% reduction in human errors when using an unattended robot.
UiPath also helps save time. One unattended robot works 24 hours a day because a robot doesn't get ill or need to sleep.
The initial setup of this solution is straightforward. It just works. You download it from the cloud and install it on your computer. You might have to update your .NET framework, so make sure that it works. It is very visual and very intuitive, so you're up and running in no time with Studio. With Orchestrator, it takes a little bit of getting used to in terms of matching up Orchestrator with the computers that it's linked to but it took hardly any time for us.
reviewer1214574 says in an UiPath review
Senior Manager at a financial services firm with 10,001+ employees
I like the layout and design of the Studio using the RPA framework. It makes sense to me. It's very easy to get started. I've been a fan of the current debugger. I know that UiPath is releasing an updating debugger but I think that's been very intuitive for me as well.
I would rate the ease of use of the platform for automating my company’s processes a four out of five because, for me, there's still a lot of clicks and keystrokes I need to do for development. I know that UiPath is releasing StudioX, which is something that is needed, for people like me who aren't super technical.
I would rate UiPath Academy RPA training a five out of five. It's one of the best. Compared to its competitors, it's intuitive and it's robust.
It's everything that UiPath is moving forward towards, intelligent, machine learning, and AI. I embrace the fact that the direction it's going especially for me personally.
It probably took us about nine months to deploy, from the initial UiPath license to implementing the first robot in production. The reason for that is the learning curve of the team as well as the education across the operational teams to bring them up to speed and make sure that everyone's on the same journey. We were also working very closely with IT to make sure that we've got the right infrastructure in place, as well as support models, governance frameworks, etc. Without it, you can't really get anything done. It's a new technology and it was a new concept for everyone. Needing a robot ID, for example, was something that was never discussed before. Lengthy conversations had to be had to make sure that we weren't putting anything at risk with data privacy, for example.
The setup was both straightforward and complex, really. Some bits we're quite straightforward, but other parts were more complex. Especially the infrastructure we're still dealing with now one year on still has some complexities. We're still thinking about credential management versus the use of virtual machines and whether we should be using high density or not. There is also the matter of all the different types of offerings. There's a matrix that you have to abide by and I don't think UiPath is even aware of all the conflicts between the different options. That's something that we're still working through right now, but I'm sure they're going to address it.
reviewer1214562 says in an UiPath review
Automation Delivery Lead at a pharma/biotech company with 10,001+ employees
We are using Studio, Orchestrator, attended and unattended robots.
Our primary use for this solution started with automating processes in finance, procurement, and HR. Now, we are researching various directions in logistics.
We do not run our automations in a virtual environment. This is something that we are trying to avoid.
With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a four. I'm an IT-based person, and for IT people it is easy to learn. UiPath claims that it is easy to learn and it's for everybody, but it's not true. For business people, it is hard to learn and hard to understand how to code to make things work. They need a lot of help with things like exception handling. If somebody lacks technical or programming skills then it makes it much more difficult to use. Although UiPath is getting closer to business users, there are still some basic skills that they need to have to make it work.
On a scale of one to five, judging how beneficial it is, I would rate the training a five. When I get new hires it doesn't matter whether they have previous experience in RPA or development, they have to go through all of the basic training from the Academy. This includes the Orchestrator and I've been recommending SAP training because we are experiencing growth in the use of SAP. Going to my team, this is the base, and then we have created our internal framework and standards that also require training. Some people may already have experience with UiPath or Blue Prism, but they still need to take the training from the Academy.
Before I arrived at the company, there were already some automations running. However, fifteen months ago we shut down a couple of robots because they were failing terribly. From that time, it took us five months to create the first robot.
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 are using Studio and Orchestrator.
Our primary use case is automating data processing for clients translating into other systems.
We do not run our automations in a virtual environment.
With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a three. I think that the technology that we use in the printing industry is a little more difficult to automate.
I am currently involved in the UiPath Academy training. We have third-party contractors who have been doing the development, and I am the first internal employee who will be developing. I find that the training is good in the first step, and also in the second step where we're learning about Orchestrator. However, when it moves to the third step and they are talking about the framework, I think that it is a pretty big leap and that is where I'm struggling. This is the section that I am in right now.
There was one project that was completed before I started, at my understanding is that from the point that we purchased our UiPath license until we had our first robot was less than six months. For my project, it has taken two months.
The workflow was able to handle the exceptions gracefully. The solution followed the ReFrameWork template of UiPath.
clientac994590 says in an UiPath review
Client Account Manager at a tech services company with 10,001+ employees
This solution is intuitive, user-friendly, and has a specific framework that allows for quick robot deployment. Most of the time, all you need to do is simple drag-and-drop, which allows regular users to interact and work with the solution to create their own robots.
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.
We use UiPath for:
- Financial domain
- Excel automation
- SAP automation
- Citrix automation
- Usage of Orchestrator queues
- RE framework
- Automating password resets
- Security and governance
- Rule-based exception handling
- Large group deployment
- Centralized repository for version control
- Execution logs and credentials
We are using the RE framework and it's very helpful for delivering the product on time.
The image-based automation is working as expected, using different levels of accuracy.
Orchestrator is the feature that allows making use of robots for remote location systems. The work queue is the added advantage to maintain the bot data.
The inbuilt RE Framework makes development easier and fast.
UiPath helped me to automate the various complex and mundane processes. You can also run your Python and .NET code in UiPath, which makes the development easy.
The UiPath interface is very user-friendly and also it is easy to learn and use.
There are many online certifications in the UiPath Academy, so it helps the user to become a certified developer and learn everything from the online courses.
Support from the UiPath community is very good.
RPA - Novigo Automation Framework Solutions - Setup an Automation Factory Model.
Automation Focus has been Productivity, Quality, Cost, Process Optimization, and compliance.
Focused on delivering Process Automation for Oracle EBS ERP application for various departments including IT, Finance, Operations, Engineering, Sales .etc
- Manufacturing: Master data maintenance & monitoring Inventory transactions, BOM error fix & transfer, WIP issue & complacent
- Finance: Financial closing, IC transaction, security & FA master & transactions, Master data, duplicate check, auto-CM creation & auto-payment, Customer Master, running letter, print errors & auto-receipts
- Supply Chain: Sales order Integration with the portal, shipment, RMA, digital shipping & backorder, item cost update & inventory interface, procurement, receiving & monitoring
- System Admin: Access provisioning, - Creating responsibility, Monitoring pending transaction & analyzer.
UiPath Studio is great. It has all the activities. You don't have to write anything. Even after that, if you feel that you have to do something for yourself, then you can write your on-premises code in it and develop your own framework. Everything is there. You just have to use UiPath Studio.
if you are a business user, even if you don't have a technical team, you can install the second version of the Community edition, which is StudioX. This is specifically made for business people who don't have a lot of ideas about technicalities. This is a great feature.
The best feature in UiPath is their robotic enterprise framework because that is an inbuilt processing framework for utilizing their work queues. It's plug-and-play, and already pre-built to where you don't have to start from scratch. It's enterprise-grade and ready to be used. All you need to do is populate your dispatcher, create a queue, create a performer, and you're good to go.
The highest benefit of it is that it's just there, ready to use, and you don't need to start from a blank screen. You don't have to figure out, for example, how to create an environment where the robots can check if there's anything in the queue to be worked on. The framework is already there. The other tools that I've used, like Blue Prism, don't have that built-in quite as well.
My perspective and overview are from that of a developer, and I find that the recorder feature is really good. This is because UiPath lets you record your actions on the screen. So, if you want to interact with a web-based interface, for example, then you have UiPath record your actions and then build the activities that you would need in order to replicate those actions through the robot. It makes it a lot better and although it's not perfect and it does need to be reviewed and adjusted, it speeds up development quite a bit. This is especially true when it's basic back development like populating fields and clicking buttons and navigating on a web.
Compared to other RPA tools that I have used, something that stands out to me in UiPath is that it has a very extensive library of activities. Those activities are easy to search for and use.
When you are writing code, there is a feature called IntelliSense, which autocompletes your code. More specifically, when you're typing code, if you're starting to type the name of a variable, it will show you all of the variables available and you can just click them. It's very interactive and it's reminiscent of the Microsoft Visual Studio environment, both from the UI perspective and the coding perspective. This means that developers that are familiar with Visual Studio will probably feel right at home using UiPath. It's very developer-friendly and it's geared towards appealing to existing developers.
The UiPath Academy courses definitely help in the process of bringing employees up to speed. The Academy is the go-to place for UiPath learning and I think that other RPA tools are copying this model of disseminating knowledge, being a lot more open with training, making it freely available, and providing an online classroom. These are things that UiPath has always done, and it certainly helps new developers get upskilled in RPA, and specifically with UiPath.
When it comes to ease of use, UiPath is intuitive insofar as the basic features have a low learning curve. However, if you want to take full advantage of what UiPath can do, and if organizations want to create more sophisticated automation solutions, it is more difficult. For instance, automations involving back-end access, maybe writing directly to databases such as SQL or using API, that's a steep learning curve. In fact, I think the learning curve is exponential.
If you just want to make a robot that sends an email, that's really easy to do. But, if you really want tangible benefits, like if you really want something that solves a business problem, it is a huge learning curve and it takes a while to master. Obviously, it does have that low-code requirement, but I would say that's only for entry automation projects, like proof-of-concept or something along those lines. For something that really solves a business problem, you would need code, because that just makes it a lot more robust and a lot more powerful if you can custom-code certain steps of the process.
reviewer1510449 says in an UiPath review
RPA Developer at a maritime company with 1,001-5,000 employees
We invoice every month quite a substantial amount of money to our customers. We saw a problem in that about 20 percent of our invoices were sent to the wrong addresses. That meant that, at month's end, when we were expecting money to come in, we would be missing around 20 percent of our cashflow that month. Of course, we wanted to prevent that because 20 percent of the cashflow of $300 to $500 million a year is a lot of money.
We have automation that runs every night through all our invoices. Because we have some problems with our master data in the company, it does a number of measurements, on whether an address for an invoice seems to be the correct address, and a number of checks, such as, what ship was the goods delivered to? After that, it looks up information through the international registers of ship ownerships, then it will do a number of checks, giving each invoice a score as rating the probability that the address is correct. If it is below a certain threshold, then we will do some manual processing, and we are looking into UiPath Action Center for this. For four or five of our largest branches in the US and Asia, we have seen a significant improvement in the payments at month's end, which has definitely improved our cashflow.
The administration is a SaaS solution, which helps to minimize our on-prem footprint. The only things that we have running on-prem are the machines running the robots. Everything else is handled in the cloud. We don't need to worry about backups, etc.
We are adopting as much as we can some of the things that should reduce the maintenance costs. We are using Robotic Enterprise Framework in our development and Automation Hub to sort of qualify our ideas. So, we are trying to implement a uniform way of doing things throughout the lifecycle of an idea. UiPath supports this fairly well, and I think it will get even better.
The stability is pretty good when we follow the best practices, i.e., whatever is in the REFramework.
The most valuable feature that we are using is UiPath Apps because it makes it very easy to implement tasks. It is very easy to scale operations, which is important because we're not talking about just five or ten agents. We're talking about 1,000 to 2,000 agents. The Apps feature helps us to scale very quickly and very easily. We only need to develop one or two bots and then link them to UiPath Apps to process everything. All of the integration between the bots and the human, along with any scheduling that needs to be done, is taken care of by Apps. In our situation, the Apps feature is the best solution to handle this scale.
Utilizing our bots is very easy, and it is done using the licenses that we have with partner UiPath. We can access our licenses, then distribute them to the customers and we can use them dynamically. This is all done in a very easy manner. We just have to navigate to the web-based hub, where we have access to everything that we need.
UiPath is highly customizable and this is helpful for us because we can develop models and frameworks that can be reused for different tasks and different customers. For example, if we have a customer with a process that is very similar to one that we have previously developed for somebody else, we can reuse the models to scale the bots. This makes the new development very easy and very fast.
The Agent Console is able to provide customer insight in conjunction with the task and process mining features that we use. We install the tool into the machine that the customer uses every day, where it will capture the manual tasks and processes into a database. The insights that we receive are related to whether a process is a good candidate for RPA. For example, if it takes the human a lot of time to complete, or they are having trouble with it, then it might be suitable for RPA because putting a bot in place can optimize performance.
Another reason this is important is that human operators work very hard with day-to-day tasks, and they don't have much time to stop and look for processes that can be automated. Using task and process mining, it starts pulling out those insights. For example, it looks for the number of screens that the human is accessing and clicking on. It looks at each click, as well as every navigation and extraction. In the end, it generates a report for us.
The Agent Console has helped to decrease the average agent handling time, which is our main goal when it comes to these massive business operations. Average agent handling time is the metric that we primarily work with and as such, everything we do is related to reducing it. RPA in our use case is not used only to reduce the HC or FTEs; but it is used to boost this particular KPI too. In one of our use cases, we have had an average decrease of 30% in agent handling time, which is very considerable.
All UI automation activities in UiPath Studio and REFramework are useful. UiPath Orchestrator is also valuable. These features help me a lot in my projects.
UiPath Studio's UI automation activities help me in easily developing automation. It is difficult for RPA developers to write complex code because no one knows everything about all automation areas. For UI automation, it is not mandatory for a developer to know how to write the code for the element on the screen that needs to be clicked or typed into. The UI automation packages of UiPath provide built-in activities, and developers can directly drag and drop and indicate the element on the screen that needs to be clicked or typed into.
REFramework is a template using which we can prepare quality workflows for the transactional processes. It has very good error handling, retry, and logging mechanisms.
We can monitor robots in Orchestrator. We can check logs, monitor the performance of each robot, and divide robots into different environments. These features are very helpful for me in managing my work. If I have two or three robots on a set of machines and I want to define my process only for these robots, I can add that process into the environment. My process will be executed only on those robots. This is a good functionality.
For every transaction, there is the queue functionality in Orchestrator. I can go to a queue and add each transaction item to the queue. For every transaction, I can check the logs. I can also check their logs based on the jobs executed. We also have triggers, so we can schedule our jobs with the help of triggers. These features are helping me a lot in managing the performance of my robot and understanding how my robot is performing.
They have UiPath Forum where I can ask any questions. Many UiPath Most Valuable Professionals are on that forum, and they help us a lot. We get quick replies. If anyone is having any challenges, they post their challenges on the UiPath Forum. I can go through them, and if they are already solved, I gain knowledge by reading those solutions. If not, I try to answer them. In addition to gaining the knowledge, I'm getting some visibility in the UiPath Forum. All these things have really helped me a lot in increasing my technical level and expertise and getting good work.
I am an RPA developer and I am using this solution as an automation development framework.
My primary use cases are web automation and data scraping.
I have done jobs that required user-action recording, creating bots for tasks such as scraping data from the screen. I have also created bots for performing tasks like PDF and Excel automation. Some of these are small, and not for a business model.
We are just a customer.
At this time, we have not automated departments or role-specific processes that require human-robot collaboration. Mostly, we have unattended automation such as NOMA inclusion. We do not use the AI functionality in our automation process just yet and we do not use the solution's automation cloud offering. We also have not used the UiPath apps feature.
I would advise users considering the solution to try it once. The community edition is free. You can explore and download the community edition and take note of all the features which UiPath offers. If it suits the company, I would advise users to go contact the UiPath technical team or support team and get more information on how to implement UiPath.
The more you explore, the more you'll learn. It's not just the straightforward drag and drop functionality. Many people say that UiPath is just for a person with no technical knowledge. However, the more knowledge you have of the technical side, with an understanding of languages like Java, Python, C#, the more you'll excel as it's based on a .NET framework.
I'd rate the solution at a nine out of ten.
Santosh Sundar says in an UiPath review
RPA Technical Solution Lead at a tech services company with 51-200 employees
It has a lot of features, but the ones that I'm really interested in and focused on are the Automation Hub and the Task Capture tool that they have created. Automation Hub helps you in gathering a lot of ideas, and Task Capture helps subject matter experts in capturing the step-by-step processes. It helps them build their SOPs or a document system wherever it is not already available.
The Uipath Document Understanding framework is also very nice in comparison to Abbyy and similar sorts of OCR technologies.
In terms of the ease of use, I would rate UiPath very high. If you have some kind of coding background in C#, .Net, or VBA, the development in UiPath is very easy. You can customize it as per a customer's requirements. It has an easy-to-use Studio where you can build complex automation. On the Citizen Developer side, people without much technical knowledge and coding expertise can also automate their basic processes. We have done some training internally within our management, and they found StudioX very easy to use for their developments.
As compared to the licensing costs or the pricing of other tools like Automation Anywhere or Blue Prism, it's a bit cheaper, however, when we talk about the open-source tools such as Robocorp or Robot Framework, the cost is on the higher side. Microsoft Power Automate is also cheaper.
There are no other costs beyond the licensing.
UiPath hasn't really helped us minimize our on-prem footprint. We are still using the on-premises deployment and everything is on-premises for us. We have, however, used some machines on the cloud. Still, the on-premises footprint in terms of UiPath is not lower.
There are a couple of minor items that could use improvement. Overall the tool roadmap looks fine. They have improved a lot from 2019 to 2021. In two years, there have been lots of additions. It seems like there's no particular improvement which they need to make. They have already improved a lot in the 2021 version, which is adding a modern framework and then modern folder structures.
They can probably focus more on attended stuff or creating a UI around that. We are not using the attended bot a lot, however, I have seen some use cases in other organizations, as I'm working in consulting. I've seen in some other areas where an organization wants to use attended automation, however, the feature is not very well designed which makes it difficult to use.
I'm just an end-user.
My first experience with automation was, "Okay, which product to learn?". After all the reviews and reading, I decided to start with UiPath. My previous background was .NET web development. I was a full-stack web developer with seven-plus years of experience and I found that I really like when a product is built on a .NET framework. I realized that "Okay, it's better to do something, learn something and I have a background of the platform so let's start from there".
When I started using this product, I found the academy was quite open, and in the forum, there were people who were training as well. I found that while I may not get 100% of the answers I need, 85% to 90% of the time the answer is there if you search.
Many people do not know RP automation, and it's great that they have these free resources - which is rare for such a product. Each region has a chapter where people working in this area come and share their knowledge and experiences.
Currently, I'm using the 2019 version of the solution. It's not the latest, however, it's not much older. I'm using the enterprise as well, which is free for 60 days. I started using UiPath apps as well. I'm learning so I use the cloud orchestrator to deploy my processors.
I'd rate the solution at an eight out of ten.
reviewer1642950 says in an UiPath review
Application Development Specialist at a tech services company with 10,001+ employees
I am a software developer and I am a full-time RPA developer for my company. We create automation for internal purposes as well as for our clients.
I have implemented 15 to 16 processes end-to-end that cover use cases including Excel, front-end web-based applications, backend Windows applications, and sometimes Citrix. I have also done some Adobe Flash Player automation.
The REFramework (Enhanced Robotic Enterprise Framework) is what we use for most of our use cases.
We are using Studio for development on-premises and we use Orchestrator in the cloud.
Jyothi says in an UiPath review
RPA Consultant at a computer software company with 10,001+ employees
Orchestrator is very useful for deployment and publishing, maintaining queues, and running jobs.
In UiPath, REFramework is useful for different use cases with predefined code templates. There are well-established steps. There is a step for code marginalization. Similarly, there are separate steps for initialization and processing. For closing an application process, a step is there. So, it is very well modularized for getting the transaction data. If there is one exception or anything wrong happens with an application, it will log the exception in the orchestrator and send an email. It can also close your applications and end data processing. So, everything is well organized and separated, and we can log the exceptions separately in the queues as business exceptions or application exceptions. We can have the complete report of a particular queue.
For document understanding, there are so many features. I haven't used them practically, but to read a PDF, there are patterns and semi patterns. A wait option is also there for somebody to come and correct it. It can wait until somebody comes and corrects it, and then it will do the processing. So, all of the features are very useful in UiPath.
RPA is actually something that can be executed, that can be used side by side with many programming technologies.
The speed of development in UiPath is very fast. For example, sometimes you want to do many frameworks and the budget is low, with the timeline being very crucial. With UiPath Studio and with the whole UiPath platform, it can be very fast to develop and deploy. That's the main advantage for me personally - that the speed of development is great.
UiPath enables us to implement end-to-end automation starting with process analysis, then robot building, and finally monitoring. They are all there. The one exception I’ve noticed is that end-to-end automation is still lagging, I have reasons for that. However, the monitoring of the robots or even using insights is there. They are the prerequisites for an RPA platform. They are great suites. They are necessities.
I like parallel processing. I like that a robot can do some parallel stuff while the user continues to do their own thing. If it needs interaction, we can just pop up a clear window or apps, for example, or through email, in order to inform the user about the robot's request.
AI Automation overall has enabled us to automate more processes. However, when we go forward and move forward, we see that we can digitalize those documents before it needs to be processed by an image machine-like OCR or even Machine Learning. For example, there are still handwritten documents. We’ve convinced many organizations to drop those handwritten documents and use digital products for us. Those are immediate time savings for the process. We are not using document processing anymore, for example, in a specific organization. For processes that still need to have handwritten or printed out documents, document understanding could be fine. I really hope, however, that they shift to AI, which is what RPA lacks. RPA lacks Autonomous Automation, that's something that everyone is waiting for. We’d like to have a robot that's actually using the computer with its own mind, not just the workflow we give it.
The solution is not just about playing recordings, dragging and dropping them onto the platform. It does more, it allows your business to have more use cases. When you are using the framework it allows you the ablility to customize the Java code according to business requirements. This is what makes it easier for us.
I think from a business point of view, we have accomplished what we wanted to. From a skills perspective, there is still a lot of upskilling that is required because our next step is machine learning.
Kryon RPA: Framework
Spend time focused on standing up your center of excellence around the solution. Kryon gave us some great advice on that in the sales process regarding defining what we're trying to do with it. Get key sponsors and then get a key team that works through the implementation, together.
What we're learning from using the solution and what we're really still trying to figure out is what is a good candidate for an RPA process, versus the other ways we could automate, whether it's process elimination or deploying some of our core engineering teams to write different tools. We're still trying to figure out what the framework is for picking the best processes.
The processes that lend themselves to RPA are processes that are highly repetitive, high volume, low-judgment types of processes, where you can write down the process in a Word document, write down the logic, and then turn that into an RPA solution.
We haven't been able to make that leap yet, in terms of Kryon's full cycle of automation from the discovery of our processes to turning on the automation and scaling it up, but we see the potential there. We haven't quite gotten to that point yet, given how early on we are in our journey.
When it comes to using the solution, for both business users and developers, you do have to have some technical background to use it. It's unlikely that you would deploy it to somebody who doesn't have any background in it. But people who are somewhat technical have been able to use it pretty successfully.
I would rate Kryon at eight out of ten. It has a lot of potential and we see that potential. It needs a few more iterations for me to bump that score up higher. It has been a good experience so far and we're looking forward to the future.
Redwood Business Process Automation - Finance Edition: Framework
The out-of-the-box finance modules within the Redwood Finance framework help to speed up the process, versus designing and writing generic BOT code.
The only time that it took was to perform the process analysis, identifying steps, and mapping the steps within the BOT code.
Testing was done from the Redwood team on a system with test data (masked) before rolling it out for user acceptance testing and Hypercare execution.
IBM Robotic Process Automation (RPA): Framework
reviewer1460010 says in an IBM Robotic Process Automation (RPA) review
AVP at a comms service provider with 51-200 employees
The way the robots are being used actually. We need to design the robot to instantiate it based on some event or human intervention. If that can also be automated, that would be good. That would be an additional workflow completed. The next step after that would be to use the RPA service. Some things which require human intervention can also be automated using some decision management, based on rules. If there's a framework which does all of this part, that would be good I think. RPA should be configured as a part of business process management and built-in. For the user, it shouldn't matter if he is using RPA or he's using none of the automation. It should be seamless from their viewpoint. So they would just use drag and drop, choose the features they wanted, and that would be it. RPA and BPM in one solution and RPA encapsulated inside BPM. This RPA should be under the umbrella of BPM. This is what the future should be.
reviewer1251291 says in a BotFarm review
Senior Principal Consultant at a computer software company with 5,001-10,000 employees
I think that the governance framework is completely missing from this solution and something needs to be done about it. Other products are ahead of BotFarm in this regard.
Having the validation of the bots is something that can be improved.
Pricing for this solution can be better.
I would like to have access to self-service support.
WinAutomation by Softomotive: Framework
Daniel and RPA says in a WinAutomation by Softomotive review
RPA Developer at a tech consulting company with 11-50 employees
I think the primary thing that needs improvement in this product is the stability. It looks like it is easy-to-use and that is very nice, but it is more important to have a stable product and not just one that is easy-to-use. If I am working to create a simple process, odd errors occur quite often and in the middle of creating the process.
The additional features I might like to see in the next release would be adding in some capabilities that other products already have. For example, some RPA process management framework. UiPath has something like that, RE Framework (Robotic Enterprise Framework), which is something in Softomotive we have to develop by ourselves. They have some premade processes in WinAutomation, but in running a process they should have some kind of error handling. For example, if there are tasks that should be run like 100 times and maybe it will freeze up at the 50th cycle, then the process should start again from 50, not from number one.
If they can come up with some kind of framework and error handling, that will enhance the stability of the running processes made out of their solution. Right now I cannot resolve these main issues on my own and they should be added to the product.
Microsoft Power Automate: Framework
reviewer1268505 says in a Microsoft Power Automate review
Digital and E-Business Analyst at a construction company with 5,001-10,000 employees
The initial setup is really straightforward. It is immediately available out-of-the-box when you have Microsoft Cloud. You just click on the button and it is there ready to use.
Our deployment took maybe a week or so. Most of that was just to play around and get familiar with it and become ready to start doing actual projects. Because you are building your own little mini-applications inside of it and the framework is available already, it is just a matter of learning how to work with the tool. You need to learn how to use it to build what you want to build.
There were only two people involved in the deployment process. It did not require a lot of effort. It was just a couple of minutes to be ready to start using it and a week to get to the point where we could be productive.
The framework for the product is maintained by Microsoft. Any applications that we build inside of it is all we need to maintain ourselves. So we do not have to maintain the framework at all.