Support could be enhanced. The first line of support consists of individuals who lack experience with some key aspects. When you create a support ticket, the time to resolve the issue may be prolonged because the first person may not understand the system or the solution.
Consultant at a tech services company with 501-1,000 employees
Consultant
Top 20
2023-10-30T11:51:58Z
Oct 30, 2023
There could be an improvement in security and permission infrastructure, which is very complicated. Most of our build governance and security is set at the group or department level. Setting that up and the efforts required for management or information architecture are very high-level. Setting up information architecture is much quicker and easier in SharePoint than in OpenText. Compared to SharePoint, OpenText is a bit more secure, but I agree that SharePoint is better from a maintenance point of view. Also, the solution could be more user-friendly. OpenText Content Manager is tightly coupled, using Java-oriented applications at its server site. However, other applications like SharePoint are moving to Angular, providing a proper front-end stack. This allows development on the front-end side without requiring server-side implementation, resulting in a decoupled front-end. OpenText Content Manager, on the other hand, is still mainly using transcripts.
Director at a tech services company with 11-50 employees
Real User
2021-10-25T20:17:20Z
Oct 25, 2021
The ease of use should be addressed. If one is skillful then this will not present a problem, but a person who is not will be forced to struggle. Mobility, as it relates to the ability to have access, should also be addressed.
OpenText Content Manager, formerly Records Manager, is a governance-based enterprise content management system designed to help government agencies, regulated industries and global organizations manage their business content from creation to disposal. Regardless of how you create and collaborate on your content, Content Manager gives you the ability to leverage accurate, contextual, and complete information throughout its lifecycle. Managing your content in this way helps you significantly...
Support could be enhanced. The first line of support consists of individuals who lack experience with some key aspects. When you create a support ticket, the time to resolve the issue may be prolonged because the first person may not understand the system or the solution.
OpenText Content Manager needs to improve its user interface. Its installation process is difficult and can be made easier.
The stability of the solution is an area of concern where improvements can be made.
There could be an improvement in security and permission infrastructure, which is very complicated. Most of our build governance and security is set at the group or department level. Setting that up and the efforts required for management or information architecture are very high-level. Setting up information architecture is much quicker and easier in SharePoint than in OpenText. Compared to SharePoint, OpenText is a bit more secure, but I agree that SharePoint is better from a maintenance point of view. Also, the solution could be more user-friendly. OpenText Content Manager is tightly coupled, using Java-oriented applications at its server site. However, other applications like SharePoint are moving to Angular, providing a proper front-end stack. This allows development on the front-end side without requiring server-side implementation, resulting in a decoupled front-end. OpenText Content Manager, on the other hand, is still mainly using transcripts.
The product could improve its scalability.
The ease of use should be addressed. If one is skillful then this will not present a problem, but a person who is not will be forced to struggle. Mobility, as it relates to the ability to have access, should also be addressed.
This is a client-side app, and a web-based app would be easier to support. Easier integration with SharePoint and other apps would be an improvement.