OpenText AppWork's low-code capabilities can be enhanced by integrating them with AI offerings like Aviator.

The crucial missing element is the archival function. When you have numerous processes in your system, generating instances on a daily basis, your database naturally grows larger over time, and without proper archival capabilities, there is a risk of losing valuable data.

There is room for improvement in the pricing structure.

A room for improvement in OpenText AppWorks is its user interface. It should have mobile compatibility because right now, you still have to make two applications with a user interface for Android and a user interface for iOS, so if OpenText AppWorks can provide one UI that can be used across all devices, that would make the solution better.

An additional feature I'd like to see in the next release of OpenText AppWorks is a better UI in terms of the look and feel. Another feature I'd like to see in the next version of the solution is mobile compatibility because, at the moment, you have to make your application mobile-ready or compatible with mobile devices because there's no provision for it in OpenText AppWorks.

AppWorks could be improved by including BPM simulation.

Integration could be improved. There could be some improvements with the low code design part. It could be more customizable and more user friendly.

The solution needs to continue to enhance the low-coding feature within the product itself. It could be better. They could continue to expand on its capabilities. It would improve the product in the long run.

The integration could improve.