It's the enterprise document storage utility, handling everything from member statements to reports and checks written against member accounts.
Hyland OnBase
HylandExternal reviews
290 reviews
from
and
External reviews are not included in the AWS star rating for the product.
User friendly
What do you like best about the product?
I like App Buiider and think it would be very helpful for end users
What do you dislike about the product?
So many workview screens to open for end user
What problems is the product solving and how is that benefiting you?
Na
An enterprise document storage utility with flexibility and easy deployment
What is our primary use case?
What is most valuable?
Its most valuable aspect is its flexibility. You can apply any keyword to search for anything within a document. This flexibility is also its biggest drawback: If you overuse the number of keywords, you can run into performance issues.
What needs improvement?
Software malfunctioning usually occurs when we receive documents from external sources. The incidents are related to the source not providing the correct accompanying metadata or keywords, which then requires manual adjustments.
For how long have I used the solution?
I have been using Hyland OnBase for a year.
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
Eight people are using this solution. We have over a billion documents in our repository, it scales pretty well.
How are customer service and support?
We wanted to implement a stored procedure against their database instead of using their internal or provided APIs. To get permission, you have to go through an entire legal process.
They bear some liability if a document gets lost, destroyed, or leaked, so they don't want to give customers unrestricted access to write anything against their database. Even after we demonstrated the performance issues, they kept suggesting alternatives. They agreed only after we proved that their APIs couldn't deliver the performance we needed. We had to go through a legal negotiation to amend the contract to allow the stored procedure.
How was the initial setup?
They provide a SOAP-based API, which has been difficult to integrate with our MuleSoft Service Bus. We're considering moving to their more modern REST API, which has better security hooks that we can leverage more effectively with MuleSoft.
A typical system deployment can happen overnight. We don't have an automated pipeline for the application; everything is done manually. If it's strictly an update to the configuration, and barring testing, it's an overnight process.
Everyone involved in development, configuration, business analysis, and management is part of one team. A separate team of about four people is responsible for administration tasks such as patching the servers and installing the updates developed by the development group.
What other advice do I have?
The product does what you need to do if you have a regulatory need to retain a document for X number of months or X number of years. It allows you to set that expiration date, and once it hits that retention period, assuming you put one, it will handle the removal. For example, financial institutions must keep checks and images on hand for two years. After two years, checks older than that are automatically removed from the database and the repository.
They have AI offerings, but we have not yet investigated them.
Overall, I rate the solution a nine out of ten.
Really enjoy the experience.
What do you like best about the product?
Functionality is great. We are transitioning soon.
What do you dislike about the product?
I'm not sure what I may dislike at this time.
What problems is the product solving and how is that benefiting you?
Documents and Reviews
Great experience using OB, i am a principal developer who devs every day
What do you like best about the product?
The use of workview product, classes etc
What do you dislike about the product?
items that we cant delete, aka afks etc.
What problems is the product solving and how is that benefiting you?
going paperless, workflow solutions etc
OnBase from the mouth of babes
What do you like best about the product?
I like how flexible Workview is and how it literally can handle the class and view load that our bank uses it for.
What do you dislike about the product?
We dislike the inability to create a software enhancement request. We "understand" the whole voting thing but sometimes we have literal business critical problems with the software that are communicated through Deluxe to Hyland and into a forever black hole.
What problems is the product solving and how is that benefiting you?
We have a write once read many environment that is benefitting the global treasury management sales of products and services to the bank. We use Workview to create a custom application that is the vehicle for all of the GTM applications. Its ability to be custom and granular helps shape our solution that has to be easily modified per the industry and its continual shifts. That flexability is unparralled.
OnBase
What do you like best about the product?
Completly scalable solution where you can use as much or as little of the functionality as you need
What do you dislike about the product?
It can sometimes be difficult to find the best way to do something
What problems is the product solving and how is that benefiting you?
Electronic Forms and Workflows as well as Document storage
OnBase Review
What do you like best about the product?
I like how complex and customized you can configure your solution.
What do you dislike about the product?
OnBase Studio's code editor could use more features that would make testing custom Unity Scripts easier.
What problems is the product solving and how is that benefiting you?
We have a lot of complicated workflows and business rules that we can automate to reduce human entry error.
Good But Could Be Improved
What do you like best about the product?
The ability to integrate with almost any software tool or business process.
What do you dislike about the product?
Moving items and configuration between environments. The ability to mass update certain config items. ***The healthcare web viewer lost functionality in more recent versions and is preventing an upgrade.***
What problems is the product solving and how is that benefiting you?
Content is no longer being stored in multiple places and in multiple formats in an unsecurred fashion.
Users are able to accomplish most of their work from a single system.
Users are able to accomplish most of their work from a single system.
Offers good dashboards and reports but fails to offer better migration features
What is our primary use case?
I am an IT personnel. We are supporting the tool. I am working for an IT firm here, and we are supporting a client.
What is most valuable?
The solution's most valuable characteristics are its features, mostly those used by its client, like workflows, some advanced capture stuff, dashboards, and reports.
What needs improvement?
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.
For how long have I used the solution?
I have been using Hyland OnBase for ten years.
How are customer service and support?
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.
Which solution did I use previously and why did I switch?
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.
How was the initial setup?
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.
What was our ROI?
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.
What other advice do I have?
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.
Hyland OnBase is a great Enterprise Document Management System
What do you like best about the product?
We are using Hyland OnBase on an enterprise scale, and we are very happy with the system (OnBase) and the vendor (Hyland). The system is stable and easy to maintain. Compared to other systems and vendors, there is a decent amount of documentation available. The vendor is also very responsive to support cases.
OnBase comes with a vast set of features. Beyond document retention (which it does well), it comes with many added features like Workflows, Workview, and many more that can immensely help an organization. OnBase is definitely more than just a document retention system.
One of the nice things about OnBase is the administration. Hyland offers most features as “clicks not code” so that administrators with less technical experience can still configure the system. In many places Hyland also offers the possibility to tie into the power of scripting to enhance the functionality that is accessible out of the box. This strikes a nice balance between ease of configurability and increased flexibility.
OnBase comes with a vast set of features. Beyond document retention (which it does well), it comes with many added features like Workflows, Workview, and many more that can immensely help an organization. OnBase is definitely more than just a document retention system.
One of the nice things about OnBase is the administration. Hyland offers most features as “clicks not code” so that administrators with less technical experience can still configure the system. In many places Hyland also offers the possibility to tie into the power of scripting to enhance the functionality that is accessible out of the box. This strikes a nice balance between ease of configurability and increased flexibility.
What do you dislike about the product?
This is really just personal preference, but I would love it if OnBase supported Linux hosts.
What problems is the product solving and how is that benefiting you?
It is helping us organize documents and forms, manage retention, and many of our processes are handled in OnBase workflows.
showing 151 - 160