The main thing is the cost. Most of the time, organizations move away from Documentum due to cost. It's highly-priced, and the support costs are high. Now, SharePoint and other options. Microsoft gives free licenses, so organizations mainly look for cost-effective products. The second thing is updates and patching. We patch very often, every six months or a year. We have SP1, SP2, and SP3, and then suddenly, it's moved out of support. That's the organization's main pain area. They don't want to keep investing from a storage perspective. The licensing model should be changed. The product itself is out of support. They have not considered it for AI initiatives. The new version should be on the cloud. I'm not sure if the new version of Documentum, xECM, is cloud compatible or on which cloud it is compatible, but the OpenText server itself is on a cloud, which would be beneficial to the business. And it would also be easier for migration.
One area for improvement in OpenText Documentum is its handling of outdated documents, especially technical ones. Currently, older files remain online and clutter storage, but a new feature to offline these files for select users has been suggested. Additionally, there is a need for better management of offline access, restricting it to only essential users to maintain security and streamline access.
Assistant Content Manager at a agriculture with 10,001+ employees
Real User
Top 20
2023-10-25T15:29:00Z
Oct 25, 2023
The main issue is the software's performance when storing around 10 million or more documents. It becomes slow and needs improvement. Perhaps it's a cloud-related issue, but it needs to be addressed. It could be due to our S3 bucket or something else. Nevertheless, this is a significant challenge we're facing. Additionally, OpenText doesn't support certain file formats, such as .rai. Some of our analyzed documents come directly from machinery. We utilize an IoT device, and some of the analyzed document files are directly generated by the machine. We then store them in the S3 bucket. However, when attempting to import these documents from the S3 bucket to OpenText, they fail to open. This is the primary issue. As a result, we have to convert these files to PDF before they can be opened. So, I hope for improved performance, particularly with a large number of documents, in future releases of the solution. Currently, our old software stores only eight million documents. However, we have over 15 million documents in our legacy software because we've been using it for the past 15 years across the globe. We have over 50 million documents in total, but only eight million are currently stored. As a result, the performance was slow, comparatively slow.
Documentum is a very robust system. Everything can be improved, but at this time, I do not have anything in particular. If anything, they can put our software in their standard.
We mostly use the Life Sciences package. That package is somewhat dated. There should be enhancements to the Life Science package and additional offerings to support pharma in particular.
Enterprise Architect at a computer software company with 5,001-10,000 employees
Real User
2020-07-13T06:55:48Z
Jul 13, 2020
An area that needs to improve is how to reduce storage space on the AWS site. Also, scaling up is difficult and we need to look at how to scale a system. If the documents increase the application size, then we need to know how we take care of reducing the size as well as scaling up the application. In the next release, I would like to see more cooperating workflows, better integration with other systems, and RESTful services.
OpenText Documentum organizes, preserves and makes information accessible, while ensuring it adheres to all privacy and security protocols. Documentum manages content across file stores and integrates with enterprise applications, including SAP, Salesforce and Microsoft, to help organizations conquer information management challenges. Documentum provides integrated support for the entire lifecycle of a wide range of content; beyond typical office documents to include CAD files, design...
The main thing is the cost. Most of the time, organizations move away from Documentum due to cost. It's highly-priced, and the support costs are high. Now, SharePoint and other options. Microsoft gives free licenses, so organizations mainly look for cost-effective products. The second thing is updates and patching. We patch very often, every six months or a year. We have SP1, SP2, and SP3, and then suddenly, it's moved out of support. That's the organization's main pain area. They don't want to keep investing from a storage perspective. The licensing model should be changed. The product itself is out of support. They have not considered it for AI initiatives. The new version should be on the cloud. I'm not sure if the new version of Documentum, xECM, is cloud compatible or on which cloud it is compatible, but the OpenText server itself is on a cloud, which would be beneficial to the business. And it would also be easier for migration.
While generally secure, some noted security issues need consideration. The installation process for on-premise setup needs improvement as well.
One area for improvement in OpenText Documentum is its handling of outdated documents, especially technical ones. Currently, older files remain online and clutter storage, but a new feature to offline these files for select users has been suggested. Additionally, there is a need for better management of offline access, restricting it to only essential users to maintain security and streamline access.
The main issue is the software's performance when storing around 10 million or more documents. It becomes slow and needs improvement. Perhaps it's a cloud-related issue, but it needs to be addressed. It could be due to our S3 bucket or something else. Nevertheless, this is a significant challenge we're facing. Additionally, OpenText doesn't support certain file formats, such as .rai. Some of our analyzed documents come directly from machinery. We utilize an IoT device, and some of the analyzed document files are directly generated by the machine. We then store them in the S3 bucket. However, when attempting to import these documents from the S3 bucket to OpenText, they fail to open. This is the primary issue. As a result, we have to convert these files to PDF before they can be opened. So, I hope for improved performance, particularly with a large number of documents, in future releases of the solution. Currently, our old software stores only eight million documents. However, we have over 15 million documents in our legacy software because we've been using it for the past 15 years across the globe. We have over 50 million documents in total, but only eight million are currently stored. As a result, the performance was slow, comparatively slow.
Documentum is a very robust system. Everything can be improved, but at this time, I do not have anything in particular. If anything, they can put our software in their standard.
We mostly use the Life Sciences package. That package is somewhat dated. There should be enhancements to the Life Science package and additional offerings to support pharma in particular.
OpenText Documentum needs to improve its support.
It's difficult to manage and customize Documentum.
The user interface can be improved. Searching for documents is complex and should be easier.
An area that needs to improve is how to reduce storage space on the AWS site. Also, scaling up is difficult and we need to look at how to scale a system. If the documents increase the application size, then we need to know how we take care of reducing the size as well as scaling up the application. In the next release, I would like to see more cooperating workflows, better integration with other systems, and RESTful services.