I am an IT personnel. We are supporting the tool. I am working for an IT firm here, and we are supporting a client.
The solution's most valuable characteristics are its features, mostly those used by its client, like workflows, some advanced capture stuff, dashboards, and reports.
The migration is a bit difficult in the tool. Whenever we make certain changes to workflow or other stuff, migrating the code from one environment to another is a bit tedious. The tool has an option for export and import, which is not robust. Most of the time, we need to do things stuff manually. For example, if we make any changes in the existing life cycle or any queues, we have to move those changes manually. There is no robust way to migrate code from one environment to a lower environment, like prod.
When it comes to the product's technical support, the turnaround time is a bit longer than expected. The issue may be because there are a number of issues or a large number of customers who are reaching out to the support team for help. I believe that the solution's technical team can provide a solution more quickly.
I have been using Hyland OnBase for ten years.
Whenever we have something or need assistance from a tool that is beyond our reach, like there are certain limitations, querying databases, or maybe any critical issues, we definitely reach out the solution's technical support team. I think my company is satisfied with the support of the product. I rate the technical support an eight out of ten.
I have experience with OpenText Documentum. Architecture and technology-wise, OpenText Documentum and Hyland OnBase are completely different. OpenText Documentum is more of a Java-based tool. Hyland OnBase has a .NET framework. Our client used OpenText Documentum for the manufacturing domain. They use the tool to maintain content related to the user guides, installation guides, and the images of the appliances, all this stuff. I am not sure how good OpenText Documentum is for the insurance domain, but it is good for manufacturing. Hyland OnBase has an expensive licensing model. What I feel is OpenText Documentum is more expensive than maintaining Hyland OnBase.
The product's initial setup phase is not difficult. I have managed three upgrades, so I can do everything individually with the tool. The upgrades were for the services used by clients.
My company takes care of the product's deployment phase in a sequence, though not always. Initially, maybe the first step would be the database of Hyland OnBase, followed by the services according to end-user clients. Applications and web clients are involved in the deployment, So it has a sequence, and it will take maybe six months. We need to do testing, starting from lower enrollments and all those things.
The product is insurance domain-friendly in nature. The tool is being used in domains other than insurance. What I feel is that the tool is more of an insurance domain-friendly tool. I think it benefits the insurance industry a lot in terms of security, maintaining the content, and using the workflows.
It is being integrated with Guidewire. Some other person did the Guidewire and Hyland OnBase integration, so it was in place, but we maintain stuff and support the integration.
I haven't explored any AI features in the tool. I think the tool has recently implemented a lot of changes with the cloud and is introducing new features as well, but I need to explore them.
I can recommend the tool to others. Once the setup of the tool is done for an organization, one has to look into more of the configuration part. They don't have to go for much complex customizations. If they are ready to spend time on the cloud-based maintenance of the servers, everything will be managed by Hyland, and the users won't have to take care of many such areas. If the users want to be secured and be within their network, they can go with the existing Windows-based servers, where they need to maintain the servers and databases.
With the features and advanced capture functionality, along with the content management stuff, I rate the tool a seven out of ten.