Hyland OnBase Reviews

Hyland OnBase was used as our primary document and image repository, and we extensively utilized the workflow module within it. It was used to store all of our customer documents, system-generated reports, operational items we needed, and check images. We built out a workflow module, including one specific for accounts payable.

Integrating Hyland OnBase with our systems enabled us to automate document designs and templates, which was extremely helpful in the finance and banking industry. 

The application allowed integration of front-end customer onboarding processes to create, route, ingest documents, and route them for approval within the application, enhancing audit traceability.

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.

It's the enterprise document storage utility, handling everything from member statements to reports and checks written against member accounts.

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.

We are a financial institution and we keep all of our member documents on Hyland OnBase. We keep statements, photo IDs, core system reports, etc. It also has a link to DocuSign where it automatically downloads DocuSign documents. 

The solution is very developed and we are not taking full advantage of its functionalities. 

We use this solution for record management and digitization of records. We also use it for workflows and to build online forms.

The retention module is one of the most valuable features. Whatever we scan onto the system can be identified and we are notified when the records are due to be disposed. 

My customers use it mainly for financial work, where they don't want their data leaked. If we put it on the cloud, there is definitely some chance of leakage. While every cloud is secure, ultimately, it is in the hands of the cloud admin. Therefore, we rely on an on-premises solution, which is much safer in the case of financial applications. 

Also, we have some customizations of OnBase, which are MRM, ROI, and those kinds of applications for the product which are used in the healthcare domain.

The product does allow some low-code development features. For example, suppose a customer needs some customization. In that case, they can put their small applications on top of OnBase, which can be integrated, and they can leverage its utility into their domains. That is one of the features which I could say is in huge demand. If a client doesn't have a technical team and prefers to do customizations on their own (rather than going back to Hyland and paying them for those solutions), they can do so.

They are improving their dashboards and reporting, which helps organizations as well. They have created some new types of clipboards in OnBase and working towards enhancement as well.

I primarily use OnBase for content management for our HR system, specifically to archive HR documentation.

The most valuable features are that it's very secure and provides audit trails for our documents.