OpenText Extended ECM Reviews

We are selling this solution to our clients and we have an implementation team that takes care of the delivery.

Most of the customers use it for information governance, records management, workflow capabilities, and basic document and version control.

Some of our clients also use the AppWorks technology for local app development solutions.

Most of our customers are very fond of the upgraded smart user interface. It was lacking in previous versions.

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

I have been dealing with OpenText ECM since 2011.

Our customers are quite impressed with the stability. There are no issues.

We have not contacted technical support.

The initial setup is very straightforward and the configuration is quite easy.

Depending on the use case of the customer, a project can take between three months and maybe 12 months to deploy. It depends on how complex the requirements are of the use case.

If there is an integration that needs to be done, then it can take up to about 12 months.

We have a support team that looks after any issues.

I would definitely recommend OpenText ECM. Where we are with GDPR and POPI at the moment, I will definitely recommend this solution.

I would rate this solution an eight out of ten.

Building an ECM repository for a leading high street bank in Scotland and integration with internet banking applications.

It is a very stable system, and we are using it to store billions of customer documents which are readily available for search and browsing. It is very easy to integrate all ECM features with other enterprise applications that are helping the bank with easy modernization. 

• Content server
• Archive server
• Search and indexing
• Enterprise integration
• Records management
• Patching
• Web reports
• Scaling and auditing.

• 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.

Simplicity to roll out, features available, customization options.

All the information is now stored in a central repository that is accessible to everyone.

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

I've used this solution for six years.

Yes, but we believe those were related to our environment.

No.

7 out of 10.

No (we were using file servers).

Straightforward.

It is an expensive solution. The licensing is not that complex for the core products, but it becomes more complicated for some additional modules.

Yes. We evaluated SharePoint & Documentum .

To keep up to date with the latest versions of the products because OpenText continues to invest money on new features.

Our primary use is for software development. It also offers capture. So far, we have been satisfied with the product. 

If you are an SAP user, you can store documents directly into OpenText without a connector. The connector is out-of-the-box, which is one of the key advantages that most customers are looking for.

It can be found in the original SAP, and no other product is offering it. OpenText has a very strong connector, which is called "ECM for SAP".

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

It is a stable solution. It is one of the market leaders.

Scalability is great. We can extend areas horizontally and vertically. So far, we have had no issues at all with the product.

We have been using OpenText from the beginning.

The initial setup was straightforward.

OpenText is a very strong offering from the engineering management side, as well with its SAP integration. Its weak point is the UI's look and feel.

The integration of a document management platform with many other applications, e.g. SAP, SuccessFactors, Salesforce, SharePoint, etc. There is a large amount of documentation available, along with solution accelerators to speed up and facilitate the initial setup and integration.

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.

Over two years.

No, Content Server is highly scalable, both horizontally and vertically. Additional servers can easily be added to the cluster. At the back-end, additional resources can be added to increase performance of the agents, indexing, and searching capabilities. The front-end can also be scaled horizontally or vertically to improve performance when dealing with a large number of simultaneous users.

High. When contacting OpenText support we always get an answer within a few hours. The technical support is also very knowledgeable on most of their products, and provides frequent updates when working on a ticket.

The initial setup was, and still is, complex because there are many components interacting with each other. There are multiple settings to check and configure. A vast knowledge of infrastructure, networking, security, software tools, and more are required to install a performant solution.

Get in touch with experts, either directly from the vendor or consult with an external party that has deep expertise in implementing a similar solution.