The features that we have found the most valuable are the integration of different third-party support and productivity services.
Robotic Process Automation (RPA) Integration Reviews
Showing reviews of the top ranking products in Robotic Process Automation (RPA), containing the term Integration
Kofax RPA: Integration
I haven't been exposed to the solution on a micro-level. Our senior technicians would be able to better answer the question about valuable features.
The pricing is quite good.
Kofax has already had the capabilities in terms of the OCR performance so that's one of the strong features.
The drag and drop functionality is quite good.
The solution allows for integrations, which is quite helpful.
Pega Robotic Process Automation: Integration
There has been integration with a robotic manager and when patches are created and released, they can easily be deployed to new machines. This is a very good feature compared to other tools, where they have to be done on the spectrum machines immediately. With this solution, we have the choice to delay the deployment of patches to particular machines.
The OCR capabilities of the solution could be improved.
The ability to call different website services from the server would be helpful.
The solution should offer integration with applications in Citrix.
Automation Anywhere (AA): Integration
Its integration with source control is very refreshing. There could be a little bit more maturity around how to do some of the features, but not having to go outside the app, not having a separate set of procedures, allows you to check in and check out right from within the app. You can make edits and uploads and undo your checkouts. That integration is very nice.
It really does have a great dashboard. It has Bot Insight, it has MetaBots, and IQ Bots. It has so many features where it can read a file and loop.
My advice is to get started and get help. It's very useful to have consultants come in to help you get started. That will kick-start your implementation journey. Also, look at it as a journey. You won't get to an end-state where you will say, "Alright, now I'm done," because you will have to improve your implementation at all times, keep progressing, moving towards AI.
In my opinion, the vendor you choose in the first year is kind of irrelevant. But when you come to a point where you're about to scale up, then it's important to be associated with the best vendors out there. For us, being a customer of Automation Anywhere puts us in a really good place to keep progressing and keep scaling up.
It's important to remember that we are not doing a full integration here, we are doing RPA. It's okay to do 80 percent of a process - the high volumes - and then do all the exceptions manually. You won't necessarily get a good enough return on spending an extra month to do all the exceptions. You want to go live with the volume that represents the 70 or 80 or 90 percent, as soon as possible. Then see if it makes sense to handle all the exceptions, the last ten to 30 percent. It's important for us to be able to deliver fast, as well as securely and controlled, and with the MetaBot and the other tools that we have through Automation Anywhere we are able to do that.
We have automated in excess of 60 processes running on 17 Bot Runners, which are like machines we can operate 24/7. We have 15 bot developers and we are closing in on capacity so we would have to expand the number of licenses soon.
Our plans for ramping up are about pumping out new processes every other week. We're working Agile with the RPA so we try to do short sprints and deliver something every week. The usage increases every week actually. I'm not sure if we are planning to have even more developers because we don't want to be in a position where people don't have things to do. We would rather have some backlog rather than having to fire five developers.
We are planning to continue on the same pace and ramp up the number of bots, rather than the number of developers. We did a proof of concept last year with Automation Anywhere's IQ Bot which was very successful. We did not, however, have time or resources available to implement that last year. Hopefully, this year we will have time and we will make the purchase of the IQ Bot license and start using their cognitive platform. We're thinking about implementing their analytics platform as well, because that's very useful for keeping track of our progress.
I would rate Automation Anywhere at nine out of ten. There's always room for improvement and, of course, we would want cheaper licenses and would want them to add even more things that we haven't thought about to their product. Still, we're really happy with the software provider that we're using.
A lot of clients I work with have legacy systems and a lot of API access is not available. Some of the systems might be running off a server located somewhere else, while some would be running on a mainframe and I'm actually restricted to working with the screen. So these clients have a very good use case. If I'm working with the screens, Automation Anywhere really does help me because it gives me the control over the screens. If you are not looking at integrating legacy software, Automation Anywhere gets the job done. But if you need integration then you start looking for other RPA tools.
It definitely saves time and effort. Improving the workflow, that's not something Automation Anywhere provides. That's a different challenge altogether - to do a business process improvement so that automation gives you even more value. That type of process works in combination with Automation Anywhere, but it's not a part of Automation Anywhere. So the process improvement is separate. We optimize the process and then we run it through Automation Anywhere.
You can probably use any similar tools. But Automation Anywhere is one tool that actually gives me automation capability right at the start, without worrying about process improvement in the first place. I can just act like how another person would. Whereas if I do a little bit of process optimization, I can use another tool also. If I get access to APIs, I might use Blue Prism. If I get access to web elements, I go the way of UiPath. If it is a human-mimicking behavior, that's where I use Automation Anywhere.
Our company is an implementation partner for Automation Anywhere, and XLNC Technologies is a consulting organization for whom I work. I am the head of delivery operations.
We are working with around 14 clients who are on Automation Anywhere. We have been able to recommend and further resell starter and enterprise packs. Implementations performed by us scale up from one bot to 10 bot runners
My primary use case for Automation Anywhere would be the one which yields higher ROI , has repetitive tasks to be performed and doesnt involve fuzzy logic for sure . Cases that we have achieved success are extraction of data from PDF's , SAP automation, AD Integration, Integration with CRM and Payment links, KYC documents and web scrapping. Listed are low hanging fruits and will boost confidence of the stakeholders in the RPA deployment , recommend to look at such use cases when looking at Automation Anywhere and its implementation.
Generally, it is used in the banking and financial domains for Oracle and Java-based systems. We also use Automation Anywhere for integration where a third-party tool has to be triggered.
My advice would be "due diligence." Make sure you read, and make sure you engage the Automation Anywhere team and the support. We didn't, but we didn't have to. But do due diligence based on cost, and scale, and really what you're going to do.
RPA is the hot word right now. Everybody wants to do RPA. But what we did is just put it into our arsenal of other tools. It's not the golden bullet. It's not the one that is the end-all. It's just one of the tools in the arsenal that IT has. That's why we chose not to spend $250,000 and, instead, to spend much less. Sometimes RPA is the answer. At other times it's system integration, and at other times it's just raw development. That's what I even tell our customers. That's our toolkit. Our arsenal is developer's RPA, and we use a third-party integration tool as well.
Just the developers were using it in our organization. They tout it as it's user-friendly: Give it to a user and they can do it. But we didn't discover that at all. We couldn't just hand it to a user, so our developers were taking the processes and applying them with development code behind them. Automation Anywhere has "record-the-screen," but when our users were doing it, they would move an icon and it wasn't smart enough to find the icon that had moved.
In terms of extent of use, it was used daily for some of our daily processes. The finance process I talked about earlier is one example. We automated that and that robot ran on a daily basis. As for increasing our usage of RPA in general, we scaled up pretty quickly. Internally, we have four or five robots running 24 hours a day, seven days a week.
While the Automation Anywhere University is good, the estimates of the time that it takes to complete it are a little low, especially when you start watching all the videos thoroughly. One of the courses that they said would take six or eight hours was closer to 16 to 20 hours.
I noticed that from version 10.5 to 11.3 the number of clicks to start a bot through the Control Room and Schedule Manager have increased. In certain cases, I would like to see that become simpler, faster, and easier.
I would love to be able to schedule things based on business case. Right now, the Schedule Manager is either once a day or pick days of the week with times. However, in the financial industry, I sometimes need to run something on the third business day of every month. At the moment, I don't really have a way to set that up in the Schedule Manager.
I would like to see some improvement in error handling. That would be great. Sometimes, the errors that you get back are awfully generic. It is like you have to do a lot of research to figure out what the issue is.
I would love to see a little smoother integration with some different types of platforms, technologies, and user interfaces.
It's definitely useful. I went through the enterprise client and the Control Room and using it, a lot of processes can be automated. The SAP integrations look to be very useful. We have a big SAP shop, so a lot of processes can be automated using that integration.
There are three parts to the savings:
- the number of hours saved
- the dollar amount saved
- how streamlined the process is.
A manual process can be one where an email is sent and then another email is sent to get the approval, and they have to wait one or two weeks until that email comes back. That full manual process can take three weeks while the automated task takes about 30 minutes.
I would definitely recommend Automation Anywhere because it's pretty simple, non-invasive, and easy to handle.
In terms of integrating this solution with other applications, the majority of the ERP vendors are now coming up with built-in robotics. That's something which Automation Anywhere has to look into because currently, with Automation Anywhere, integration is an add-on product. Many other technologies are actually integrating RPA into their products.
I haven't taken courses at the Automation Anywhere University, but my team has. It's pretty simple. It's pretty easy.
I would rate the solution at seven out of ten because of the stability issue. Hopefully they can enhance the product. I heard that in the next release they will have natural language processing, not only for English but for other languages.
Among the most valuable features that we've been able to utilize are the screen scraping and object cloning. These are two features we have used so far. We are also utilizing the API integrations.
We are excited about the solution's cognitive document processing, IQ Bot. That's an interesting one and we have at least a couple of customers who are looking for those features.
- The most valuable features are Excel operations and PDF for integrations.
- It's very developer-friendly.
- With IQ Bot, we can now include cognitive automation into our process. The cognitive document processing is pretty good with IQ Bot.
I really like the way the bots are built, being able to take some old, clumsy screen that someone built and put your keystrokes and your information onto it. It's fairly simple as well.
I would describe bot creation with the word "exciting." We've had a couple of team members who have been working on projects who say, "Let me do it!" They're familiar with the product and they're very comfortable with the building process.
I also very much like the integration of this solution with other applications. We have some old web applications that we've been using, and we've been writing some of our own DLLs to integrate with it. It has worked really well. We're able to have the bots take over what would have been a lot of training and a lot of meticulous work.
I love the XML feature behind the scenes.
The flexibility: If there is anything the tool cannot do, we have the ability to make a MetaBot to achieve that functionality. The overall flexibility of the tool makes it very useful for us in our landscape.
We have integrated it with everything from standard off-the-shelf products, like SAP and Oracle, to custom apps that we built within our landscape. The integration to other applications is very good and easy.
The most valuable feature is its Excel integration.
We have business users who are developing bots using this solution.
The solution has improved our organization through its integration with other products. We can integrate multiple platforms through the use of Automation Anywhere via the use of third-party APIs, so there is no human intervention at all. Everything happens on the back-end.
Automation Anywhere is excellent for integrating with other solutions. It provides the ability to leverage the APIs of third-party solutions. We use some of the already built-in MetaBots to then scrape the data and manipulate independent data that we need in order to integrate with other third-party solutions.
Give the tool a try. Get the business onboard. Build some quick, easy bots at first. Then, you will be able to see the capabilities of the tool quickly.
Our bot creation process is fairly robust. We have a centralized model with a good process from beginning to end, which involves engaging our business partners, documenting the as-is, looking at the future state, then coding the automation. We leverage Automation Anywhere, as a tool in our tool belt, and one that we've enjoyed adding because it increases our capability to change processes going forward.
Automation Anywhere integrates pretty well with the other applications that we use. We like to go the API route through Automation Anywhere, but we are always looking at customer web portals or the portals of our suppliers, as we have pretty good integration capabilities.
We are looking forward to using the bot monitoring capabilities in version 11.
We haven't used the cognitive document processing capabilities of Automation Anywhere.
I have not taken any Automation Anywhere University courses.
My current and previous companies have had stability issues.
I started on version 11 of Automation Anywhere, then when I joined a new company, they used version 10. Therefore, I have seen both versions. With version 11, some of the development stuff was a bit clunky in terms of the tasks that we were performing. They didn't perform as expected, or perform properly, when we were developing the bot. Then, once we deployed it into production, the bot would run for a specific process and work properly about 10 times, but on the eleventh time, it would break. It was always random. Nothing had changed at all, in regards to our system, architecture, or infrastructure.
On version 10, things had been a bit more stable. We made sure that we build code which effectively captures all use cases and exceptions, but stability is key. When you're building automated solutions using bots, people are already skeptical and hesitant to adopt them. Anything you can do to improve the stability is definitely helpful. Ultimately, it depends on what your goal with RPA is. If you're using RPA as a stop-gap to build large-scale system integrations, then it's very helpful. If you're using it as a be all, end all, then stability is your number one concern.
Automation Anywhere has some limitation with its integrations. You can build your logic with MetaBots and .NET components, e.g., if something is not gathered by Automation Anywhere or built into functionality, you can write a MetaBot. A MetaBot is like an external component. You can write it through C# or .NET code, and make a DLL, and import it. This is not open to all data types or EXE functionalities which can be written through C#. You have to define your variable types, matching them with Automation Anywhere existing variable types. Because of the knowledge required, I cannot let another person, who doesn't know Automation Anywhere, build my external DLL code.
They are already addressing some concerns that I have been having, like having cascaded code blocks, which is very helpful for developers to use when finding and debunking codes. Until now, we haven't had collapsible cascaded code sections in Automation Anywhere. This is not typical, as any IDE will usually have it, on any language.
The current interface for business users is not intuitive, as it is a code-based view. A business user wanting to develop a process may find the interface a bit elusive. Automation Anywhere is now working on a process flow view with a drop and drop, which should be better for business users.
There is not much guidance for implementing DevOps, like continuous development. Nowadays, the technology has come for the deployment part, it should be part of Continuous Integration and Continuous Development (CI/CD).
With Jenkins or TeamCity, there is a job, and I want to see them have integration with Automation Anywhere, so we can directly code check-in, run, test, and deploy. Now, we are doing this manually for deployment, but I want to see a DevOps job instead.
No tool will ever fix your company. It is always about the stability of processes, understanding your scope, and what your problems are. This tool is a great tool to help with that once processes are stable. It will always be dependent upon people. Make sure you program the bot to help people, not what you think it needs to be. There will be a lot of meetings, scope developments, and data review, which will need to happen first. Then, if you get good with that, then the tool's going to be excellent.
So far, everything has been good with the solution. It is a great tool.
The integration works very well. We have integrated it with four other software tools.
From a developer perspective, the solution is very simple. Our end users don't really see it. They just see the end result.
I would like more integration around main applications, e.g., SAP.
Automation Anywhere has to keep their RPA tool connected to everything to maintain it in the RPA market.
Automation Anywhere is a great tool. I have been in IT for 30 years, and am amazed at how far we have come with technology and tools to help us do our jobs. The ease of use and the power which the product offers you in a matter of minutes, if not just an hour, and what you can create with it.
It integrations really well with other applications, as long as you have access from the same computer which you're running the software on to your other systems. Then, it can interact with those other systems just as if you were any user who is on that same computer. From this aspect, it is more powerful than other tools which I am familiar with.
We are just starting to look into the solution's cognitive document processing by doing a proof of concept.
Early on, I did try a few of the Automation Anywhere University courses, mainly to get familiar with what was available, so I could guide others to the website for training. At this point, there hadn't been much there that I needed for myself. However, we have looked at the courses, and we are encouraging a lot of our business users to take advantage of the tools.
The important thing about any RPA tool is it has to be a collaborative effort between IT and the business. It needs to be driven by the business, or it won't be successful. An important overall goal or strategy to have as you start your journey: Have good buy-in and ownership from the business. They have to want to do this and take advantage of this new tool.
A lot more can be done to make the solution easy for developer to use. While it is good as a base product, it could have better logging and alerting features. We would like the tools to have more usability, especially for humans in the middle.
Other solution features which are offered by competitors, like IBM, should now be part of the part of the Automation Anywhere suite of products.
I need high value products to be created, so I need integration with other solutions. Machine learning and AI need to be integrated with Automation Anywhere. While IQ Bot is a good beginning, our company does not work with manual paperwork since we are already digital. We would like to see more integration with cognitive tools going forward.
For our interorganizational processes, it has automated some of those processes.
The Bot Store has helped tremendously with accelerating integration from other applications. Especially with Workday, which is one of the main applications that we look to integrate.
I would like to see integration better integration with Excel and SAP.
Our developers are looking forward to code versioning.
I would like to see GitHub or GitLab integration in the next version.
It would be nice to have more screen scraping features for legacy systems. This needs improvement, because it doesn't work very well at the moment.
I would also like to see cloud capabilities, but they announced that is coming.
It interacts well with other software tools. Other automation tools have trouble with integration.
The tool provides everything that we need to design a task. It is a complete tool.
The tool is user-friendly and easy to use. It is easy to understand how to automate a task.
The bot creation process is easy, manageable, and everything is well-organized for a developer. Everything is centralized.
There are some places where Automation Anywhere needs improve a lot, especially from an integration perspective. We have had to build our own scripts to make this happen, building a bot in Automation Anywhere, along with some scripts. However, we have not yet implemented the Automation Anywhere MetaBots. So, once the MetaBots are implemented in our area, we should be able to achieve more.
If the bots become more stable, we can completely avoid using our additional scripts.
I would like to see the record management, data tracking, and database feature. Some of these have been implemented in the version 11. I have not used the latest release, version 11. Also, if some various cable features which come out with it, that will be really helpful.
The MetaBot is a valuable feature.
We can integration with other APIs, which is a good thing. This helps us with our database integration. For example, we have done an SAP integration, which is great, since SAP has a lot of manual work.
IQ Bot is great for invoices. It helps a lot for retail and on the SAP side.
Ease of use:
- For developers, the Control Room components are very popular. They are easy to use, along with the Repository Manager, Schedule Manager, and maintenance of the bots.
- For people from nontechnical backgrounds, the product is simple from them to use. Everyone can learn it. It takes about two weeks on the tool.
- The ability to use previous integrations is valuable.
- With Automation Anywhere you can read and extract CSV data easily. You don't need multiple commands to read it.
- The user interface is good. Whatever I've done, the user interface has been very good.
I would like to see a lot around API integration going forward, like the ability for other systems to talk to the AI better by opening it up. I would like to see more chatbots or anything in the journey of making it truly immersive for human workers working with these bots.
There are a couple things that have room for improvement: Its openness and more APIs should be exposed to allow people to integrate. How do you make it easier to integrate back with this technology?
I would like it to do more predict, which means if I have a thousand bots in product, how do I check which of the bots may be at risk of failing? This would really help in supporting the bots when scaling the programs.
The ease of visibility in the processes which are working is its most valuable feature. Take, for example, Control Room. This is one of the unique features of it, because at the end of the day, the business does not need to know whether it is a MetaBot, IQ Bot, or anything like that. How do you give the terms of business visually? Control Room is another big aspect of it, from the business point.
From the technology point of view, it's supposed to do activities that you do in your day-to-day life. It is also extendable. Of course, we cannot solve the whole world's problems, but we can extend it with additional coding, and things like that.
There are two things that it can provide you.
- Quicker in automating the task that you already have. Sometimes, the process is chaotic, but the business needs that way to perform some tasks. With automation, what we can do is accelerate the automation, then look into the process optimization that we engineer. That's where we help. Automation Anywhere helps us to accelerate the adoption of automation faster so the customer can realize the benefits.
- It allows us to look into processes for what can be optimized.
That is where it helps.
Last month, Automation Anywhere launched communications, which is a very good thing, because now you can actually get two things when you use it.
- Developer experience: The developer experience is essential for the product to go into the market very well. So, that helps it.
- You want to get back what is working and not working, what the developers wanted, etc.
What Automation Anywhere brings to the table is how do you actually connect these things together? The purpose of automation is automating the task that everybody is doing in their day-to-day lives or some of the cognitive side of it.
The availability of Automation Anywhere to integrate with various applications. whether it is SAP, web forms, Excel, or PDF, exposed quite a bit of integration opportunities within the organization. Definitely, this is one of the key assets, as well, for us to work better with the customers.
One of the biggest challenge that everyone is facing is in the format of the document. The document management processes that IQ Bot gives has very good functionality of how you can actually take unstructured data and make sense out of it, connecting inferences, then making the data available to the user. So, IQ Bot is one of the best tools that I can think of in that aspect. This solves the problem of various document structures, document formats, etc.
The Bot Insights is one of its big assets, because that's what they have given you the visibility.
Prior to working with RPA at BP3, we worked with a lot of process and decisioning technologies and also integration technologies. So, we have sort of a unique perspective on how RPA fits in and plays well with others. In particular, we're partnered with IBM and Automation Anywhere, and we saw them on stage together, presenting. I think Automation Anywhere, from a cultural perspective does a really good job partnering, but they also provide a product that works well with other products, so it's easy to integrate too. It's easy to include it in a solution and easy to use it to drive a solution which leverages other technology.
In today's market, you have to think about, how was RPA today and how would I rank it versus what it can be in the future? I think we're in the early innings of what RPA can be and what Automation Anywhere can be. We saw some indication of that in the keynote speeches. You can just get a sense for the scope of the vision and where they want to take RPA at Automation Anywhere. I won't try to rate against the future, but I think we're in early innings, two or three versus a ten. But, when you compare it to the state of the art today, I'm really impressed with RPA, and I think it's an eight or maybe nine (out of ten).
I would recommend if you're starting out to look at RPA and how to get started with Automation Anywhere. That is the first thing that I would do is. Find a couple of problems that you think are easy, then take a moment to really think about problems which are important to your business, because you have a limited amount of focus for your business. You business only has a few limited resources: time, money and focus. If you're going to spend that focus, spend it on something that matters. It's fine to do a research project or a pilot project, something that doesn't have a lot of risk. You have to do something that matters for your business, and if you're having trouble finding that and making it make sense in an RPA context, then I'd say work with someone who can help you reframe the problem so you can find those opportunities.
People are now trying to automate many different kinds of technology. They have use cases related to ARP, invoicing, and three-way matching, for example.
We are seeing an incremental need for legacy systems which do not have an architecture in place or API integrations. Our customers are doing things like simple website scraping, bringing the data into Excel, taking that data and then putting it into their legacy systems. We are seeing customers that read a lot of invoices.
Our customers have been using Automation Anywhere for a lot of integration purposes. They've been using it not only for process integration but for application integration as well.
From a QA and development perspective, we would like to communicate with the tech support through email and have that put in the dashboard. This would let us better track the ticket and make it easier for us to communicate with Automation Anywhere.
They recently integrate Oracle and SQL. I would like to have more integration and feature going forward.
We have had issues with stability in the past, and there should be a function that helps you to find out what is wrong with your environment that is causing the automation to fail.
We would like to have more information on how Python integration works, and how easily it can be done.
The implementation process is complex, as there is integration with other applications. We need to understand the other applications' requirements. It requires us to convert their business logic into automation. That is where the complexity is.
We perform the integration for this solution with our in-house team.
The GUI can be improved by making it more user-friendly.
Python integration is coming with the next release, and they should expand on that.
There are several things that would improve the product. I would like to see them include a group chatbot and make the IQ Bot more stable. Just those things would be great. Adding those kinds of features improves what we can do with the product. Using a client control room concept to ensure that everything is based on the web login, would also be great. Obviously we know that the development of new features will take some time.
We are expecting those kinds of features in the future. We expect more AI integration in our technology.
Automation Anywhere could use to be more stabilized. The product is becoming more stabilized with newer versions, but there are various things that still need to be stabilized. In the current version that we are using, we have a Control Room where the client will sometimes get disconnected. This will result in downtime. Therefore, we need some stabilization from the tool perspective. We don't have any other option than to raise a ticket to Automation Anywhere or get in touch with their support to get the issue resolved. So, we are having downtime. This can be improved.
We are not completely okay with the IQ Bot. We previously used version 5. The newest version does have more accurate results.
Technical skills are required to use the product. With these tools, technical programming is still required with the guidance of technical people. Business people can go ahead and try building a few smaller processes, then when they gain technical knowledge, they can use this tool to their full advantage.
Most of our processes are attended automation. It would be great if more processes were unattended automation, so we could release more FTEs.
We are currently using third-party Taskbots. We would like Taskbots directly integrated into the tool.
The most valuable feature is that we can automate data manipulations. We can save IP's, we can save time, we can use manual reports. The main benefit of this tool is that it is a robust solution.
The feature I think that helps most is the ability to integrate. There is SAP integrations, SAP application integration, web application integrations, and email integrations. We have multiple features — there are a lot of features. They are also very good features which enable us to do many things.
The product is not working sometimes with the methods we prefer. If it is going to be a flexible product it should include some more common things. There are so many small issues with the product it is not as good as it could be.
The whole package that Automation Anywhere offers is really good. The variety of commands that it offers made to play well with other integrations. It could be using a C# module, code on JSM, the APIs — I want to use database XM. Ultimately, I want to use anything that makes it friendly for me to accomplish what I need to. That is a help because it often will be something I have already learned, it will be easy to access, easy to build, easy to sustain — as long as the commands work as expected.
Unattended Automation is the best feature for me. Because I use it extensively, it is also one feature I am very familiar with and so it is also one of the areas that I would like to see more improvements on. Any time I speak with people who promote automation and say that it is unattended, they may have a machine perform an operation. Very few understand that each unattended operation packet is unattended at all times. No matter what time of the day, if you just click Run once and it operates to get something done. You don't continuously relaunch it.
One of our security applications requires a lot of newer features in terms of recognizing a lot of objects that affect security, whether we are talking about the security of a building or of an enterprise. Integration automation is now building on growth, e.g., I can upload Microsoft and Azure integrations. This will help us in order to scale up the machine learning aspect, which is required in the applications which we are developing.
One of the challenges that I think should be resolved — from what my team was telling me — is that Automation Anywhere is not able to connect to a database directly. I have not evaluated this myself. There may be good security reasons for this, but it should be possible.
For example, generally what we do now is to write scripts to push the data from the database and into the automation event. The direct access feature — which is not available according to my team — could solve the issue with the scripts. There's room for improvement in making more flexible solutions.
As of now, because I have not used the new version very extensively, I don't have any reference to say what features should be added to the next release of the product. My one thought is that I don't know about the possibility of reading from unstructured data and if Automation Anywhere has any features to access unstructured data sources. It would be good if it can read the data and build some intelligence over that to push data to the right application. We do have some requirements from clients in other organizations where invoices will come in to be scanned. Based on the analysis of the data, copies of the data can be sent to different, appropriate applications. We are using different tools to do this now. If this kind of feature for reading unstructured data is there, then it will be easier to incorporate in processes. That is good to add if it is not there already.
There can be some options to connect to the database directly where we should be able to add some data.
There was a limitation where we were supposed to login remotely to one server and carry out some actions. That integration was not possible.
I would like more integration with Microsoft Excel. More screenshots that can be integrated with Excel would help our customers too. It is good that Automation Anywhere is now willing to partner with Microsoft.
I need to be able to work on Citrix with the solution.
I need cloud-based applications. Now, we are manually running the application.
Alert transition is happening in the Python space and on the front lines of AI and with other tools. You have the opportunity to use different data blending tools and data manipulation tools. It would be good if Automation Anywhere could make more plugins available to use with a greater variety of tools and additional options. I think it would be a better product if it had a greater capability for integration.
We had a terrible experience with a local integrator. I don't think that they were ready for the integration/deployment process. We spoke to Automation Anywhere who has implemented more stringent partner qualification schemes to take care of this issues.
The main problem that we see is migrating data from one system to other system. This is where a human comes into the picture. While we can do Excel crude data going into an ERP system, we would like it going forward if the Excel to SAP integration had a higher focus in the coming features.
The Excel functions that we see are currently very limited. While I have not tested it, I have seen these functions expanded in version A2019.
I would like more detailed activity logging of what the client does. Currently, it just shows that a task started, then a task has ended. We want more detail around this for our clients, especially for error logging. E.g., we had to create an encrypted log for our clients to see what happens every second for every step. We made this in a CSV, and that CSV can be accessed by anyone who can change it. If Automation Anywhere could integrate this into the Control, that would be great.
Technical support for this solution is good, and they have provided us with resolutions to our problems. We are partners, so naturally, our support systems are connected.
Normally we need to wait for a message from the technical support team, and then we have to capture screenshots and do some monitoring. We also need to do some analysis. This makes for a huge gap in resolving an issue.
We do have a customer with a technical issue that was taking quite a long time because of their Oracle integration. There was a very long gap in time before resolution, so the customer was a little bit unhappy about it. They have to be able to foresee these types of use cases and ensure that they have a stable tool that is able to cater to my new ones.
Version 11 is a bit heavy. At times, it takes a toll on the computing resources. It consumes a lot for computing power. We have seen multiple instances where computers or the client has crashed because of this particular problem. Automation Anywhere can improve this a lot. However, the A2019 version will be a lot lighter because it is all web-based. In the future, we expect to see lighter version, but for now, it is okay.
The features around holding and handling Excel data need to be improved. They need to be able to handle data tables, data variable, and Excel numbers.
They need more scripting integration.
The integration of IQ Bot, Bot Insight, and other products should be flawless, and the execution should be seamless, so this needs to be improved.
The vendor should make recommendations based on our customer's requirements so that they can make the right choice.
Automation Anywhere will sometimes announce releases or updates in their roadmap, and we wait for them, but they do not happen on time or at all. This happened, for example, when we had an issue with IQ Bot. We ended up waiting for two more months.
We are one of the smaller startups in the area so we experience a lot of issues. Most of the issues have been:
- How do you build up your platforms?
- Automation Anywhere is more geared toward how humans work, and a bot works differently.
These are the specific challenges that we have seen.
Some small issues:
- A bot will be working and the the screen will lock out.
- The app has a password change policy every few days.
- One day, there will be a message box saying that the application is down or not available on a weekend. The instructions will say read the information and click, "Okay." But a bot doesn't understand the instructions because it is not the IQ system.
There are a lot of initiatives going on. E.g., there is one for the Excel part where they are building a plugin in Excel. Those type of plugins would help if they were built in various applications for integration across applications. I would like more plugins overall. It would be nice to have a plugin for all applications, like PowerPoint or any PDF to text converter, to make the tool easier to work with.
On the user side, we have seen issues with user training.
The product still requires programming knowledge. We would like it to become easy enough to use where anyone in the organization can utilize the tool and use the bots. The usability should be at the same level as a Microsoft Suite product. This is on Automation Anywhere's roadmap to evolve toward this.
if Automation Anywhere could bring in object recognition, it would be a game changer. Today, we have a lot of video analytics. People talk about video analytics since I come from the consumer background. We are looking into the latest technologies of facial recognition from an audit proxy, e.g., counting the movement of the products from the counter versus the billing application. I have brought up this inquiry at my last three Imagine sessions but I am not getting an answer. Maybe the demand in the market is less. but people now are looking for this type of solution where Automation Anywhere can bring in some cognitive inbuilt.
It would be great if video analytics could be brought in as a third-party product integration or on the Automation Anywhere platform. I would like the video analytics to be integrated within the next two years. Right now, most people are using third-party tools. Video can be translated into an image and information can be picked up from that, then translated into meaningful insights to make decisions.
Getting buy-in was a major challenge because of the various people not aware of the technologies moving and getting buy-in from top management is a challenge.
A major issue is getting the in-house team trained. I would like to have a better way of managing the teams. The more your in-house team is trained, you're less dependent on your partners or solution providers, thereby scaling up the confidence of doing it in-house. I just visited a booth now on the training part to see what can be achieved so I can go back and tell my team what Automation Anywhere is providing in terms of training.
I have done a lot of use cases. Recently, I have done SAP automation. I worked with MS Excel, a web application, a Windows application, and a mainframe application. We automated three to four applications at once. We automated them in a row where one application's output would be input for another application.
I have done development and production support. I have helped organizations with integration.
New versions keep coming up. The challenge for us is to have the downtime to do the migrations. This could be improved upon. We would like fewer version changes and upgrades happening to the application. While the downtime is not that much, depending on the business processes, there are times few critical processes are running on a daily or hourly basis. We would expect the downtime to be even less for them.
There are a few internal applications that we have where Automation Anywhere needs to be added. We need to get those applications embedded so the integration process between those applications is smooth. E.g., With a Citrix type of environment or VDI environment, we have not been able to get the right information. We have to use the coordinates. Recently. we attended a session and realized that they have come up with an IQ Bot and computer vision technology. Therefore, we have some use cases which we want to leverage.
Our focus would be for them to keep innovating for more intelligent solutions which can merge your text to speech. These types of solutions, along with other ML and AI capabilities, can solve for the larger objective and typically RPA platforms are not able to do. The type of applications that we use are very large and different. They are not the typical ERP systems or systems which normal organizations would have. If they could bring AI and ML capabilities onboard, this would help me rate them even higher.
The most valuable feature of this solution is the SMART Recorder.
The overall developer client has an easy-to-use UI.
The Control Room, scheduling features, and client repository are really good features that make day-to-day bot development and enhancement quite quick and easy.
The PDF Integration feature is also quite helpful, as well as the Send email command that helps us skip a lot of Outlook-based steps that are not necessary.
There are multiple features, like PDF integrations, which are coming up. Task-related features to PDF integrations are coming up nowadays, so people want those executed and improved a lot in Automation Anywhere.
For improvement, I would like to see Automation Anywhere integrating with multiple other technologies. As of now, it is integrating with .NET. When it come to future technologies, I want Automation Anywhere to integrate with Python scripts, and make the execution easier. That will be very helpful, having our cognitive technologies interacting with Automation Anywhere.
Automation Anywhere has been an integral part of this product's evolution in general. A hindrance that we were faced with was companies who did not have API integrations for Salesforce. This is where RPA and Automation Anywhere came in and helped us with integrating solutions which did not have API integrations within themselves. That's how we've evolved in the past two to three months.
A majority of this tool works on automation. For future prospects, this tool should 80 percent deal with neural networks, deep learning, and artificial intelligence and that has to be integrated a lot. As these are future skills, these integrations will help us take the tool to take to the next level.
The most valuable part is that it have the integrated OCR solution within it. All the other solutions do not have the right integration of the OCR solutions. You need to go to two different places to get one solution. Whereas, in IQ Bot, there is one area where you get all these solutions together in one area. That is the most important and beautiful point that I like about IQ Bot.
We need more commands for PDF integration to make it more flexible.
I am a platform architect for the RPA so I deal with all 3 major RPA vendors. I build the Infra for all big setups. I have immense experience plan, design, and building the setup on cloud, on-prem and with different configurations.
I implemented AA in different environments, the AA installation is the smoothest compared to other RPA software installs.
Migration is a little challenging since it requires direct integration with DB, credential vault and all that. Since multiple credentials are involved, it is a challenge to get all the credentials, it should be easier if only the control room credential was required. Versioning migration is still a challenge.
- Cloud API vision and OCR engine integration should be more effective.
- Auto-update of the Bot agent in runtime machines from Automation Anywhere control room server.
- The import and export of the previous version bots to the latest version of A2019 should be more flexible and friendly for the end business users.
- AI Sense recorder should be upgraded with additional features for better results.
- SMTP mail features should come with migration options. All kind of VB scripts and Java scripts which we built using exiting version should support in this version.
Using Automation Anywhere we have built/supported 200+ automation around operations and automated different Sharepoint, Outlook, ServiceNow, and contract processing related use cases. It offers a lot of features, flexibility whether it is through Meta bot, IQBot, etc.
It offers :
a. Zero-install, Web-ready platform: Deploy RPA across the entire organization and scale bots on-demand in a few clicks. b. Use the pluggable API architecture to maximize extensibility and customize RPA to meet unique business automation requirements.
c. Integrated machine learning: Streamline your document-centric processes with drag-and-drop IQ Bot integration.
d. Self-learning automation engine: Create a smarter automation engine by infusing third-party AI technology.
Blue Prism: Integration
We were using this solution for two main purposes. The first was to leverage the OCR capabilities, and the second was integration with Outlook to check email and retrieve attachments from email.
We were also looking at the workflow component, and how to orchestrate the bot and the process flow within Blue Prism.
This is all being done as a pilot project by one of our departments to assess the impact of implementing RPA.
It can be improved more in :
1. Surface automation techniques: using region mode. Identifying images more properly.
2.OCR: Can improve more in OCR, to read text more correctly, currently can say OCR in blue prism only works for less cases and is only effective 50%. so mostly OCR's of Blue prism is very less used and other API's or tools are integrated with Blue prism for OCR techniques.
3. Integration Support: To integrate any tool, API with blue prism. the team support is very less and also no proper details are available in Blue Prism. This can be improved much more.
4. AI: AI techniques will make Blue prism more powerful which is currently not done.
When I am comparing Blue Prism to UiPath, it lacks many features. For example, I am missing all variable types that I am used to having in UiPath.
I don't like that it is so limited, anything that you do feels limited in your capabilities.
Usually, you have dropdown menus with 10 choices but if you need that 11th or 12th one it is so difficult to work around it.
For me, I feel that it is lacking in features.
It consists of simple actions that work quite well together, and the integration is good but the scope of things that you can do is too narrow.
The interface could be brought to a more modern state of the art interface. It still has this gray Windows 95 style, which is outdated.
The way that humans interact with robots is a feature that is very poor in Blue Prism.
The focus is on the unattended automation, for example, robots running in the background at some bank. If you have more digital assistance, assisting humans in their daily work is something that is very difficult and I would like to see this improved.
- Higher standardization of process integration with the customer's internal applications
- Employees orientation towards non-repetitive work.
- Extensive overall functionality and integration with Microsoft products
- The studio is easy to use, and
- The product is feature rich.
I would rate the product eight out of ten. I am scared not to be too subjective because I would go for a higher grade. I still see some room for improvement. I still see some need for integration with other solutions, but I would certainly recommend these to all my customers, comparing it to what the competition has.
I believe that UiPath opened topics of RPA and AI/ML in our company (which consequently led to a shift and much stronger orientation of our company — globally — towards technologies and technological areas like software development, the blockchain, IoT, etc.). I believe that this role ("enabler" role) was crucial and also helped tremendously in raising overall 'digital'/'ICT' and 'programming/integration concepts' awareness company-wide. You might agree that the impact of this scale might be much higher and more important than any time and costs saved by actual automation.
- An easier way to use object-oriented languages
- Better version control with different features
- Git integration if possible.
Creating proof of concepts for Oracle product integrations and form filling for clients. We are also in the works of using it to automate expenses in-house.
- Unlike other leading RPA tools, UiPath provides a great user interface so that a person with minimum technical knowledge can understand the flow.
- UiPath provides a large number of activities which we can reuse as per our need just by changing the properties and parameters.
- UiPath provides the flexibility to create custom activities as per our need.
- UiPath supports integration with various OCR, cognitive services, ML and IoT related services and tools.
- UiPath provides the flexibility to use an unattended robot without the need for Orchestrator.
- UiPath Orchestrator component is a very powerful tool which if utilized effectively, can make the robot management and monitoring very easy.
- UiPath Orchestrator supports using APIs, in which we can get the details from the Orchestrator database.
- UiPath’s recording feature is very helpful to begin the automation process and provides options to choose from recorders as per our need.
- UiPath supports version controlling feature which is very useful when the project is done by sharing tasks with multiple persons in the team.
- UiPath provides various workflow models such as sequence, flowchart, and state machine.
- UiPath provides an inbuilt logging facility.
- UiPath provides scraping of both structured and unstructured data.
- UiPath provides specific tutorial and documentation for SAP automation.
- UiPath provides debugging options usage, in which we can go through each activity along with the process flow, highlighting each action on the screen along with the flow, and showing the values of variables at the run time during the point execution of an activity.
- UiPath provides the facility to use numerous .NET namespaces by importing them easily to the project.
- UiPath provides the flexibility to create a custom activity from our custom .NET DLL.
Cognitive analysis is the most valuable feature because it helps to launch our automation smartly with many integrations.
Be it any mundane tasks like invoice processing, document management, document extraction, and migration, order processing, KYC filling, application integration, Citrix automaton, or any such rule-based tasks can be automated with RPA technology.
Among all RPA solution providers, UiPath is the best choice and market disrupter, from our hands-on experience with the top three RPA vendors while shortlisting UiPath as our RPA vendor. With its intuitive visual coding drag and drop and Microsoft SharePoint workflow foundation technology and open platform capability, code development and debugging are a cakewalk for anyone with minimal or even no coding background.
I use UiPath to automate processes that use different systems. This is the best use for the tool since it has integration with a lot of systems.
- We have a lot of processes to be automated. UiPath helped us to be cost effective and time effective.
- UiPath provides us with high speed in case of implementation.
- Implementation speed which helps how fast can you automate
- Reusability and extensibility which is used to build modular automation and reuse at the workflow level, plus it extends UiPath's functionality via custom activities or various integration.
My primary use case is to automate the process of RPO. Here we use data scraping, web recording, email automation, integration of multiple application, etc.
- Quick automation
- Easy reporting
- Agile customer support
- Easy integrations system.
- Desktop automation features and API services
- Email services
- Third-party vendor integrations, and
- The community.
Fast-tracking the interfacing between an in-house planning application and an international partner's planning application.
Using RPA to do check and balances on invoices, and consequently uploading this data to a tax engine and extracting VAT, European sales listing and Intrastat reports. Finally, these reports are uploaded to the dedicated web portals.
Extracting handover data of wagon from a data lake and entering it into the follow-up application, since there is no direct integration yet.
- Excel automation: It has activities related to most of the functionalities in Excel and makes life easier for anyone who spends a significant amount of time in Excel for analysis and reporting.
- PDF automation: It performs well in reading native PDF documents.
- Email automation: It integrates well with IMAP, SMTP, and POP3 apart from supporting Outlook and Exchange which are used extensively in large corporations.
- Web automation: The use of UiExplorer in extracting the properties of web elements and easy modification to improve the re-usability of workflows.
- Windows automation: It works well with Windows-based apps for updating information received in Excel spreadsheets and to capture the information and reports generated in the apps.
- Mobile app support to monitor bot health and status of the workflows.
- OCR integration works well with third-party engines.
UiPath speeds up the implementation of robots and allows integration with other external tools.
There are multiple use cases:
Automation of manual Excel workflow: Previously, our account support executive used to manually prepare client Excel sheet using a variety of third-party integration. Data flows manually into Excel and is then exported manually to a different system. What a fantastic work done by UiPath using integrations and webhooks. We almost saved 24 hours of weekly effort per employee and imagine we have to do this every time of the year and for hundreds of clients.
Automated data entry: Automated data entry of generated invoices was made so much easier with OCR recognition that we are trying to explore it in more departments like human resource and support systems.
We are currently implementing a solution for a large telephony company to migrate data between systems. This data is fetched from a system A and placed on a system B. Much of UiPath's functions are well used, such as integrations with PDF, OCR, Excel, and a few others. The financial return tends to be large since the robot manages to work 24/7 and with almost zero errors.
Integration with PDF reading OCR, Excel/CSV, SAP, Outlook/Gmail, as they are primary functions in the day-to-day operations of a company.
I found the recording, screen scraping, data scraping, and integration with third-party tools like ABBYY most valuable because they not only make the whole automation easier and less effort taking, but also, they let us use the power of external systems by integrations.
Availability of free training and certificates is another most valuable feature of the product.
The primary use case would be automating repetitive human tasks: read emails to get data, then login to the specific application and select other data based on the email received and reply to the initial email.
The secondary use case would be integration between legacy software.
- Integration with Outlook, which is the main mail server we use in the company.
- Integration with Google OCR and Microsoft OCR is very useful when we need to extract information from scanned PDFs.
- Data scrapping when we need to extract large amounts of information from websites.
- Integration with Excel, when we need to allocate this data in tables or CSV for future use, and many others.
- Citrix automation
- Computer vision
- Data scraping
- API integration.
Certainly, the integrations with Windows and Google OCR, PDF, Excel, Outlook and SAP are the most valuable within our area of performance.
The main request of our clients is the integration with the SAP system and specific tasks of email, like sending and downloading of NFS.
- UiPath supports integration with various OCR, cognitive, ML, and IoT related services and tools.
- UiPath provides the flexibility to use unattended robots without the need for Orchestrator.
- Data scraping and web automation
- Citrix automation
- Easy integration with all windows applications.
We combine this RPA solution with predictive analytics. We are in the hairdressing industry, so we predict the amount of haircuts that we get every month in advance. Based on that prediction, we set up our work shifts based on it. We do that predictably, then we use UiPath RPA to fill in the work schedules for each employee in advance and measure it, since it is really important for us to get an accurate number of shifts based on predictive analytics.
It is fairly easy to use. We are using it with a lot of integrations with separate tools to get the flow of data going.
With Excel applications, it is not able to handle a lot of pop ups. It should be able to do this automatically. We just change the format of the file from XLSX to XLS, but it should be able to handle this automatically. Instead, when something pops up, it gets stuck there. This type of thing are small, but still the process gets stuck. I would like to see better integration of applications to avoid these issues.
We are also making a lot of manual changes in SAP. We are looking for a solution where we don't have to make manual corrections every time, similar to what UiPath did with some SharePoint websites.
The seamless integration with programming underneath, so if you choose to, you can get a bit technical with stuff. If there is something missing, you can make it yourself.
The increasing amount of possibilities in Orchestrator to control robots and schedule them, with the possibly of a dynamic schedule in the future. In addition, there is API access to Orchestrator.
We would like more API integrations, especially more API connections to SAP. While this is on the roadmap already, activities and packages with more automated API connections to other software or platforms would really help us.
Documentation-wise, UiPath could get a little better.
Technical support has been very accommodating. In fact, they'll be on site to help us overcome some of the challenges we've had without having third-party integration support. We've been struggling on our own, but UiPath has been there and has even agreed to come onsite to help work through some of these issues.
As a partner, we have a lot of great people at UiPath who we can call and ask about things.
They've been helpful with understanding what the timeline is for new stuff, like integration and new activity sets.
From a partnership perspective, like in delivery, they've been really helpful.
The security needs improvement, especially in regards to managing the credentials.
I would also like to see better integration with Microsoft products.
We still have to test the final product. UiPath's recommendation is build another bot to validate the other bot's work. That is the scary part: If you make a mistake creating the bot, how can you recover from that mistake?
A lot of Elastic is not working, which is why the solution is not integrated.
While the commercial solution is successful, the government solution needs improvement. Government has so many regulation and requirements that still need to be address by the product.
The features that we use the most for our use case include reading PDFs, email integration, and web and desktop automation talking to other desktop software.
We have generally found it easy to use, but we also develop some extensions. We are actually a software development shop, so we have developed extensions to the core UiPath platform. They have made it pretty easy to do that.
I would like to see some integration, or ease of integration, with APIs, so we can automate stuff faster. E.g., we go through a co-op, which is a card processor, and they have a very powerful API.
Ease of use and speed of development are the most valuable features.
The overall integration with Microsoft stack and a few other third party vendors, like Google, are very useful to us. Having these built into the product speeds up our development, so we don't have to code a bunch of connectors on our own.
We use unattended robots and the Orchestrator module. I am most familiar with the Orchestrator. We are very new to this solution and just getting into it.
We are a financial insurance company and we do VoW, Verify on Web. We have a bunch of different insurance carriers.
We run automations in a virtual environment, VMware, and I haven't seen any problems with it.
With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate it a five. For my part of it, this solution seems very useful. I have limited exposure to it because I do more of the installation, the configs, etc. I don't really work with the workloads, although I see what is being worked with. We have our in-house developers who are doing the integration into our in-house programs, so I watch what they do and it just seems that it's very easy to pick up on.
I have not used the UiPath Academy, although I think that the developers have. I did not get any feedback from them about it.
I was not involved at the time, but I think that from the point that we purchased our UiPath license until we had our first robot was approximately three to four months.
I really liked a lot of the things I see coming in terms of the future improvements for Orchestrator. I think it's going to continue to grow into a true kind of Cloud Platform for end-to-end automation, whereas right now, it's a little more focused just on building things in Studio, and then managing monitoring them in Orchestrator. So, I'm excited about some of the further integration with the dashboards and everything for managing how it works.
Upcoming is better management of projects from end to end. I've built a lot of things myself to keep up with that. But having UiPath support, a lot of that, a little bit better, it's improved. This is including the focus on the process mining and the design phase, and it's often a bottleneck of not having enough time to go through and really thoroughly map out and document the processes.
I am interested in trying the specific Studio for test automation. I think UiPath has a big advantage in that space with their RPA software. It really solves an issue that a lot of other test automation platforms have, which is not being as consistent as they could be, or being too hard or too complicated to program correctly.
From a cost perspective, we have definitely got our money's worth on the unattended bots, which is what we have been focused on. We have bought a few attended bots to try them and this next year, we will be looking for good use cases. It requires a little more integration and using the API. We're looking at leveraging more attended bots, and we may end up buying more, but we're still evaluating how to use them. Unattended bots felt like the clearest advantage for us to implement, and we were successful in starting with those.
We were an early adopter of this solution in our region, so I often speak with people who are researching this solution. I tell them that UiPath is a really great platform and it's growing. It's moving in a really great direction, and I recommend people to take it in-house. Find a small team of people who are really passionate and interested in learning it, and then start small. Start with a few small things to get your feet under you, build an operating model that will support scaling, and then slowly scale it out over time. That's what we have done, and it has been successful for us.
Overall, I am very happy with UiPath, but I do have a few small quibbles. On the whole, it's been very successful and I'm very happy.
I would rate this solution a nine out of ten.
I would like a better ability to connect and integrate with other software systems. An example would be integration with data and business intelligence tools. I don't think they have a native connector yet. So, just something that a user can connect, and have RPA in the middle, would be helpful.
I would also like to see an easier UI for the user. It may have already been taken care of with Studio X, but I think if they keep improving that, it's going to get a lot of people interested because users are attracted to it.
In the next release, they need enterprise connect. That's something we were wondering about.
The solution could maybe use more artificial intelligence components or stuff we can start to use in the AI field.
It could use an easy integration with SAP. Most of the processes of our company are in SAP. Sometimes it's kind of tricky to automate it.
In the majority of cases, the initial setup of this solution is simple to medium in terms of complexity. We are finding very few complex scenarios at the moment.
I think the overall architecture is simple. It is very clear and very straightforward. UiPath's product team is doing a great job in is creating a lot of very out of the box integrations and analytics, and that always helps. That is good, but I think if people are not trained yet and they think that it's easy, drag-and-drop, and simplistic, those folks struggle a lot.
We've seen that people think "Oh yeah, it's just some scripts and drag and drop so we can do this easily" and that misconception exists. We don't treat it as an easy scenario, so we gave it all the respect that proper Python code, a data science problem, or a highly complex situation deserves. When you approach it that way, it's at best at a medium complexity.
In general, we treat it right in the middle. It's not that straightforward, but the architecture is simple enough that the development complexity is medium. That's the simple and medium combination.
They should expand on workflow type items and take another step up from the long-running workflows to offer more visibility of business processes within Orchestrator.
The solution needs a better integration team, different versions of Orchestrator, and to make it easier to identify problems with versions, as well as to be able to fix those kinds of problems. It's hard if you don't keep up to date all the time as well, for example, to go from 2018 to 2019 versions. It's quite a big jump considering activities and things like that.
Orchestrator needs to have better integration to include business users.
Part of our deployment is in a virtual environment and part of it is not. The implementation is actually still in progress. We are in the phase of setting up our infrastructure and trying to automate some POCs (Proof of Concepts) and some early successes to show the financial benefits of RPA to the C-suite (C-level executives such as the CEO and CFO).
On a scale from one to five where one is very difficult and five is very easy, I would rate the ease of use of the platform as a four. I think the product is fairly intuitive. Because I come from a tech background though, I feel like it is going to be a little easier for me to understand than some other people who don't have that same background. The only reason I don't give it a five is because the integration between Orchestrator, Robots, and Studio does require a little bit of intimate knowledge to be able to connect them all and make sure that they stay connected.
We have not used attended robots yet, so I'm not sure how cost-effective they are because we don't have any data on that. We use unattended bots and they seem to be effective solutions, but I don't know what they pay for them.
On a scale from one to ten where one is the worst and ten is the best, I would rate this product as a nine. The only reason I'm not going to give it a ten is that I have struggled with certain errors and stability issues. Whether that is our fault or a general bug in the actual software is yet to be seen. I have a few open tickets, but I've really liked this software overall.
Advice that I would give to a colleague at another company researching this or similar solutions would be that they look at their organization and see if they are really ready for deploying RPA solutions. A lot of RPA solutions are sold with the promise that anyone can build solutions with the products and the bots are going to deploy quickly. I don't think quick deployment is deceiving, but I do think that trying to implement a solution that does move so quickly like this into an organization that doesn't move quickly can create friction.
I'd rate the ease of use of automating our processes at three and a half out of five at this point in time. That is because we've been on a journey over the past year or so and it's not been smooth sailing. There have been issues. I'm not saying that UiPath's support hasn't been great. It has been, but there is still a lot of work to do. It's still a relatively new product in terms of the grander scene of the industry. There's still a lot of work to do there to make sure that the integrations with existing software providers as well as new ones and API connectivities are as they should be. Often, you'll find yourselves using the workarounds in order to address issues that they haven't quite solved yet. I know that's constantly being improved, but that is the journey that we've been on.
One of the issues is with the acquisition of new types of software and new companies. It's important to introduce process documentation and make sure that it's not just making it look like UiPath products, but making it feel and act like one to us. They need to make sure it's embedded and the integration is seamless. They should just keep improving how easy it is to use. I think it's very good already, but there's always room for improvement.
We had merging companies coming together with a lot of integration going on. With integration, there are multiple teams, processes, and systems. To keep up for our reduced expenses, we had to do it. This was another tool in the toolbox for us: automation.
We have a project that combines UiPath with OCR and our integration tool. This allows us to automate processes we use in different projects that are coming from different vendors in different countries. Apart from gathering the information, we are template invoicing. The robots take invoice information and post the results into our SAP and other systems. It is much faster than our original process. This has been implemented in Spain, and we are now releasing it to other countries, one by one.
Using this solution is not just about saving time or reducing the number of staff. It is also for improving stability and decreasing the number of errors that we have. In Spain, where we were implementing a pilot project for purchase orders, we saw a decrease in the number of human errors. When they started, there was an error rate of ten percent. After three months in production, the error rate decreased to five or six percent, and after six months it was one or two percent. Also, even though there was still an error rate, it was consistent and it is something that we can account for.
In terms of money savings, we are talking about hundreds of thousands of dollars annually.
On a scale of one to five (where five is beneficial), I would rate the UiPath Academy as a four. There is some stuff that they could do better. I sampled the advanced, which is really difficult because it's just PDF. I had to use some YouTube videos to understand the framework that you need to pass for developer. They could do more videos on that.
They have three parts. The first is the foundation, and they are a lot of videos. The third part of it (advanced), there are no videos except one. That's only those PDF files, which you have to look and read through. I was like, "Okay, I probably can't do it." Then, I fell upon some community YouTube videos from other developers who just demonstrated it. This would be great if UiPath offered that, because I found out later that the developers made mistakes in their videos.
In the foundation, they get into much detail in the beginning. You're overloaded with information. You have to go through videos like three times to get it correctly. They could remove some stuff out of there. Those quizzes are really frustrating too. They are too detailed. If you sat with Uipath, you think it's really easy. However, it's not so much, if you get into those details.
Studio is a bit overwhelming in the beginning. They could get add some details, but not so many, into the foundation training. I've seen StudioX and loved the colors. Please get the colors into Studio. I loved the flow and that you got all these activities and colors too. It was so much easier. It was visually easier to understand where to click. It was really user-friendly.
I would rate the ease of use of the platform for automating our company’s processes as a four out of five (with five being very easy). I would rate it as a four because it didn't work in the beginning to get my bots active. I had to get into a lot of videos to get them running. I didn't understand how it needed to be designed or coded.
The Orchestrator training was much better, but I still somehow missed some details which I needed. However, it's not just do it, then it's done. You need some time to get into it. Though, it's much easier than Studio.
The integration with Outlook is not that good yet.
We do deal somewhat with Citrix. It depends on the client and how the bot has to be set up. We have some clients who do run through Citrix, then we have some who use a VPN tunnel to get in. So, we have it on both.
The implementations or integrations through Citrix are really good. The only problem that we are coming across is just maintenance. If the Citrix platform gets updated and we're not notified, it breaks. So, we have to reconfigure our bot to the new updates. Unfortunately, that's just the name of the game, and that would be true if we were pulling them manually versus a bot. We would still run into that with the Citrix platforms.
We don't like the attended bot experience, where it requires the user to be hands-off. We installed it on the user's machine, and the user should not touch the mouse or keyboard because the moment they do, it crashes. It takes over the machine and cannot work in the background. For this reason, it is difficult to work out scenarios that are purely attended.
For example, we have a process that downloads two files and then does some massaging of the data. Now, the data needs to be looked at by the user. An email is sent and the files are deposited into a common folder, and the user will address the task when they have time. After the user manipulates some of the data or makes decisions, it can proceed to the next step.
They drop the modified files into the common folder, but the bot doesn't react because there is no feature in Orchestrator to trigger based on the arrival of a new file. Instead, we have to put in a call to check periodically, whether it be five minutes, fifteen minutes or some other interval. This is something that we don't find desirable.
Creating a trigger that is based on either the arrival of a file or the arrival of an email is a common scenario and it should be built into the platform so that I don't have to code for it every time. As it is now, there are only two ways to trigger a bot.
Orchestrator does not have a good filtering mechanism to look for jobs, and the table view needs to be improved.
From the UiPath side, one thing that irritates me is that you cannot find the downloads to upgrade to the new version. I'm a paid customer and I log in with my credentials, but I cannot download it. I need to create a ticket, tell them who I am, and I have to give them a long list of things that I don't remember. They will address the ticket maybe today or tomorrow, and then finally I get a response. When I use other tools like Microsoft and SAP, as a customer or subscriber of the tool, I just download the latest versions and install them on my servers. When I have a mandate to do work, I want to be able to do it. However, when I can't download the file and have to wait for a ticket to be answered, this wastes my time.
The integration with Elasticsearch and Kibana is a struggle. They are not UiPath products, but they are recommended by UiPath. Some documentation is provided, but it is an Orchestrator installer package the just installs itself. I had to do a lot of experimentation on Windows machines because the configuration is different for Linux machines, and this gave me some trouble. There is a lot of information about this in the UiPath forums and I spent a lot of time on it.
Right now, I have a set of configuration data that I put into an Excel file. The users can change the file and my app will run using the configuration variables. A problem occurs if the Excel file is not closed properly because there are locking issues. This is a pain because the bot crashes when opening a locked file. There is something in Orchestrator called Assets, but it is kind of limited. It only accepts text and a credential. It would be nice if it had a simple database table, say to be able to create a couple of columns that I want to set up for a bot-related task. Rather than a single piece of text, there is a whole table of information. My users will be able to edit it, based on the permission that I assign. Then the bot will look at it and work according to what is specified. This would be a great feature to have.
I would like to see the Studio web-based so that we don't have to install it on everybody's desktop.
The most valuable features provide solutions for when I am using OCR (Optical Character Recognition) technology. It easily integrates with Google OCR, Microsoft OCR, and ABBYY OCR. We are using that integration feature to incorporate OCR mostly for reading scans. To interact with Google OCR, Microsoft OCR, or ABBYY OCR, you don't need to implement a separate component but you can just — in a blink of an eye — integrate those peripheral solutions into the UiPath Studio and use them in your automated processes.
If we can integrate other features that are not part of UiPath, it makes it far more useful in automation. In this case, UiPath is not building out an actual OCR component but they are just giving you an option to incorporate the other OCRs. That is very valuable.
The emailing and integration with self-service BI systems are areas that need improvement.
We have IT solutions that are oriented to service our call center because we are a contact center company. For example, we have a CTI (Computer Telephony Integration) solution to help manage our phone calls. It is something that we developed in house. We are developing a UiPath (the company that acquired ProcessGold) solution using RPA robots to improve our processes. So, that is our main use for the ProcessGold solution.
We use the UiPath product in order to reuse processes that we manage better and use the time of our agents more efficiently. When we established a connection with a client by phone, our agents spend a long time talking with the client and are also responsible for doing some back-end tasks. In order to reduce back-end tasks, we use RPA robots to reduce the time you need to spend on follow-up calls. For example, after a second call with the same client, you may need to fill in a form or a CRM entry. If we can simplify this task of filling out a form where we insert all the information automatically the robot saves that time. That is the main idea and the reason we use these robots.
The user interface can be improved and the version control can be better. Document linking can also be improved, and also the searching could be more user-friendly.
Better integration with AI would also be an improvement.
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.
Data Scraping is definitely a unique and useful feature that we had not known about before.
Smooth integration of OCR, which is very quick, is a useful feature.
Manage packages to get more packages.
Save as a Template feature.
Snippets are really useful as a reference for logic.
Plus button between activities & Ctrl+Shift+T is very useful in adding activities quickly.
The features like Data Scraping, Excel Automation, Mail Automation, System Automation, Secure credential activities, User events, and App integration are valuable to us. The integration like ABBYY OCR and Tesseract OCR are helpful. ABBYY OCR is a very good activity that can identify handwritten text, but to use this requires a licensed version.
UiPath requires less code writing and is user-friendly compared to some other solutions. The standard things can be automated very easily. The drag-and-drop activities make life easier.
The most beautiful activity is sentiment analysis, where we can predict the good reviews and the negative reviews. This gives us a great advantage.
Integration with different tools makes easier by using APIs.
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.
What I have found interesting is that our product acts as a human would but it's not intrusive. It doesn't require any real integration or interface with one's own systems, in any meaningful way. Obviously, you need access, an account to log in, but it otherwise acts as a human, and that makes deployment quite smooth. It doesn't require you to change anything in your system. I found that very useful.
Regarding the ease of building automations, I'm not sure how it's done because I'm not a programmer myself, but it's great. Just looking at how fast they moved once we had the program settled in — it was quite fast. For this particular process, which is assembling a document, talking to DocuSign, sending out emails, and so on, the deployment of production was like "today." It was quite quick.
In terms of the ease of management of automations using UiPath, I don't dare poke into it, as a non-technical person, but it looks manageable. I have someone who does not do RPA normally, who doesn't do this type of programming at all, but that person knows where to look for errors and doesn't get lost. It's reasonably accessible.
The most valuable features are the recorder because it's user-friendly and the integration with other tools Excel.
WorkFusion's SAP integrations are really good.
Our primary use case is for desktop automation for smaller solutions that stand outside the development on the core operating systems.
We also use it for building robotics capabilities and skills in all of our geographies across fourteen countries in Africa.
Automations have been done over several operating environments and include solutions in the following areas.
2. Compliance and Risk (Regulation driven requirements)
3. Credit solutions and integration with decision systems
The primary focus is delivering solutions that enable better customer experience.
Kryon RPA: Integration
I think our version is two versions behind. I just had a talk about it last week with our account manager at Kryon and we planned together to upgrade the environment once per year. In my opinion, today, if possible, it would be better to have it done automatically, like an application on your smartphone. Or even if done manually, the upgrade should just be "next, next, next," and it's upgraded, rather than making it a project to upgrade. In the digital era, that is one of the expectations, that it would be easier.
Besides that, it's all about functionality: What you can do and what you cannot do. I'm not very familiar with the competitors' solutions, so I'm living in the world or Kryon functionality. Sometimes I'm looking to automate something and it's not there. That doesn't mean that it's not possible.
We use Kryon Studio to develop new wizards and we use the features to capture elements from the screen and automate processes. We use the product thoroughly. The screen capture allows us to interface with systems which don't have an API, or where the API is very expensive, and it allows us to do on-screen integration.
The automation process is very user-friendly and the usability is very good. Developers are very satisfied with the system.
There is a vast field of RPA tools. You have to know what you want to do and how to add value to your business. You need to see if what Kryon gives you is the best fit for you. For us, as beginners in the field, it was good, because of the support and the willingness to help us and to be cooperative. That was very helpful at the beginning. So you have to evaluate which step of the RPA lifecycle you are in. I can tell you more, in a year or two, if I'm satisfied when I am more advanced. But for starters, it is a good decision.
In terms of using the solution for the full cycle of automation, from the discovery of processes to turning on the automation, and scaling it up, it's a little bit early to say, because we don't have a lot of experience. And I can't compare it to any other thing that we have, because we're really at the start of it. But so far, it has met our expectations. I didn't think it would go as fast as they described it, and it didn't, but it was fairly rapid, and it has its ROI. All in all, good.
It's not for end-users, absolutely. It's not that. For developers, it is interesting. We didn't actually use developers to work with it. We had more, what I would call an "implementation guide." It takes knowledge and it takes time. There are a lot of technical issues, not only because of Kryon but because of our system and the integration between Kryon and our system. It's definitely not for end-users, regardless of what anybody says. It's not. But it's fairly decent for developers.
We have our four developers who actually touch Kryon. We have two-and-a-half to three people who are dedicated to deploying and maintaining it, and another one comes and goes. We definitely have plans to increase usage. At the moment we do about 1,000 transactions each day, but we want to get do more.
As for helping our organization embrace digital transformation, we're heading that way. It's only the start, but we have a good vibe here. I could answer that question more comfortably in a year. But I see the way. I see the light.
We had an outside advisor, not Kryon itself, to help prioritize processes that are ripe for automation. We preferred it that way. Maybe Kryon could have given us that service, but we preferred to take an outside advisor.
I would rate Kryon at eight out of ten. It's not as rapid as they describe it and it has its limits. We have met with Kryon a couple of times. The guys were very helpful and said, "We'll bring that into the roadmap," etc. But we hit the limit of the product. For starters, we expected that to happen in year-two or year-three, not three months after trying it. But all in all, it has been a good experience.
With respect to web-based applications that we have, Kryon may not be able to do certain things in terms of technology and support.
Also, there are limitations on integrations with other platforms like ServiceNow. There are some issues integrating. It's not a really an open system. The product, its design, etc., is really good, but they have to look at the openness, how to integrate with other products which are available in the market, as well as with our own solutions. You can do integration but it is not so easy. You have to build certain things to integrate. It's not like an open API is available. It's there but it's not really open compared to competitors.
We use Google Drive a lot. If somebody sends us a spreadsheet or a document, it's going to be in Google’s format. It's not going to be in Microsoft Office format. But currently, there's no integration with Google’s documents. That would be a huge plus to have.
The same goes for, using Chrome natively. There's an extension but it doesn't necessarily always work. We have to close Chrome and reopen it to get it to pick things up sometimes, depending on the page and the IFrames and things like that.
Our original plan was to do something like two robots, and a few processes, but because it was such a success in the company, we expanded it. We have 11 processes. The eleventh is due to go live in about a week. Some of them are not complex, some of them are more complex. It depends on the process itself, the amount of time, the amount of integration, if there are dependencies on another system.
In terms of plans to increase usage, for now we really want to see how the day-to-day is going with all the processes. More processes mean more licenses and robots, and we have to do ROI as the next step. I would guess we'll do more, but it's already a lot to have 11 processes in a year with four robots.
We have relied heavily on the the data group base integration features, as well as the email and Exchange integration features. The ability to integrate with Office makes life a lot easier. One of the things that we do is interact with a lot of Excel worksheets and their information without having to load up the Excel worksheets themselves. Instead, we are able to pull the data directly from them and do the manipulations that we need, then put them back into the spreadsheet or into another worksheet without having to wait for Excel to load.
The ability to integrate with a database is a big perk from a scalability standpoint. Our automated processes for our rate programs are driven by database entry. We also use databases for our queuing systems and reporting purposes. It is proving to be the backbone of our analytics side of tracking and monitoring our automated processes and systems.
We have been using Kryon Process Discovery for about a year now. With our initial tests and monitoring just a couple people, we were able to identify 79 possible use cases within a one-month period.
For developers, Kryon is quite easy to use. I come from a scripting background. Adapting from scripting over to working in Kryon's development environment is very simple. It was an easy adjustment.
It is easy to move things through testing and into production. From a development standpoint, it is a pretty streamlined, straightforward process.
From a solution standpoint, screen capture and tight integration with Outlook are valuable features. We tried the same TOC with Blue Prism but it was more complicated.
They recently released the newest version that has a good program flow, quality, and blueprints that are all good improvements to the automation. They also have good integration with SAP.
It's also easy to run scripts from the EBS.
The image processing capabilities definitely need to be improved.
We have had trouble automating processes running on Windows Server 2016. It seems to be related to integration with the Office tools, but I cannot 100% confirm this.
Technical support can be improved.
Blue Prism Cloud: Integration
The product could be improved by including advance features like OCR - optical character recognition - which are currently not native to the product. We are looking at integrating Blue Prism with other products. They've told us that Blue Prism Decipher is coming with intelligent document processing solution, but I haven't seen it.
It would be good to see OCR integration and OCR capabilities included in the solution and, of course, going forward, artificial intelligence and machine learning capabilities.
I would like to see a web-based control room, rather than the one that is in-built with the desktop version.
Integration with different databases would be an improvement because there are certain things that are not compatible with Blue Prism.
The is much improvement needed in the hyper-automation components, such as insights.
We would like to have more reusable components from different vendors, as it would make things easier for us. For example, drag-and-drop downloads that can be used within our automations.
HelpSystems AutoMate: Integration
While this solution is continually improving, as it is now, the user interface could use improvement when I compare it to a product like UiPath. Specifically, the Automate Enterprise interface needs improvement.
When you are promoting packages within the environment, it is easy to extract an import, but it would be better to have it all in the same console. As it is now, you have to extract the package separately. The environments should be able to communicate; you push the button, click on deploy, and it goes straight to the production environment.
Increasing the integration with other databases would be an improvement.
Adaptive Growth is a reseller for HelpSystems' AutoMate Robotic Process Automation software system. Our primary target markets are manufacturing and distribution companies. We also feel that nursing homes and trucking companies are markets that RPA will provide tremendous benefits in operational cost reductions. HelpSystem's PDF and email integration into business software workflows is a great benefit for most any company.
Microsoft Power Automate: Integration
The most valuable features are the Flow and the UI Flow. Flow is used for workflow automation, and UI Flow is used as an RPA solution.
This product is very easy to use.
RPA has introduced a lot of new features include computer automation, AI, and third-party certified application integration.
Our primary use for this product is for the automation of manual tasks that may require some small integrations between systems. An example would be something like automatically sending an email from an action that is performed on our online system. Another might be writing data to our CRM database based on the input from an online form.
Before really adopting Power Automate, I did have some experience with UiPath.
The main difference between Microsoft Power Automate and UiPath is that I think UiPath just has a wider variety of opportunities for integration. By that I mean there are more products it can work well with. So even non-Microsoft-based products work well with it, like integration with Citrix platforms. This can function without a lot of extra work. I think that is really one of the main advantages.
In the future, I would like to see more focus on AI and third-party integration.
Compared to other RPA solutions, there is a little bit of a feature gap.
The licensing model is difficult to understand and is something that should be improved.
When you are implementing a project, it's quite difficult to comment on what it is that you are doing. For a simple project it is fast, but to have a better overview then it gets complicated.
I would like to see more integration with other products.
There is definitely a lot of enhancement that Microsoft can incorporate into Power Automate. For example, we have quite a lot of .NET applications that we created. These are custom applications that we created using something like VB.NET or C#.NET. These are obviously applications that are not published by Microsoft. I would like it if Microsoft could enhance the capabilities of Power Automate to allow users to connect to other tools and applications in some way. That will help us create better processes without making them more complicated or having to use another automation tool. Right now, we have to use UiPath to help us make processes such as the one described. I have not seen any way that Power Automate can do that type of integration. So if we could get better integration with non-Microsoft solutions as a feature for Power Automate, that will be very useful.
The solution lacks certain items.
I'm not really qualified for judging the solution. A developer could give better pros and cons.
We would not miss Microsoft Power Automation that much. As still has a long way to cover tasks when it comes to the ease of use like UiPath, which is pretty user-centric.
The solution needs to improve its integration with SAP and Oracle models.
The solution's automation is still evolving and still has a way to go.
The solution could benefit from mirroring Oracle's use of videos and community forums to help users get acquainted with the product. It could use better online training and/or documentation.
It is a great solution for simple automation activities or simple automation of simple tasks.
It is also integrated with Office 365. Integration is an absolute breeze with any RPA software.
Its integration with SharePoint and Outlook is the most valuable.
I found it very easy to use. I could do everything that I wanted very quickly, and I didn't have any complications at all. I never had a problem in using Microsoft Power Automate.