Kryon RPA Pros and Cons
Kryon RPA Pros
The bot is typically about twice as fast as a person and more accurate, as long as the data going in is good. That is the biggest advantage.View full review »
Attended automation has diverted 34 percent of training calls to our tech support centers.
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.View full review »
As a business user, it's so easy to use. With the recording of the processes, we didn't need to hire a specific developer... we are able to build most of our processes without having to develop the actual development skillset... the simplicity is the biggest win.View full review »
The recording capability is valuable because of the amount of data it captures automatically. It's quite good. It means less development, and fewer configuration settings to fill in after you're done.
Troubleshooting and debugging could be improved. It's missing a proper debugger. It's very difficult, based on the log files and the fact that it doesn't have a proper debugger, to troubleshoot issues. It will sometimes end with no indication as to why it ended and it becomes a bit of trial and error.View full review »
It has been helpful in reducing the manpower and error rate since we are able to run tasks 24/7 without interruptions. As humans definitely take breaks and there may be absenteeism that is unexpected, the solution provides continuous work. Humans tend to make errors once in a while, but the solution has almost zero percent errors.
We are able to cope with our clients's demands. No matter how much volume they throw at us, we are able to get it done quickly.View full review »
We use PowerBuilder as our application building codex. Kryon adds flexibility when we have the functionality of SQL, where we can take sets of data out of the back-end and run complex computations or do a bunch of data validations inside the wizard. It can save us sometimes dozens of steps, then if we were to try and do those same reviews using the user interface completely. The balance that we get from using Kryon RPA, alongside being able to screen scrape and frequent screen, gives us an advantage that we haven't had previously with any of our other attempts at robotic process automation.View full review »
Once I decide a process is suitable as a Kryon solution, the cycle of automation is quite quick. I learn about the manual process and I'm one of the two guys who program the Kryon environment. It's relatively simple. There are many details, but once you understand the concept it is quite easy.View full review »
We took a very complex business area, and every activity in it which can be done automatically is being replaced by the robot instead of people working on it.View full review »
The number of commands it gives us to edit and modify is really good. It also captures screen activities and plays them back.View full review »
[One of the valuable features] is the triggers. It's relatively simple to activate it. You can activate it via Control-M or via email. It has a lot of built-in triggers which enable us to easily activate the jobs.View full review »
Kryon RPA Cons
The only unstable part is Studio where you build this stuff. In our version, the 5.25. It has a memory leak. If you leave it open for too long, eventually it just freezes. Saving your work, closing, and opening it just once a day is all it takes. However, this is a bug that I have noticed about the stability of the actual tool.View full review »
I have seen some very minor occurrences where Kryon's interactions with Microsoft Office might cause the robot to hang. However, it is about one to two percent of the time where we are seeing this happen. It is such a small percentage that it's not even something that we are overly worried about. This would be where they might have some stability issues, but it could be the Microsoft Office API or how they are interacting together.
With the customer support, there have been some times where we have had to go through explaining the issue a couple times because it has gone through a couple of people's hands. There have been a couple of scenarios where we have had to re-explain the issue and bring somebody new up to speed on what is going on or what the problem is.View full review »
At first, we had problems with the object detection but in this latest release it has been better, and I think it keeps getting better.View full review »
Another major drawback is OCR. We are not able to read scanned documents correctly in a reliable way. There is always some margin of error. Some of the processes require us to read scanned documents, and you need to ensure that it is 100 percent accurate. Without that level of assurance, you can't automate such tasks.View full review »
We would like to see having a little more specific documentation, or some of the examples be easier to find. One of the big things that we get directed to now is the Kryon Community page, but a lot of that wasn't in existence or publicized when we started doing our training and education. Now, we're stumbling through using it. For the majority of the time, we have either had to try and interpret what the instructions meant or do a service desk ticket.View full review »
It would be better to have [upgrades] 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.View full review »
What we are lacking is OCR, the ability to read text. We would like it to have the ability to take a page which is free text and analyze it, and then for the robot to know what to do next. This ability does not exist in Kryon products.View full review »
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.View full review »
We need stronger governance to know, when a transaction is done, whether it worked or failed; strong logging. That would be helpful.View full review »
The product requires some more time in development. It still has some bugs and some things to work out. They're constantly releasing. They need to continue working out the general issues of using the product at scale, first and foremost.View full review »