The product should improve desktop automation, which is hard to configure. It needs to have custom connectors. It is the only advantage that Microsoft Power Platform has over Kofax RPA. It has more than 800 custom connectors. 

Compared to other Microsoft products, like Power Automate, Kofax does not have most of the native integration with other solutions. It is based on API integration. The product has some constraints and performance issues.

We've faced a few challenges with Tungsten RPA. One issue I recall was with sending emails that needed multiple attachments. At the time, the feature only allowed attaching one file at a time. We discussed this with Tungsten RPA, and they planned to add multi-attachment capability to their backlog. I'm not sure if it's been upgraded since then. The solution's desktop automation is tricker. 

Everything is working based on the server model. Kofax does not cover desktop automation, whereas other products have covered it. The solution should have predefined connectors. We have a mainframe, database connector, and external applications, like site-core integration. Also, CMS portal integration should help come to the latest trend.

Tungsten RPA features enhanced desktop automation capabilities, improved Active Directory integration, and upgraded recorder functionality. These updates will be available in the upcoming release.
Firstly, The first level of support needs enhancement. When you open a ticket with Tungsten, they inquire about various aspects of the issue. The initial support level should involve conducting a Webex meeting to address and assess the reported issues within the environment directly. This would involve thoroughly checking the issues and logs, among other relevant factors. It may require a minor configuration adjustment that could be resolved promptly during the session.

There are several challenges associated with Tungsten RPA. Firstly, there is often a perception issue among employees who may believe that RPA is intended to replace their jobs rather than enhance efficiency. This misconception can hinder the adoption of RPA solutions in the workplace, as employees may resist the implementation of automation technologies.

Secondly, there have been challenges related to integrating Tungsten RPA with applications built on Java. Many issues have been addressed and resolved in  V11.3, thus improving the compatibility of Tungsten RPA with Java-based applications and major challenges.

Automation of complex processes involving stable legacy systems could be a major plus. The biggest issue lies in the stability of the target environment. Automating systems based on Citrix, where using AI or OCR-based capture of a screen, presents challenges. 

The Citrix environment's instability can hinder automation. Users can adapt by pressing buttons multiple times, however, robots may require complicated logic, leading to an exceptionally complex implementation with more error handling than originally budgeted.

Kofax is unable to handle tasks such as processing documented leave requests from their company or assisting employees in finding new employment opportunities. Also, the cost of spare parts could be lower.

RPA technology is constantly changing, and sometimes Kofax lags behind. 

Kofax RPA's UI could be more user-friendly. In the future, I'd like to see more frequent updates and better integration with Citrix.

Kofax RPA could improve web-based automation and there should be a choice of what browser we can use, such as Google Chrome, instead of an inbuilt browser from Kofax RPA. Additionally, Kofax RPA is missing an orchestrator that other solutions have, such as UiPath.

The technical support must be improved.

Automation with the latest websites is not effective. The support of newer websites developed using new technologies would improve this solution. The Java and Windows application automation could also be simplified.

We are in the field of AI, and one of the features that should be added to this product, such as robots, is the integration of AI so that more information can be incorporated into local activities.

The scalability has room for improvement.

The interface could be better from a usability standpoint. In the next release, I'd like to see more integrations and connectors.

We are on version 10.6, and the current version seems to be 11. Kofax is cycling the capabilities of the product very quickly. One of the difficulties has been to actually keep up with the capabilities as they've evolved. On the one hand, it is good that the product is getting better, but on the other hand, it is difficult to implement the best way with a product that is evolving constantly.

The product could be improved if they would use AI integrated robots. Some AI integrated features would be nice. 

The HR and IT areas of the product need to be improved. Right now, they are lacking. They need to be modernized. More logistics should be involved.

The process discovery could be a bit better.

The product needs to develop a web version of the solution.

I would like to see them further enhance the OCR, specifically in the multi-language support. We had a document in Japanese where there was a bit of a struggle. If that could be corrected in the new release that would be good.

I think they need to do a better job of following the lead of its competitors and build upon that. I would like to see more AI capabilities, and I think that is one of the keys. Exception handling should be improved as well to reduce errors and things like that.  

Its documentation is not widely available on the web. For Automation Anywhere, a lot of documentation and YouTube videos are widely available, whereas the documentation for Kofax is not that widely available. When there is a problem, the channels through which I can get a solution are limited. Its forums are also limited as compared to Automation Anywhere, and we have to figure things out ourselves, which takes a lot of time. They should work on the availability of its documentation.

In Automation Anywhere, there is a feature called Discovery Bot that automatically records the process steps and suggests a possible bot. I am not sure if such a feature is available in Kofax. If it is not available, it will be very good to have this feature. It will definitely help in involving non-technical people who are dealing with the process. They can go ahead and run this discovery bot and then provide that input to the technical team. The technical team can use this input to improve an already-defined high-level bot.

Kofax needs to create a community where developers have the opportunity to donate to it.

The education surrounding this solution should be better. It needs a free training portal for anybody on the internet to use so that they can get an idea of what the possibilities are.

I've noticed that no solution, including this one, is trying to automate very simple processes. There are always exceptions and special cases involved in regards to how you can handle these instances. It requires a kind of deep understanding of how to utilize these features and it's not very straightforward as of right now. The documentation could be stronger.

The solution should add orchestration into its next release. 

The solution needs to be scalable.

Of course, there is always room for improvement and I know there are developments all the time. This includes, ultimately, the development and increased use of robots. It's something that our customers want and I know that Kofax is working on that. I don't know if similar products already have this kind of function but this is one we've been waiting for and I know that it's not a simple ask. 

For additional features, I'd like to see a recording function and a more simple interface. I also think that there could be more support for emerging learning or artificial intelligence. 

This product has room for improvement in support of airplanes and aviation. Maybe the interface could be improved in the next release. 

It would be very handy if you can connect directly to the ERM or ERP system.

Concatenation of error messages.

Kofax RPA needs to improve integration with SAP and Microsoft. The professional services offered by the tool's team is below par. Its licensing needs to be more modular.