The solution is improving every day and they have valuable tools for integration with RPA tools like OCR system, for example. We use it on our PDF documents and on our invoices.
Robotic Process Automation (RPA) PDF Reviews
Showing reviews of the top ranking products in Robotic Process Automation (RPA), containing the term PDF
Kofax RPA: PDF
Automation Anywhere (AA): PDF
#1.You don't have to really code anything, as it gives you a good interface (UI), because the components are already preconfigured, you have to just a drag and drop sequence in terms of how you want to execute the steps.
#2. There are preconfigured APIs that can be used. E.g., if you want to interact with the mailbox solution, you can have the RPA fetch attachments or email body from the mail solution. You can process attachments via test file or PDF. You can even make Automation Anywhere work around PDF, which is typically not that easy to work with in terms of extracting information.
#3. Metabots/ IQ Bots: One of the features, which we have not used too much, but available, is the MetaBot feature. These preconfigured solutions are easily downloadable, and you can just plug-and-play with a bit of customization, which also means you do not have to keep recreating and can reuse existing functionality. Some of the typical uses are that you could be regularly logging into a website. You can just download a MetaBot, as a useful webpage interface and just run it. All you have to do is maybe replace the name of the website, and in case there is a certain authentication mechanism that is being used, then provide that information.
# 4.There are multiple levels of cloning. In case screen cloning doesn't work, you can do object-based cloning or keystroke-level cloning, depending upon what parameters are available to you and what is the level of information that you capture. You can traverse between object cloning, which is the lowest, most basic form of cloning to a stroke-based cloning, which is like taking care of each keystroke-level which is made by the agent.
The most valuable feature is PDF automation, where we can automate templated PDFs with almost 100% accuracy.
DOMX path support for identifying the web elements is helpful.
The Control room features, such as pooling devices, Queues, and the secure environment, are also valuable.
We primarily use Automation Anywhere to automate Windows applications and Web applications. Both of these are easily automatable with the advanced Automation Anywhere commands, which are user-friendly and easy to use in the Financial & Banking services industry.
It can be used to automate the PDF processes, Microsoft Word, as well as Excel. Without manual intervention, the bot can make its own decisions based on the business rules, and its timely actions make the bot to run smoothly. This saves the users' time and compared to manual processes, the bot reduces the effort and time, with it safely run from the control room.
My primary use case starts with downloading an inventory file in IE and then storing it in the database. This uses DB variables that interact with the banking application.
Through its automating system of generating quotations, it is much easier for us to track back the same customer data. It is giving us a real-time capability for generating reports.
Automation anywhere has equipped us with amazing tools including Bot Insight, IQ Bot, Discovery Bot, etc. The Discovery Bot is used to search the entire task in the system that can be automated. It keeps much value in our organization.
Extracting PDFs is very easy using Automation Anywhere. Its strong points are that it is easy to use, easy to deploy, easy to share, and has multi-user support. Different devices can be used to execute the bot.
The Bot Store provides some utilities for free, which can then be integrated into my workflows easily.
A 2019 dual-mode is very useful and the Control room type of setup for use of A2019 Client is very useful as it eliminates disconnection issues. Also, the broad range of Commands and elimination of the need for Metabots is also very helpful in Automating the increased number of variable types cover an expanded range of web and window components.
Bot insights and IQ bots are both valuable features if implemented in a cost-effective way for larger enterprises, Bot insights provide analytical details of the ROI that is generated by running bots and IQ bots help to automate document processing in an intelligent way minimizing the cost of document processing and hence saving a lot of employee time and money for any enterprise with a large volume of pdf data.
There are many features of Automation Anywhere that were found to be most valuable like WLM, PDF integration, Advanced Excel Commands, Terminal Emulator and its commands, Interactive Forms building features of A2019 which helped us in developing UI for our front office automation and integrate it with multiple rest APIs. The new features which were introduced in A2019 like Data Table, custom DLL, IBM Watson Speech to Text, IQ BOT, Document Extractor has been impressive. The option to use the Python Script has been very helpful.
My primary use cases consist of the following:
- Filtering and manipulating multiple Excel, CSV, XLS files to gather relevant data as per the business requirements.
- Extracting text from searchable and non-searchable PDF files and uploading the data to separate output files or web-based forms.
- Scheduling tasks to run on a daily basis or implementing trigger-based process execution.
- Implementing email automation in various modules.
- Working with external macros and JScript files, depending on the given business logic.
Automation of AP 3 Way Invoice Matching Process. Details from PDF invoices with the corresponding data in terminal. This project involved applications like Outlook, Aurora Terminal, PDF reading by IQ Bot, and Excel. The current scope of the project was to process around 600 invoices per day from 20 different suppliers which has saved a lot of time for the end-user. It has been deployed in production and the customer is pretty much happy with the performance of the bot.
On-Premise installation of CR with 1 runner and 2 creator license.
AA brings a lot of benefits for our organization in a number of different ways.
I could say that many of the Salesforce activities are now replaced by bots, like creating the case ID number, uploading the attachment in the Chatter feed object, and many more.
Earlier users were converting the unstructured data from the PDF into the structured format to process the task but now, this activity is replaced by IQ Bot. It reads the unstructured data from the PDF and processes the task smoothly. Basically, we are dealing more with the invoice PDF to read the unstructured data.
I believe everyone is aware of the Jira application, which is used for issue tracking and project management. Now, all the Jira activities are replaced by the bots. Whenever any user is logging any issue through Jira, the Bot automatically assigns the ticket to the respective individuals, which saves a lot of time. In a simple way, I can say the Bot has replaced our Jira monitoring team.
We get many banking and finance use cases e.g. reconciliation, accounts payable, etc. from banking clients which involves the extraction of unstructured data from various scanned and true PDF documents. Post this, the data needs to be validated and triaged before feeding it into SAP and Java-based applications.
The Automation Anywhere platform has always stood out from the rest of the solutions available on the market given we have IQ Bots and Bot Insights neatly integrated into the platform which enables us to develop rapidly and train the learning instances using pre-defined domains over the purchase orders, forms, invoices that need to be processed. Post extraction of the form and data fields from the documents we post them into SAP and Java-based applications. Automation Anywhere's ease of automation with these types of applications helps to deliver consistent and reliable automation in record time.
We are currently using AAE 220.127.116.11 Client with Control Room, IQBots, MetaBots, Bot Insights, and AA2019 capabilities.
The recorder feature for front end automation and email packages is the most valuable feature as it has more features and it makes the email server related tasks easier and more independent on the email client. Integration of VB, python, and java scripts help us to make our code more reliable. Excel basic and excel advanced package with increased features help us to easily automate the Excel related tasks.
PDF package is also valuable for PDF to image conversion, encryption, decryption, and merging.
OCR package is also valuable as it helps to read the contents of Image.
The most valuable feature is IQ Bot, as it allowed us to train it to extract important logistical information from customer PDF documents, irrespective of the format. This is valuable because not all PDF sheets have the same format. Many customers tend to use various formats to represent their data. Hence, with IQ bot, even with the wide variety of different PDF formats, the bots would still able to help us extract what we needed.
We use this solution for all the business processes and mainly to integrate with Excel files, our database, and our ERP.
We basically process data that are in form of Excel, PDF, or CSV formatted files. We also interact with information that is stored in our database.
Generally, we automate a lot of processes that are repetitive and time-consuming. We work mainly with processing data, thus reducing the time needed to do the process manually. The workforce is also reduced for completing simple tasks like logging in to a forum, as well as complicated tasks like banking or finance. All of these all possible.
reviewer1468062 says in an Automation Anywhere (AA) review
Senior RPA Developer at a tech services company with 201-500 employees
It is one of the simplest RPA tools, having a simple user interface, and it is very easy to get hands-on with this platform. It has vast learning resources available, too.
- Extracting data from scanned PDFs: Using Automation Anywhere made it much simpler to scrape data from scanned PDFs and convert it into standard Excel format, as per requirements.
- Portal Automation: AA makes web automation simple and our manual tasks have now been automated. Our portal is for making client bookings of the client. The Bot reads the Excel file shared by the user and accordingly, makes the booking in the portal with minimum time and with high accuracy.
reviewer1180077 says in an Automation Anywhere (AA) review
Lead Engineer at a financial services firm with 10,001+ employees
Anurag Vishnoi says in an Automation Anywhere (AA) review
Head of Robotics Process Automation at a comms service provider with 10,001+ employees
Implementation of Automation Anywhere (AA) allows us to automate business processes and has brought productivity gains, error reduction, and speed of execution in multiple HR and Finance operations.
This automation has also helped in achieving better compliance and standardization of the processes. A number of processes were able to be digitalized 100% without much human interaction required. The only exceptions are managed by humans although the RPA bots are doing the majority of the work.
Implementation of IQBOT has helped in capturing the semi-structure data from pdfs and doing the straight-through processing of these documents.
Blue Prism: PDF
reviewer1338657 says in a Blue Prism review
Development Lead For RI DMV Modernization at a tech services company with 10,001+ employees
There are many reasons why many companies don't go for Blue Prism. It is not open, and the community addition is not available. Blue Prism provides support through partnership. You need to do a partnership with them, which is a major disadvantage. You contact a Blue Prism team, and they will schedule a meeting with you. They will give you a demo and help you set up everything, whereas with UiPath and Automation Anywhere, you can try the community edition, and if it fits your needs, you simply buy a license for that.
The initial setup of Blue Prism is complex. They simply provide a PDF or documentation for you to go through it, whereas, if you go with UiPath or Automation Anywhere, they have several videos and community support to guide you.
The documentation of Blue Prism is static. They don't have any sort of videos or open forums. Other tools have got a lot of community support, but Blue Prism doesn't have that. Its training is also hard to attain, and they also don't provide any certification.
We've primarily used the solution for financial purposes. We have payroll management and a lot of manual processes. With this, we can run automated reports. There are about 15 to 18 interfaces where we get the information. We can consolidate emails, PDFs, and Excel. There's automation to pick everything up and understand all the sources and different kinds of data. We can input raw data, consolidate it and then handle calculations. We can download data and save it in folders.
reviewer1141743 says in a Blue Prism review
Senior IT Architekt at a tech services company with 5,001-10,000 employees
In one of the use cases, we import Excel tables. We extract the Excel data from the output of a proprietary application. This application produces Excel tables as an output, and we then create PDFs for certificates for the people who are flying. They have to do training, flying hours, and things like this. In this project, we closed the gap between the proprietary application, provided by a different team, and the HR application.
It is deployed on-premises. Due to security issues, we are not allowed to use cloud services. We only have centralized application servers that are operated by the central operations team. It is not on users' desktops, which is possible, but it is not our focus.
We are using approximately 70% of all of the activities that are available in UiPath. These include web scraping and data entry, where the information is stored in a database. We also perform database queries.
The biggest benefit that we have from UiPath comes from using the API.
The features that we use most often are database communication, scraping, and PDF functions. The only features that we don't use are those related to Excel, for spreadsheets.
For smaller projects, we are only passing parameters from .NET applications but in the newer projects, we are using features such as database communication and data scraping.
The ease of building automations is great. When I talk about UiPath, I am usually referring to Studio, which has a very intuitive and easy-to-use interface, yet it is very powerful. This is something that has improved with the help of forums and tutorials. In 2016, it was more difficult because there were really no forums so we had to contact the head office in Bucharest, Romania when we needed help. Getting a demo had to be done in the very early hours and there was lots of communication back and forth. It was a struggle to find solutions, although to be fair, they've been very helpful. These days, it is very easy to use because there are numerous examples, and UiPath Academy is available, along with other resources.
We have been using the UiPath Apps feature and it has helped with the ease and time required for creating automation. Everything has improved over the past several years, as in the past, there were no examples or tutorials available. There was no manual and it was very technical. At the time, you definitely needed programming knowledge in order to handle some of the scenarios. It was at times like this that we relied on support from Bucharest.
Even today, there are only a couple of programmers in the company who develop the bots. Even with the Apps feature, I don't think that the end-users are ready, although this may be because of the way that our organization is structured. Everything is given to the IT department because our scenarios are very complex, and not a simple case of data entry or something like that. With such complex solutions, it is definitely too difficult for our end-users.
The primary use case is the automation of many reports, dashboards, and tables that were created manually by some of my colleagues. The tasks involve collecting information from SAP Solution Manager, manipulating some of the data based on business rules that have been implemented, and then storing the data in a specific way that can be used in the next part of the workflow. This includes using Excel and the aim is to create a PDF report that is sent to the top business line managers.
UiPath is the perfect tool to implement a solution like this, with continuous operative tasks between Microsoft native applications such as Excel, Outlook, and PowerPoint.
The feature that we use the most is Studio.
Document Understanding is a good feature that is very helpful to us. We have an ongoing project that requires reading PDF files. We need to use different OCR engines and see which ones give us the correct data. Document Understanding allows you to extract the data into different types using different extractors. For example, there is an ML extractor and other types that allow you to pinpoint fields and determine which should be accepted. Based on the confidence level, it gets better every time. In this way, the feature has helped us a lot.
This is the friendliest community and forum that I have ever seen, which is something I see as added value.
I am an RPA developer and I work with UiPath in that capacity.
Our current use case involves the automation of a process involving healthcare-related data. This is confidential data that is received from the customer and inserted into Oracle forms. Reports are then generated from it and these reports are then used by the organization, which is in the healthcare domain, for their analysis.
The data being analyzed includes medical and treatment history. For example, with the current pandemic going on, there are all sorts of healthcare data that is related to it, including various types of treatments. When somebody walks into any clinic or hospital, all of the treatment is entered into a database and we get an extract of it. The analysis is used to get more details.
Another interesting use case, prior to this one, involved the documenting of invoices. We were working with approximately 250 different samples of purchase invoices, many in different formats. One might be a native PDF file, whereas another could be a scanned PDF, and yet another might be a simple handwritten invoice that was converted into a PDF based on a picture that was taken from a mobile device. We were receiving these invoices from our client and they wanted to extract data from them. It was accomplished by using the Document Understanding features in UiPath.
The other notable use case had to do with issuing refunds for purchases that were made on an e-commerce site. When a customer made an order and there was a problem that resulted in them wanting a refund, there were multiple ways that the client could request one. A refund application could be received by the customer care department in the form of a simple call, which was a verbal request, or as an email written by the customer, or as an automatically-generated email that was created based on filling out a form on the website.
Regardless of which of the three input methods is used, the refund request is gathered and sent to a mainframe application. At that point, the information is extracted from the mainframe and the refund is issued using another application.
The automation of these tasks using features such as artificial intelligence and document understanding has reduced our costs. For example, with the invoice processing use case, there was a team of between 20 and 25 agents who were doing it manually. Obviously, a team of that size has a large cost associated with it. Also, the volume was very high, which meant that the team was not able to deliver on all of the work. There are approximately 250 vendors sending invoices to our customer to process the data, which translates to about 1,000 documents being sent on a daily basis, to be processed by only 25 people. It was a huge task. With this level of volume, people tend to get frustrated.
We implemented the automation and the team size has now been reduced to only five or six people, and that is only required to monitor the bots. For example, they check to make sure that the data being fetched using document understanding is at par. We have set the minimum confidence of the documents being scanned at 90% and each day, a report is generated and sent to the customer. Overall, it was a very cost-saving implementation.
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.
One of the things that I like is that they keep adding new features, such as machine learning models. For example, if you are reading a PDF copy of an invoice then the RPA should be able to identify and understand it. Rather than using rules to identify different formats for different kinds of invoices, machine learning and AI should be involved.
We are using the AI functionality and it gives us the ability to have more automation, saving more time and manual effort, and at less cost. This is possible because UiPath provides pre-built and pre-trained AI models that we can import, depending on the use case.
Some of the processes we have implemented are very complex, and these are the ones that we need AI for. Some of them involve human interaction and cover use cases such as taking different formats of invoices and pushing them to SAP. We have had good success when working with the machine learning capabilities.
The Action Center and Task Manager are very good for business users. The features are helpful because these days, business users are expecting more than a simple rule-based operation in RPA systems.
UiPath Studio integrates well with third-party tools such as Git. It is easy to maintain code from within Studio.
All the features, all the packages, everything, have been great. All of the artificial intelligence which we are getting is super-useful, as are all the needed updates.
All the features are valuable as, much like any application, it cannot work without just one feature. For example, we have PDF automation, we have Excel automation, Citrix, SAP, and we have SharePoint automation - which makes it so that we can automate anything. All the features combined allow us to work on multiple projects or one specific project.
The ease of building automation using this solution is good. I really enjoy the flexibility. It's also very easy. We do need a few coding skills with languages like C# or Power Automate. However, it's got a good UI, with drag and drop functionality. That makes it easy compared to other tools, like Prism automation. UiPath is much better and it's highly recommended.
Scaling automation without worrying about the infrastructure was easy. I simply did some googling and looked to see which automation tools were out there and which was the leader. There were multiple training portals - including UiPath Academy, where I was able to pull all of these tutorials and insights. There's also a free forum where queries are answered. It made everything quite easy.
The solution enables us to implement end-to-end automation starting with process analysis, and robot building. This end-to-end coverage is important to me as we follow an agile methodology. We have an RPA development life cycle. This product gives us all the tools and everything we need. The requirement gathering and document preparation come as standard models. We have UiPath Studio for testing and UiPath test features for maintenance. We have the Orchestrator where we can maintain everything as well. We can see where things are working or not. In fact, we have integration with PagerDuty that gives alerts if something is failing or not working. It's really important that UiPath has integrated across all the life cycles, and that all the phases are working properly.
UiPath has helped to minimize our on-premises footprint, which has been very important to me. It's very important due to the fact that we can build a robust and scalable solution for an enterprise and have security in UiPath. It's very important that customer satisfaction is there, no matter what we are developing. It's very important to our organization.
It's a very fast solution. It can provide a result or automation to a business process within seconds. If we have an API, we can integrate EPS as well instead of using the UI. Basically, we can get any solution we need within seconds. It's very fast.
I have noticed that the solution reduces the cost of digital transformation as we are saving on manual hours. It's reducing them. We don't have to hire more people to do these manual jobs, which has helped us reduce the cost.
We did require application upgrades and IT application support. We wanted to update get all the latest features that UiPath often releases. I've seen every month or every year we get all of these new packages. It's better to include the latest version to get all the latest features.
With UiPath, we have reduced human error. Humans are prone to making errors that they can make at any time. The bot does not. It's continuously given proper feedback. The lack of human errors has affected business a lot. The bot allows for complete confidence that perfect work is being done. It has also freed up employee time. We've saved thousands of hours. We have ten processes that are running in production. Up to this point, with those running, we have saved up to 1,918 hours from the automation. On top of that, employees can now focus on higher-value work. It has improved work satisfaction. There is more self-motivation that boosts the work, which we are doing.
The solution has reduced costs overall via automation. However, I cannot speak to exact cost savings. As a whole, it's saved our organization money.
Our use case is mainly for PDF automation for invoicing. Specific data from the invoice needs to be gathered, entered into, and compared within the SAP application we use. We face challenges as the formats of the invoices change and can range in length from a single page to up to 100 pages.
We've integrated a tool called ABBYY FlexiCapture and ABBYY will help format and be used as the source of input for the UiPath bot. This bot in turn will process each and every necessary customer detail to the SAP application. If everything is correct, and the data meets the parameters, an email will be sent to the customer, attaching the necessary invoice. If there's an exception, we'll be able to look at that too.
There are some other sets of use cases as well, which include SAP or Hyperautomation. However, we also do generic workflows where we have data from multiple domains and will need to build our XML output. The XML output will contain a lot of data (such as the date, time or name of the customer) which will keep changing and is not fixed. I built a bot using UiPath that I host on Orchestrator which can monitor this data.
Another use case is placing job descriptions into an analyzing tool to search for keywords. Depending on the sort of description which we have pasted in, it will throw out a certain set of outputs, such as if the word is feminine, masculine, how many details it contains, how long it's going to take to complete the description, et cetera. This part has been done using an API key, and therefore it's not a normal cut and paste job.
I've created an app for conversions and exchange rates. Every day I need the exchange rate of a certain currency and I use the API free exchange and UiPath.
It's also used for the reconciliation of invoices.
I've used it for the creation of an onboarding bot for employees to be onboarded onto a website with a remote system. I used AWS and a virtual machine and created a Google Form from there, and used UiPath's computer vision to do onboarding activities and extract data from files. PDF files can then be entered into the remote system. UiPath can be used to fill the forms.
It can be used for web extraction tasks as well, for example, for booking flights, where you can extract the flight details for particular search criteria and place them into an Excel sheet.
It can also be used to extract data from invoices in order to populate an Excel sheet, for a portable format. I've created a process that used documents as a learning model and extracted the invoices, using logic to output the transactions.
Another use case I tried was extracting data from Amazon based on exact data. The same can be done on Linkedin using the Linkedin API. I'm fine-tuning and extracting data, putting the outputs on Google Sheets.
I've experimented with many use cases and automated many processes.
reviewer1642950 says in an UiPath review
Application Development Specialist at a tech services company with 10,001+ employees
UiPath has helped to improve our organization in several ways. Prior to UiPath, the company was using legacy methods of automation. These were time-consuming and required that more code be written. With the ease of use and speed at which automations can be developed using UiPath, the company is bringing on new clients and therefore, more business.
UiPath and the automations that we create help us to better utilize our resources. For example, a manual task that used to take between seven and eight days can be completed in one or two days with automation.
This product is bringing new clients to the business and nowadays, all of our clients require something to be done in the domain of robotic process automation.
With respect to ease of use and building automations, UiPath is very good. I would rate them at least a four out of five in that regard, especially when compared to other products on the market. The ease of building automations makes them quick to create and it can be accomplished by people in the business sector.
UiPath enables and helps us to create end-to-end automations, and it divides all of the subtasks up in a good way. For example, monitoring processes is different from developing code, and each of these is separated such that they are independent, but we can link them together for the benefit of the process. This is important because I am a complete process developer, so having all of the different subtasks available in one tool allows me to best develop automation for our clients.
This solution has helped to decrease our time to value, which is something that is evident when you look at the automation we were doing previously. Our technologies included Python, VBScript, and other ways. These approaches took more time to develop and are a little bit more complex. With the help of this tool, it takes less time to build the same automation. It allows us to focus on building the logic and algorithms, without having to deep-dive into things like syntax. By allowing us to focus on the business logic for each process, it leads to significant time savings.
We use the attended automation feature and it helps us when it comes to tasks that require interaction between user and application, such as the necessity to enter credentials. It is quite helpful, in particular for BPM processes, and this is something that is important to us. The typical case is when somebody is doing repetitive work as part of their task. In other words, they are working on one task, and the bot is working beside them but needs the occasional input from the user. In these processes, the bot is doing 80% of the work and the user is doing the remaining 20%.
We use the AI functionality because it makes it feasible to automate processes that are quite complex. For example, Document Understanding and NLP from the UiPath Cloud are things that we use.
The AI features enhance UiPath's capabilities and allow us to automate more processes overall. Previously, when we were doing a specific task, we may not have been able to fully automate it. With the help of AI, we can do more.
In previous iterations of our bots, before the AI features were used, we were not able to get all of the information that we needed from PDF files. This is specific to certain use cases, to present an example. The AI functionality generally gives us more data, whether from document understanding, computer vision, or otherwise.
UiPath has helped to reduce human error because the bot is doing everything and eliminates the opportunity for people to make mistakes in the process. UiPath has had a positive impact in this regard, although we have had successes with other similar tools as well.
UiPath and automation have helped to free up employee time and nowadays, they are more creative because of it. With many of their tasks automated, they have time to work on things that are more creative and have a higher value.
For example, for a task that used to take an employee 10 hours, they are now spending between three and four hours on it. In the remaining six hours, they can be more productive and work on more important tasks. This not only helps the employee but adds value to the company as well.
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.
The developers like the studio interface better than other RPA providers that they've used in the past and find it easy to use and can provide a lot of impact.
The ease of building automation using UiPath has been great. We actually have done them with airmen, with people that are in the Air Force. We've done training and workshops such as one-week workshops with about 250 airmen. Most of them, 80% to 90%, have built bots that work in production with basically little to no training. They can do a lot without any development experience whatsoever going into the solution.
The solution has saved costs for our customers. Overall, it's tens of millions of dollars there for a potential return. They're still working on scaling that out. However, bots that have currently been built could be spread out across the entire Air Force, which is 650,000 employees, and would have about $30 million worth of potential benefit.
UiPath has reduced human error. With one particular use case, we did with flight authorizations, they had to compare your names off of a PDF to a 40,000-row spreadsheet. That not only saves time, it also reduces that error dramatically as the bot can go and find the row in the spreadsheet and then match it exactly as opposed to somebody looking for it manually.
It has saved time for our customers, equally likely $30 million in potential savings and allowing for a shift to higher-order work.
We’ve used UiPath Academy courses. We actually have a new employee training right now using UiPath Academy, and we recommend it to our customers as well. It's fantastic due to the fact that we're not spending very much time onboarding new employees. We're letting them go do the academy and then help them in assisting where needed. That's a huge benefit for us as we can continue to do our job rather than focusing on onboarding. Users can also self-lead, and new developers can go and utilize it without a lot of interaction from others or a lot of help from others.
The functionality where you can quickly convert your code from Studio X to Studio is really nice.
Timothy Green says in an UiPath review
Director Financial System at a non-tech company with 10,001+ employees
Right now, it is way too big for me to even understand it. I feel like it's a universe. I'm just trying to get directions. The area that I'm looking at right now is analytics to make sure that we can properly report on how they're doing, and that's what is going to make management invest further into our idea. I come from a reporting background, and that's what I focus on in other financial packages that we have with PeopleSoft, Hyperion planning, and the FCCS cloud. In many of these automations, the need part of it is that you're not stuck within the software that you had; for example, a macro within Excel can only help you with what you're doing in Excel. It can't help you with an email. It can't help you with a PDF form, but you can bring these together, so the automation opportunities are endless.
So, at this time, it hasn't saved us money because we're just in the investment phase. That's why I want to do reporting so we can see. The decisions you make now affect the next 10 to 20 years. Everyone gets too short-term-focused. You should go to where you want to be five years from now and go backward. What you are doing today is going to make that five years strike. So, it is an investment.
The automation of the cloud offering helps to decrease the solution's total cost of ownership.
The document understanding is great. I interact with different documents of people. The IDs of one are different from a document or a PDF. For example, our contracts, et cetera. It can understand the differences.
I’m not quite sure about the ease of building automation using the solution just yet. It seems to be moderate. Not too easy or difficult.
The solution has helped our organization save costs. It’s likely saved us about $10 million.
UiPath has helped us reduce human error. That’s had a partial impact on our business. Our techs understand the different types of processes and competencies it can help with. Regular users cannot see this just yet.
It has freed up employee time. It’s allowed for a focus on higher-value work. Employees seem happier. It’s an easy tool to use and deploy.
We’ve used the UiPath Academy courses. All employees take the course and learn about it. You still need more education afterward, however, the biggest value of the Academy is the knowledge. I've got people who are new in the company and I can just say "take these courses." It's accepted by everyone as part of the process.
Often, the solution is used for a lot of connecting data from different systems, et cetera. Also, a lot of tasks involve taking data from Excel or an email and putting it into different PDFs at high volumes and then saving everything in a certain spot in the file directory.
With federal governments, a lot of the use cases vary around what they're doing, however, it's just a lot of PDF, Excel, and Microsoft Suite automation and then interacting with their custom and web-based tools for subject information.
We work with TMS, a technology-management resolution division. We use UiPath to read the PDF documents that we get. We manage a business service for TMS and as part of that business contract, we read the PDFs and enter that information. We get that information out via documents from the templates where we have to enter information related to that particular case.
These are the use cases that we are currently working on, but we are also looking to use this for quality assurance of all the steps because this is a highly visible, very critical process for TMS. We have to make sure that everything is done on time and that all of the information is relevant and responsive. Quality assurance is a big deal for us, and we are looking to use UiPath quality checks at different stages in the process.
My experience in using UiPath, in general, is in developing traditional bots, assisted bots. There are the typical mundane applications that we're trying to remove in order to add value to customers.
The solution is used for extracting information from documents and consolidating data, maybe from various Excel sheets. I've used applications, such as PDF, Tableau, and a number of different entities as well. It varies.
reviewer1695615 says in an UiPath review
Associate - Robotic Process Automation at a financial services firm with 10,001+ employees
There are some external dependencies. When we have APIs available, UiPath does have that option that we can hook into APIs. That's really where I'd like to be down the line, more like hooking into APIs, data warehouses, so that you don't have to worry too much about the screen scraping functionality, even though that's a great big part of what it does.
I would really like the ability to bring OCR connectors into StudioX, if possible. Right now we're only using OCR and Studio as that's where the plugins are available. I don't know enough about the back end of what makes this feasible versus not feasible. However, at the moment, with StudioX, you can only really read and digitize PDFs. If they can bring in the OCR connectors, they'd allow citizen developers to be able to read in a larger breadth of documents that they would generally need Studio to do.
I have used the AI functionality for PDF automations. In these processes, the bot is able to capture the data properly about 70 to 80 percent of the time. But if a document is not proper or it isn't handled the right way, the bot struggles to get the required data. UiPath has to work on this aspect so that the bot will be able to completely capture the data.
There is also room for improvement in the area of third-party integrations. In the last week I have gone through a video for an integration service, but it did not show things end-to-end. Rather, they just explained the connection details only. After performing the steps they showed, I was not able to get things working properly in my process.
The first use case is related to our email process. We need to download multiple attachments in the form of PDF and Excel files from emails. We only accept the PDF files into a specific folder, while the Excel files go into another. We split them based on the file extension.
The second use case is related to the retail domain, in which we need to update an application with data that we get from a client. We process a few Excel operations and then update all of the invoice records in the application and generate a PDF invoice form with the client's details from Excel. That PDF is then emailed to the client.
We are handling millions of users' data that comes in via raw formats, like PDFs, invoices, hard copies, et cetera, and we have to capture that data into our applications so that it can be transformed into usable data for the users. We use UiPath to develop bots to analyze and capture the information in the required format, and to automatically upload and enter the data into Excel.
OCR Tesseract, by default, is the good OCR search engine to extract data from a digital PDF. For any Unstructured document with a normal noise, background letters, either UiPath Document Understanding or AbbyyReader fails to extract the exact values. Very difficult to depend on Computer Vision too as a third party tool for small to mid-range business purpose. Hence, a combination of AI/ML with a good OCR Engine is required for UiPath to go forward.
I have used the cloud deployment at well. Now I use the on-premises version.
If anybody is going to evaluate UiPath, first, I would say, you need to look into what kind of automation you are going to do. If it's ERP, I would definitely recommend UiPath. If it's something, like a PDF or insurance kind of use case, then I wouldn't recommend UiPath. From my experience, what I understand is that UiPath is good for SAP. However, you can use it for any other kind of ERP as well.
I'd rate the solution a seven out of ten.
There are two features that I find to be the most valuable in UiPath.
One is Orchestrator because it allows us to manage the bots and processes. For example, we can monitor unattended bots' run history and their logs. We can also modify our code based on screenshots by logging the screenshots and then viewing the logs in an Orchestrator job. That helps us trace errors and rectify them.
The second valuable feature is REFramework which is a pre-defined template built with proper exception handling and logging activities. Those aspects help developers to develop code properly.
In addition, I have implemented UiPath with ABBYY FlexiCapture for some projects, and that has been very helpful for successfully completing those projects and providing a positive impact for our customers. It makes it very easy to extract data from a PDF and then build code to process it in UiPath. The integration of ABBYY FlexiCapture with UiPath is a very good feature.
For me, the most valuable feature is the solution's ability to discover automation opportunities.
The Document Understanding feature for extracting information from documents or images helps reduce manual work, saving people from having to scrub data from PDF files or images. UiPath extracts all the information and stores it.
In addition, its AI and machine learning make everything easy, as do the Data Service tools, because they don't require coding to create automations. I can do everything without coding knowledge.
And the UiPath user community is the best. The people there are very friendly and helpful, and engage with each other. UiPath has done a good job building a good forum and a good blog, and making the community members interact with each other. The community is one of the reasons UiPath is my choice. It is a strong community.
reviewer1860774 says in an UiPath review
UiPath Solution Architect at a financial services firm with 10,001+ employees
UiPath's performance could be improved. UiPath's framework was built on top of .NET Core. It was a 32-bit platform initially, but they recently introduced a 64-bit version. Let's say I have a huge machine with 64 gigs of RAM. If I have a server machine and want to use multi-threading to extend my automation and multitask, the design won't allow me. I can't separate things into multiple processes.
The platform is designed to go step by step. Parallel activities are not truly parallel, but it creates the impression that it's running in parallel. For example, if you're on the left segment within a parallel activity, and there is some wait time, it doesn't stay there. It goes to the middle and then to the right. It schedules tasks based on a time-to-completion window and then takes them from end to end.
UiPath optimizes the time and doesn't let the CPU idle, but it doesn't give you multi-threading or asynchronous methodologies. These are available in the C# and .NET framework but absent in this platform. It's a step-by-step process where you go through each activity. A casual developer or coder who wants to leverage UiPath should be able to. I'm not saying that the working code is not there, but it's quite basic. It doesn't support functions or asynchronous methodology.
UiPath is attempting to make it easier for a citizen developer to automate processes. They don't have to know how to code, but a citizen developer can't do it when the use case becomes more complex. When they advertise that one doesn’t need to know coding to program bots, that's only true for easy or intermediate use cases. We still need a programmer for anything beyond medium complexity.
The marketing could be improved because the methodologies went from waterfall COE to an automated operation model. However, people are trying to do automation in an Agile model, but it's not exactly executable that way. When customers see the demos from UiPath, they expect that the results will be significant, and they are. However, we might try to automate something, and we’re unsure whether it can be automated because there's a gray area. There's always a 20 to 30 percent chance automation might fail. And that gray area is something that I want UI to focus on.
They have tried this with StudioX by adding checklists. The industry is not following this practice, though. I'm not sure how they should ensure that it gets followed within the platform, but the delivery model needs to improve. It's still niche.
Another thing to consider is the work-life balance of the developer and the solution architect. The overall challenge of automation tends to become exponentially complex over time. For example, let's look at one aspect: the account tables. I can go to the account tables from a simple PDF perspective. The PDF is readable by the board, and the solution can extract all the data and do the account tables within SAP or Ariba and mix all of it and then submit a report to the business.
This can be extended to intelligent document processing using form recognizer and custom models, then passers, pre-processing, post-processing, and sending the report to the business. The complexity of it can be extended quite a lot. There should be a framework or methodology in place to hedge the bet so that it's not too complex and doesn't disrupt the life of a developer, solution architect, or business analyst.
If the automation becomes too complex and challenging, our support team won't be able to sustain it in the long run. Once the development team is gone, the automation will die two or three months down the line. It's a balance to manage the complexity and extent of our automation.
It's pretty scalable. It can be used across all major providers. If you want to automate Windows, web-based or PDF-based interactions, or do email or Excel automation, you can. We can also do terminal automation, mainframe automation, and Citrix automation. It covers almost every possible scenario for real-time data handling.
We only have a couple of challenges, when a customer says we need to do this or that and UiPath doesn't have built-in functionality for that. We need to think differently and add some additional .NET components, for example.
But UiPath is pretty scalable, and we can use it across all technologies for automation.
UiPath automations have saved a lot of man-hours for business people. They used to have to do simple tasks, like creating reports in Excel and calculating with formulas. We just uploaded the data into SQL Server and then connected to Power BI through UiPath. It was a small project for us, just a matter of two minutes or so to put things in place, but it saved them a lot of time. With the bots doing this "small" work, it enabled the employees to relax and work on more valuable tasks.
The employees involved have been happy and they have also suggested a few other processes that could be automated, after seeing the results.
There was also an order management project in which we extracted details, such as delivery date and quantity, from a PDF. Before it was automated, that was a tedious task. It took a lot of time for people to do it and their accuracy was lower than the robot's. The automation reduced the team size for that business and they were very happy. They saw a very good ROI. And it used to take the business much longer to do small reconciliations, but the bots are so fast. They are seeing good results. It has reduced a lot of human error. Initially there are some errors, but once you learn from them and train the bot, you get accurate results.
We have only done a few attended automations, but they have sped up processes that require approval. In those situations, they play a major role. More than the monetary savings, the benefit is that people can concentrate more on the important work, and with less stress. But unattended automation is the most important process.
reviewer1895613 says in an UiPath review
Process Automation Analyst at a non-tech company with 1,001-5,000 employees
My previous company was in the banking sector, and we had done automation with websites, UI, SAP, Excel files, and PDF. In my current company, it is being used for finance and HR. We have ERP, CRM, chatbots, etc. We are using this solution to integrate different systems.
I use UiPath Studio to develop the code, and I use UiPath Orchestrator to publish my work. We have our own UAT systems to test the code. We can install the UiPath in the test environment and find all the compilation errors in the debug mode and fix them. We also have version control. If we upload a version and it doesn't work, we can downgrade the version. Everything is tracked in UiPath Orchestrator.
We are using it on-premise. In my previous company, it was on the cloud, and we accessed it through the cloud.
We work as a center of excellence and we develop automations centrally for other departments. All our deployments are unattended bots that are deployed and managed by us, centrally. They are all running on a virtual machine. Nothing is running on client computers or laptops. We do not have any attended use cases. The process owners are interacting with the bots.
We use the bots for a lot of reporting, including monthly and weekly reports. We are a construction company and we have a lot of reports for all kinds of things, such as construction projects, different construction sites, and various subsidiaries for regional departments. A region like Bavaria, for example, needs its reports. And there are plenty of controlling departments in all of the subsidiaries.
We also have some ticketing use cases. One of them is for IT services, meaning internal ticketing. That bot regularly checks our ticket software and automatically processes some of the tickets. For example, when an employee needs rights to a specific system, the bot checks whether they fulfill the requirements and approves or declines the ticket.
Another type of ticketing use case is more about processing customer tickets. As a construction company, we also do facility management, and that means there are a lot of external customers with their own systems in which they record tickets. The tickets are not visible in our local systems so someone has to go to the external systems, export the tickets, filter them, and then tell everyone what they're supposed to do to their buildings as a result. The tickets might be about small repair jobs, for example. We run this daily and, in the morning, everyone receives an email with all the tickets that have to be done within one day, three days, one week, et cetera.
Both of the ticketing use cases are connected with SLAs. If you miss a certain time frame before processing a ticket for external customers, you have to pay a penalty fee. For the internal tickets there are SLAs for internal tracking purposes. Because those tickets have to be processed within two hours, that bot runs every two hours and checks for new tickets.
Another IT services use case is for getting access rights to local drives.
We also have many recurring processes. For example, in HR they have to go to the system and confirm a process. It’s a necessary evil which is probably due to the legacy systems we have. Someone defined this process a long time ago and it still has to be done.
We also have use cases in finance and treasury. They are not tickets, but they process requests from employees. For example, they can request cash on a specific card and the bot will check the emails and then basically transfer data from an email, or from a PDF form attached to an email, and enter it into the finance system.
One last type of use case is where the bot works as an interface between systems. Data has to be exported from one system and imported to another system and there is no existing API. The bot exports and imports the data. We have one bot that exports PDF documents and sends them to an email interface. It defines a specific subject and then attaches the file. That file will automatically be uploaded to another system. Or the bot may log in to a system and upload the document. These use cases are due to the fact that there is no interface between two systems and they're either not big enough to develop an API or they may involve an external customer system and the customer has no interest in providing an API.
I'm the lead robotics engineer in my organization, and we are involved in marketing and research for new technologies such as mobile phones and laptops. We are an organization with 219 employees and started using UiPath for laptop marketing and advertisement for our customers.
Our clients have different requirements and strategies, and we build software robots tailored to their needs. A customer can send an email with attached PPTs, Excel sheets, PDFs, and images, and the bot can extract all the data and express it in the required format. This is uploaded as an article onto our website, and on our platform, so the marketing, advertising, and technology solutions specs are taken care of without any human intervention or involvement. We designed 39 robots for the same number of clients.
Our second use case is for invoicing; customers share checks for payments with us via email, and we have bots to extract that data and input it into our SAP ERP system, which is fantastic. The RPA automates billing on the financial side of our organization.
We use the solution across 17 locations with servers managed centrally from our main office, connected using the UiPath Orchestrator. We have 19 licenses but only use 17 currently. We don't have more than seven end users as this is purely a tool for internal use; our customers don't have access.
My company's major use case for UiPath is to create automations for web and desktop applications. For example, we use it to automatically download content from another page or PDF. It's creating automatic programs to help us download data from the website or application.
Excel automation is extremely reliable. Excel integration is one of the top features that I have been using. We also have a feature called Document Understanding for processing the PDF format of an invoice by a bot. It has the capability to scan an invoice and then pick out the required fields, such as the name of the vendor, the details of the products being sent, or the cost of the product. There is an AI functionality that allows a user to program the required fields to be extracted, and the bot automatically follows those rules and extracts the data. Therefore, the AI functionality of Document Understanding is another important attribute that I personally like about UiPath.
I also like the Computer Vision functionality, where UiPath provides image processing abilities for robotic process automation. This provides a big advantage because images can be automatically processed without involving any additional tools. With an API, we can automatically link the Computer Vision engine and start extracting and processing images at a quick rate.
UiPath is a low-code platform, or mostly no-code platform, where coding is minimal. We can drag and drop all the required steps and then develop a bot in very less time. I am good at programming, but even a user who doesn't know programming can easily pick up the tool. The ease at which anybody can learn it is quite high. Overall, it is a 10 out of 10 in terms of usability. It is really easy to use with the tutorials that they have in place. Everything about it is quite simple.
We use Orchestrator to keep a track of all the robots that are deployed, monitor the logs, and deploy the robots on the runner machines. We use Orchestrator to upload the bots from Studio to the cloud and then deploy them to runner machines across our virtual machines. Once a bot executes, we get the logs, and if needed, we can monitor them to check that the processes are coming in smoothly. In case of any failures, Orchestrator also has the functionality to re-execute the process. So, we are utilizing the cloud to a greater extent for managing our robots.
The UiPath community is wonderful. It is one of the best communities where we can get a solution for any question that we post in a matter of minutes or hours. Whenever we post a question about any doubt or a bug, someone from the UiPath support team or community replies. Their knowledge is useful for other users who might face the same problem in the future. They have an MVP promotion where if I answer more than 100 questions, they provide us freebies or maybe certification vouchers. That's a good thing that they're doing to grow the community. I'm really enjoying the community members' involvement as well as their support shown during any problems that we face. I have also used Power Automate, and the community support of Power Automate is not that great, but the community of UiPath is very responsive.
reviewer1978716 says in an UiPath review
RPA Developer at a computer software company with 501-1,000 employees
Our company uses the solution to process state reporting uploads for clients.
For one use case, we automated the process of dragging forms, filling in fields, capturing confirmations, logging information, and moving files for upload.
For another use case, we automated the process of manipulating data, setting filters, and generating reports in Excel.
We are now moving to another department that uploads yearly tax reporting files to websites.
We do not yet use AI but have many possible use cases for reading invoices and PDFs so we will try these processes first.
We started using it to automate manual processes from other departments. We service other departments, to begin with, including the media between the business and the IT departments.
We started automating very repetitive manual tasks that the business side typically had. For example, if they had to open an application early in the morning to try to process transactions. Then, late in the afternoon, they would have to do the same thing as well. Now we have a robot that does that in the morning and the afternoon, which saves a lot of overtime since it has to be done at six or seven at night, and previously sometimes people would be forced to stay. Therefore, this way, we save that time and overtime.
Another example would be we use it to download ATM transactions from a webpage. The robot downloads those transactions and then uploads them into our data warehouse, which reports for them. Normally, we don't have that information there.
Another use case would be in a department that would print a bunch of wires late in the afternoon. The department would print them out physically and store them somewhere where they review everything later. Now, with UiPath, we scan the transactions from the Fed, and we just print in PDF and send it to them via email, and it saves a lot of time.
From a development point of view, the Studio tool as the basis of componentized architecture has been a really critical part. You get out-of-the-box, componentized architecture to jumpstart or accelerate development and that's a very key feature.
When talking about deployment, you have a very robust infrastructure to manage your automations, the robots, and how they can be configured, deployed, executed, monitored, and maintained.
When it comes to process discovery, it has excellent front-end tools and capabilities vis-à-vis Task Capture and Automation Hub.
And at the back end, the notion of botting sites to monitor and manage your robotic infrastructure and reporting on it is pretty great. These are all pretty good tools.
The ease of use is because of the UI's capabilities. The fact that it has a .NET Framework, from a developer's point of view, makes it a very easy product to jumpstart into. But what is key is the ability to do really fine development activities. You really can get to a nuanced level of development for complicated and robust workflows. The tools are definitely well constructed to allow you that kind of flexibility.
A really good example would be if you are doing something with OCR to read a PDF. You can vary the OCR engines and test them out to determine which OCR engine will give you the best results. That's pretty good because you do get into situations where one engine may work better than another.
We can also implement end-to-end automation and that is critically important. We always strive for what I call "straight-through" processing, where we're trying to handle all the use cases based on business rules. We're not always successful, but that's not a bad thing. If we can take 60 percent of your processes and automate them with straight-through processing, where everything works, your exceptions are a much smaller work set. That has had a significant impact on clients. For one of my clients, where we have worked very hard, they have better than 90 percent "throughput," meaning that 90 percent of their transactions go completely through the automated workflows. The client has been incredibly pleased with that.
We also use the UiPath Academy all the time, in two ways. Internally, we avail ourselves of all the courses. It's especially important to understand new updates and releases. It's a great place to go to understand what those new features are. That is of real value.
But the Academy is also a good starting point when I want my engineers to be certified. They can jumpstart that process by going to the Academy and making sure they know how the product works. They follow through on that program and complete the training. Once they finish that, we try to get a project or two under their belts, and then have them take the certification exams.
reviewer1986627 says in an UiPath review
Director of Transformation at a retailer with 5,001-10,000 employees
We have quite a few use cases, and a few big ones are creating purchase orders, reviewing invoice PDFs and extracting information from them, and creating customer orders from forms that are emailed in.
I did work on Blue Prism for about two years.
It's been a few years now, so I can't speak to the current state of Blue Prism. That said, one of the ways I really struggled with it, was it just did not have the connectivity that UiPath has out of the box. A lot of applications we use regularly, such as PDFs and Excel documents, just did not work intuitively. I remember specifically having to write the code to handle passworded PDF documents manually. And so, that lack of integration in things that you typically use in every single process was a real frustration with Blue Prism.
That was one of the first things I noticed about UiPath is they handled those integrations much more smoothly. There are many more of them, and they are much more ready. The other thing that I would really give UiPath credit for is they are much quicker to iterate and build out new helpful features. Blue Prism was frustratingly slow to fix these problems once identified. You would face the problem and be forced to solve it with your own code since you couldn't rely on Blue Prism to get a solution to you in a good amount of time, unfortunately.
The option to record processes is the most important feature of UiPath. We can use it to record every action automatically and it is then converted to a workflow. This workflow defines the complete set of processes so that we can automate every requirement.
A related feature that is one of the highlights is the AI. We have used many other scraping solutions, but none of them was effective. UiPath, however, can easily scrape data from webpages and applications and it works flawlessly with any program including .NET, PDF, legacy, and SAP.
UiPath has three components, UiPath Studio, the robots, and UiPath Orchestrator. UiPath Orchestrator is a web-based application for deploying, monitoring, and scheduling bots. With Orchestrator we can manage everything regarding the bots. We can customize the actions, but there are also templates. For example, one of the templates enables you to upload to OneDrive from Excel sheets. We just add the parameters and the automations are done.
We have used a few of the UiPath Academy courses, basic classes, because we use the Community Edition. When we move to the more advanced version of UiPath we'll be doing more of the classes. The Academy is very user-friendly. We don't require any further lectures or other sources for learning. A user can watch these videos and start operating the next day. All the actions and features, everything, is clearly demonstrated in the videos. It has proved to be very informative for us.
Kryon RPA: PDF
The stability is pretty good. The only unstable part is Studio where you build this stuff. In our version, the 5.25. It has a memory leak. If you leave it open for too long, eventually it just freezes. Saving your work, closing, and opening it just once a day is all it takes. However, this is a bug that I have noticed about the stability of the actual tool. Our production console and robots have been rock solid.
We are still a fledgling operation with it. We have one guy who works part-time on the PDF and another full-time contractor working with the business to build more bots and wizards and also finding more opportunities. Then, there are two of us who are dabbling in it in addition to our regular jobs.
It is also helpful for certain one-off updates. I am a support analyst myself for a lot of our software. People in the business will come to me with really simple problems. E.g., HR had to send out an email to every intern with some of their employment credentials and links to sites for things that they needed. However, they all had to be personalized. Each email needed to have unique information to each candidate in it. So, they built the template real quick. They handed me the email and we dumped a list of the interns from our HRS system on it. We just threw that in the bot real quick with a couple of loops using the email template with some variables and were able to send out an email to all the interns in minutes, which could have taken a whole day, if done manually. For one off things like this, it's such a simple tool and really easy to use.
While there are other ways of doing these type of tasks, e.g., a lot of HR systems have some sort of bulk email feature built-in to send new hires information. Our HRS doesn't have that or maybe it's too clunky to use. This just makes it super quick.
We also use a lot of similar things with one off SQL automation where we could build a complicated script and run that. However, the bot can run a loop of queries for whatever variable it might be and spit out a report. This takes literally minutes to build and run versus hours if you go different paths. This makes it a very sleek little one off thing.
IBM Robotic Process Automation (RPA): PDF
The primary use case is the development of facilities using artificial intelligence, specifically Robotic Process Automation (RPA) to perform tasks across business systems and applications in much the same way as human workers do.
IBM Robotic Process Automation is an RPA tool that is used to automate any repeated simple/complex tasks with ease. IBM Robotic Process Automation is one of the simplest RPA tools, having a simple user interface, and it is very easy to get hands-on with this platform.
It has vast learning resources available, too. Use cases include extracting data from scanned PDFs. Using IBM Robotic Process Automation made it much simpler to scrape data from scanned PDFs and convert it into standard Excel format, as per requirements. We also use it for portal automation. AA makes web automation simple and our manual tasks have now been automated. Our portal is for making client bookings of the client. The bot reads the Excel file shared by the user and accordingly, makes the booking in the portal with minimum time and with high accuracy.
reviewer1468062 says in a BotFarm review
Senior RPA Developer at a tech services company with 201-500 employees
The most valuable features are the portals for extracting data from PDF files, appending data to SAP, automating the SAP, downloading reports, and mapping and creating the reports accordingly to your requirements.
The solution is great to automate any repetitive tasks, which you might do on a daily basis. For example, the organization may need to be generating invoices or extracting data from PDF files daily. It is very versatile in what you can automate.
Fortra Automate: PDF
reviewer1417143 says in a Fortra Automate review
Business Analyst at a tech services company with 51-200 employees
We didn't actually deploy the solution. It was basically testing the product. It was just some simple testing we were doing. We've tried downloading reports from the new RP system, using RPA, and doing some manual uploading from some PDF files into our ERP. It was just used for some super simple operations to try it out and get a feel for it.
reviewer1550007 says in a Fortra Automate review
Product Manager - RPA at a security firm with 11-50 employees
I primarily use the solution for giving the sessions to the clients and trying to get them to set up AutoMate in their organization and also help them to design and create a workflow.
For example, one of our clients, for a healthcare chain, was having a lot of COVID patients coming in in 2020. Their SAP systems are on 15(16) Field information had to go on to the Department of Health site, as all the blood samples are tested in the government hospitals. There were lab technicians keeping the SAP application open and they were copying all these 15(16) Fields of 2000 patients end of the day into the DOH website. That was taking them a lot of time. Two other people were hired to help.
What we did for them was automate the process. We went into the SAP system and every three hours would download that information, then, we would go to the DOH site, upload these 15 Fields for all of the patients.
After two days, we could go to the DOH website, and download their PDF document, which was a report on whether they had detected COVID or not. For the data we download we would enter the date into that Excel file for the hospital and attach that PDF document onto the top record of the patient. This way, there's complete information about the patient. With this solution, the cycle was complete.
We use HelpSystems Automate primarily for file manipulation, such as moving files from folder to folder and tasks that other tools can't do without some programming.
When files come in, we want to send them to specific locations based on their names and based on the results of IF statements. The solution makes this kind of work more straightforward and more drag and drop.
We also use the product to move Excel spreadsheets or PDF files and to convert PDF files; it's a powerful tool for transferring information. It has a playback feature, but we don't use that in our current environment.
We have two servers running the solution; one for development and one for production. Going from development to production is as simple as dragging the object over and putting it into production with little to no change, which makes promotion straightforward.
We get a data file comprised of multiple reports, and it's a text file. We use the solution to split the text file into individual reports, and then we can drop them into a folder, and they get picked up by another tool, OnBase. That is an essential task for us.
We also use the tool for retrieving data files and sending them out via AWS or Google Cloud, as it has cloud-based capabilities.
The tool works behind the scenes; we created a process that reads many data files, matches them to a SQL database and moves them to the correct folder while collecting information required for other processes further down the road. That's mainly what we use it for, and I'm responsible for maintaining it. Automate makes my job easier because I don't have to keep rewriting scripts or changing file names; we can quickly change a database file, and the solution picks that information up and processes it.
For example, we get a file that has ten reports in it. We take that file and run it through Automate, which reads the data file line by line and breaks it up. Line one through 1000 is one report, and 1001 may be a second report. Automate handles that repeatedly very well. It then reads the database to determine what the report is and where it is supposed to go. If a report doesn't match any database parameters, it's simple to go into the report in Automate and add the condition.
ABBYY Vantage: PDF
We are using this solution for PDF reading capabilities for some invoices. We also utilize it to read DW4 forms.
reviewer1645167 says in an ABBYY Vantage review
RPA Developer/Consultant at a tech services company with 1,001-5,000 employees
We use it for document processing. We have PDF documents, and we need to extract tables from those documents. We use ABBYY FlexiCapture to extract tables.
reviewer1647012 says in an ABBYY Vantage review
Sr. RPA Applications Engineer at a tech services company with 10,001+ employees
It is saving a lot of time, especially for the users who are doing the same tasks on a regular basis. Previously, they were manually copy-pasting from the PDF files to the legacy systems. By using FlexiCapture's integration with UiPath, we are able to automate a lot of complex processes and save time.
We were using the default OCR tool that came with the UiPath software. It is integrated with Google OCR and Microsoft OCR, which are okay for smaller, simpler documents, but they're not going to give you the control that you can have with ABBYY. The engine itself isn't as good.
ABBYY is definitely more mature. It's all-around better. If I pass through an invoice PDF, the percentage of getting everything right with ABBYY is higher than it is with the others. It is definitely a lot more expensive, but I can tailor what I need to each document, and I have multi-lingual support. I can pretty much just get behind what ABBYY is trying to read and make sure it is reading everything correctly, whereas, with Google OCR or Microsoft OCR, I just worked with whatever came out, and I had no control over it.
Microsoft Power Automate: PDF
reviewer1476138 says in a Microsoft Power Automate review
Digital Innovation Manager at a consumer goods company with 10,001+ employees
Microsoft is gradually becoming better, but for RPA, it's not fully there yet.
If you are looking for a low-code, simple to deal with email and extract a spreadsheet, then Microsoft is a good option. However, if you have a complex RPA use case where optical character recognition or PDF ingestion is needed then Kofax is a better choice.
I'm responsible for the center of excellence running Kofax as an RPA solution, and not for the Microsoft Power Apps.
I would rate Microsoft Power Automate a seven out of ten.
reviewer1294329 says in a Microsoft Power Automate review
Senior Product Manager Data Science at a government with 1,001-5,000 employees
We set up a process to monitor Twitter so that whenever specific hashtags that we cared about were used, the whole record of what was tweeted out was captured and stored into a SharePoint list because it was free and easy to analyze as well. That has helped. Event triggers, several different connections, and what you can do with the information once you have it have been very helpful.
We also used it as a one-time solution in a scenario where records were captured in a Power App, and oftentimes, those records, which were almost like medical records, would need to go to another team one at a time. We used Power Automate to capture all the information that was stored in Oracle. From the record, it would put the information into a Word document, convert the Word document to a PDF, and then email the PDF off to the team. All that was done behind the scenes with the user clicking one button. It was great.
I use Microsoft Power Automate as part of my job as an RPA developer. The solution is part of everyone's Office 365 account at our organization.
The solution is used as a primary tool for providing RPA solutions. We've created an automated desktop flow for the whole process. It includes three platforms.
We use the solution as an extension of Power Apps. We create files and SharePoint using flow by converting HTML code into PDF.