Unit Head, Enterprise Application at a financial services firm with 1,001-5,000 employees
Real User
Top 10
2024-11-11T15:55:00Z
Nov 11, 2024
OpenText needs improvements in its integration model to align with newer integration types. The BPMN 2.0 model does not function as designed, and there are challenges with application performance and the BERT files. Overall, the product needs significant improvements.
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.
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.
Senior Information Systems Specialist, BRM Unit Lead at a government with 1,001-5,000 employees
Real User
2021-03-17T12:59:20Z
Mar 17, 2021
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.
OpenText Appworks. AppWorks is OpenText's Enterprise Application Development and Management platform. It allows you to quickly and easily build purpose-specific apps for the enterprise using the web technologies such as HTML5, CSS3 and JavaScript. These apps can connect to the OpenText EIM Suite using RESTful API.
OpenText needs improvements in its integration model to align with newer integration types. The BPMN 2.0 model does not function as designed, and there are challenges with application performance and the BERT files. Overall, the product needs significant improvements.
OpenText AppWork's low-code capabilities can be enhanced by integrating them with AI offerings like Aviator.
There is room for improvement in the pricing structure.
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.
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 integration could improve.
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.