Co-founder & Solutions Architect ECM CCM & Electronic Signature at Sabil IT
Real User
Top 10
2023-11-01T15:16:00Z
Nov 1, 2023
I would rate it around eight or nine, considering its capabilities in implementing and managing a high volume of documents. In the realm of capturing ECM solutions, there are limited choices, and the three major players capable of handling a significant volume of documents are OpenText, IBM (Datacap and FileNet), and Hyland. When we discuss ECM platforms, it encompasses not only the capture aspect, specifically Captiva in this context, but also includes archiving solutions and business process management tools. Regarding future enhancements for Captiva, I would like to see advancements in intelligent document processing. This is crucial as we encounter clients who are increasingly incorporating capture and recognition techniques based on artificial intelligence in their operations.
Assistant Vice President (Practice & Solutioning) at Genpact - Headstrong
MSP
2022-01-12T15:30:50Z
Jan 12, 2022
You should have a very good process. You should have a process-need gathering session to identify where exactly it is required and what type of problems it will solve. If you have that very well articulated, then it would be a better IDP solution to implement, and you will be able to use it properly. I would rate it an eight out of 10.
Senior Director, Platform Engineering at a real estate/law firm with 10,001+ employees
Real User
2021-11-15T22:57:00Z
Nov 15, 2021
I would advise utilizing a document standard, like CMIS content management interoperability standard. This would be good to use. Think of that as a JMS type of protocol for messaging. You can put the JMS protocol and you can swap out out any messaging infrastructure in the backend. It should work fine. JMS is the abstraction layer. Similarly, in document management, CMIS is the abstraction layer which provides a standardized interface to capture, search, and retrieve all the standard documents through a standardized interface. In the background, we have the flexibility to switch out a document repository to OpenText or whatever is working well. OpenText Intelligent Capture is pretty good. On a scale of one to ten, I would give it an eight.
Learn what your peers think about OpenText Intelligent Capture. Get advice and tips from experienced pros sharing their opinions. Updated: October 2024.
OpenText™ Intelligent Capture, formerly OpenText Captiva, is an enterprise capture platform, providing omni-channel capabilities for collecting everything from scanned paper to chatbots. It is not just for organizing content at the front door, but automating processes across the enterprise. It can automate processes for standard documents, such as Financial Accounts Payable and Accounts Receivable, or complex documents, such as contracts or partner requests that require action based on the...
I would rate it around eight or nine, considering its capabilities in implementing and managing a high volume of documents. In the realm of capturing ECM solutions, there are limited choices, and the three major players capable of handling a significant volume of documents are OpenText, IBM (Datacap and FileNet), and Hyland. When we discuss ECM platforms, it encompasses not only the capture aspect, specifically Captiva in this context, but also includes archiving solutions and business process management tools. Regarding future enhancements for Captiva, I would like to see advancements in intelligent document processing. This is crucial as we encounter clients who are increasingly incorporating capture and recognition techniques based on artificial intelligence in their operations.
I recommend using the solution. I rate the overall solution a nine out of ten.
I rate this solution a nine out of ten.
I rate this solution a nine out of ten. I recommend this solution to others, especially if they deal with vendor invoice management.
You should have a very good process. You should have a process-need gathering session to identify where exactly it is required and what type of problems it will solve. If you have that very well articulated, then it would be a better IDP solution to implement, and you will be able to use it properly. I would rate it an eight out of 10.
I would advise utilizing a document standard, like CMIS content management interoperability standard. This would be good to use. Think of that as a JMS type of protocol for messaging. You can put the JMS protocol and you can swap out out any messaging infrastructure in the backend. It should work fine. JMS is the abstraction layer. Similarly, in document management, CMIS is the abstraction layer which provides a standardized interface to capture, search, and retrieve all the standard documents through a standardized interface. In the background, we have the flexibility to switch out a document repository to OpenText or whatever is working well. OpenText Intelligent Capture is pretty good. On a scale of one to ten, I would give it an eight.