OpenText Content Manager Reviews

I'm an administrator at the moment. I normally work with staff to structure different BCSs (Business Content Services). I've been working on BCS restructuring and, in another project, on the disposal of records - basically archival and destruction of documents and folders. 

Lately, I've been working on the data governance regarding the migration and move to SharePoint. So I've been writing instruction publications on it, and I've also been training on Content Manager. It's a daily work, mainly digital.

There's barely any physical work at this stage. Basically, I try to improve the information management maturity of the organization I work in.

I came into this organization two years ago for the archival and destruction project. I saw that the information management maturity was poor and needed to change. That's how the BCS project started, to restructure the way people use document collections within the system. But there's very little interest from the agency itself in improving, unfortunately, apart from a couple of people who are responsible for line records management. 

Otherwise, it's been a struggle to get staff interested in improving how they work with information, their record-keeping, and so on. It's been a little bit tough from that perspective. It still is.

And that's because, before I started working here, the people working on the system were not qualified records and information managers. They caused enough damage that people became uninterested in the process of information governance. This includes the executive. So, basically, everyone's looking forward to moving out of Content Manager and into SharePoint.

We are a system integrator. We deal with client requirements to determine the best solutions that should be deployed. Our primary use case for OpenText Content Manager is managing enterprise content, such as documents and emails, as well as engineering document management.

OpenText Content Manager has provided a return on investment through improved content management functionalities and reliable performance.

Our organization primarily uses OpenText Content Manager as a document management system to handle various SAP modules such as procurement, material management, SCM, finance, and documents generated in Salesforce. It helps us manage, monitor, and control these documents by creating a repository for access, tracking changes, seeking approvals through workflows, and classifying content.

The tool's implementation has made life easier for customers. It is sold by SAP. The integration between SAP and the solution is good, making it easy to access the documents. It is widely recognized as a market leader in enterprise document management. 

The solution automates everything and helps us to track every move. It increases visibility and saves time in finding the documents using classification. The ability to track document changes is critical, especially for legal documents and those related to procurement. Knowing what changes occurred, when they happened, who made them, and the approval process are all crucial aspects managed by the record management solution.

OpenText Content Manager has improved our efficiency by 50-60 percent. 

The solution is for managing content where users want to keep and secure documents, with records management functionalities to streamline document workflows. It involves adding metadata to organize content and establishing connections between documents, facilitating efficient information organization for various processes.

Understanding customer requirements, including governance for trustworthiness, is crucial. Our process involves operations, unit access databases, testing, and transitioning to configurations and development environments. This includes full-term development and providing support during the go-live phase and beyond.

The first advantage is integration with your IP directory. You can customize any metadata and centralize all content, making it accessible to users. When a user is hired, the system automatically restricts and allows access according to their role. Another feature is organizing content into groups or rows within the system. Additionally, you can integrate modules to classify users and documents with specific security levels for enhanced security. The solution supports various levels of security, including private, secret, or public information, ensuring users can access only what they are authorized to see.

I use OpenText Content Manager in my company as it serves as an ECM solution to store documents and workflows. The tool also helps with record management and offers many connectors with SAP and Salesforce that help store documents.

The most valuable features of the solution are that it offers connectors, helps with document storage, offers workflows, and takes care of report management.

Our primary use is Records Management, with a secondary push by some to use it for all document management to include all draft work and convenience copies.

We are required to have a robust Records Management system. It does this job. We had it integrated with HPRM ver 8.3, but dropped the integration when we moved to HPE-CM 9.1.  Integration was not well documented.                                                          

The solution has a good security infrastructure and a stable framework.

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.

We use the solution for records management.

The solution allows us to do digital management, everything being digital nowadays, without the need to resort to paper use. The entire process has been digitized.