Practice Director at a outsourcing company with 51-200 employees
Reseller
Top 10
2025-02-14T04:30:45Z
Feb 14, 2025
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.
Senior Solution Architect at Freeport LNG Development, L.P.
Real User
Top 10
2024-06-10T17:53:00Z
Jun 10, 2024
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.
Technical Lead at a financial services firm with 51-200 employees
Real User
Top 20
2023-10-20T19:29:00Z
Oct 20, 2023
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.
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.
OpenText Content Management offers seamless document storage and advanced search features. Ideal for organizations needing integration with SAP and other applications, it enhances workflows while ensuring security and compliance across multiple platforms. OpenText Content Management stands out with its advanced integration capabilities, allowing seamless connectivity with SAP and other applications. Its enhanced security and permission systems safeguard information, vital for industries like...
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.
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.
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.
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.