The cost of the product could be improved. Currently, there are certain snags in document viewing, and communication from the pre-sales team is not clear. The expectation from the customer versus the product explanation needs alignment. OpenText's knowledge website needs better organization.

There are some workflows which need to be more user-friendly. We need to improve here on the specific map of the developers. Also, the support from OpenText is really difficult. Honestly, I had a very bad experience on this. It's really difficult to reach out to OpenText. Even for small things, OpenText is not transparent. As a professional, I don't think that's the right way. This is also one of the disadvantages; many customers are moving out of OpenText. 

I saw multiple instances when I was working with new RFPs or new opportunities. So many customers are raising the same concern, and they are looking for alternate products. That's been the case many times at the project level.

With OpenText, we ourselves often have to resolve the issue before OpenText people provide a solution.

The performance, stability, and consistency could be improved. The solution works well when the load is low. We have around 6,000 to 7,000 users using the system, and we see some performance issues during peak times.

More out-of-the-box automation features should be added to OpenText Extended ECM. The workflow engine's integration capabilities can be enhanced in the solution. Limited automation capabilities are already present in the tool, and custom development efforts are required before full utilization. 

We make iterations on it. Every year, they usually ask for some small things. Overall, they are pretty happy with it. Being the IT person here, I do think there are areas for improvement, but both for us and them, it is 80% to 90% good enough. It might take a big overhaul to get to that next step of being able to do even more. They are fairly happy with it right now, so I do not see that coming immediately down the pipeline. It is like the juice or the squeeze on some of those things, but there is definitely some room for improvement. We have learned more since we implemented this, so there are things we could do for sure. Overall, they seem to be pretty happy with the process.

When it comes to addressing complex use cases, three or four years ago, we ended up purchasing an additional OpenText product called AppWorks because we started to run into some limitations with the workflow that can be done in Extended ECM. It was a little limiting, so we ended up getting another product. They integrate together, but in some of the more complex scenarios, we have started to shift and start building things in AppWorks. Documents are still stored in the Content Server. It is almost like an additional layer that helps us do a little bit more. So, Extended ECM Content Server does a very good job for a lot of use cases, but if you do need to do something that is a little bit more complex, you might need other tools.

There is room for improvement in records management. ECM should be a single place to keep all the documents so people can easily search and access them.

OpenText Extended ECM's user interface could be improved.

The use of SmartUI must be improved. It's been out for years now, since 2016. OpenText has released more enhancements in SmartUI, but I think it's taking too long. We need to get to a point where we are completely dependent on SmartUI and get rid of the classic UI options.

The annotation tool needs improvement. In other tools, such as Hyland OnBase, you can easily do annotation. You can easily merge documents. You can easily compare documents, whereas with OpenText, it seems to be a challenge. You need an additional tool to do that. I am not quite sure why that has to be an additional feature because, with the old tool that we use, OnBase is already delivered. That is a very old version of the tool. It seems like OpenText is still trying to explore.

We still do not know enough about this tool. We are still trying to learn or figure out where we can find the information. It would be great if there were easy-to-follow user guides or videos that tell us the top 10 or 20 features that we should know about OpenText. It would be helpful to know how to do something from a development perspective rather than from a user's perspective. It would be helpful to know how to easily develop a report or a workflow. It will help people to do all the configuration and use the tool.

A dashboard with information would be nice to see.

The solution needs to improve the user interface. 

I have not used it enough to start running into issues. Some of my technical guys could name a couple of things, but in terms of support, we did have challenges getting good responses from them.

The solution should work better with partners and be more developer-friendly.

The tool's documentation is not proper and has missing information like steps. 

In terms of features, problems are mostly internal. We are still struggling with fixing our taxonomy and how we want our browsing to work. That is what we struggle with the most. There are no additional features that I would like to see. I am pretty happy with it, but their support could be a bit better.

Pricing could be improved and the stability or the performance needs improvement, which is very important.

The overall architecture is still a bit cumbersome. The architecture needs improvement, as it's complex.

• Compatibility with external source code management tools like RTC is missing. This would help in the automation of deployment activities for enterprise applications. 
• Improvement in analytics and machine learning would help in getting a more holistic view of content.

Mostly, we are looking for new, advanced UI features. Currently, the UI does not look great.

Initially there can be stability issues due to unknown factors such as usage of the system, quantity of documents ingested, load during peak hours. Over time, these stability issues can be solved by tweaking the system and scaling according to the volumes and requests done to the system.

User interface (at least in the version we are using, desktop client).