Hyland OnBase Reviews

I developed a meeting minutes and meeting record system together with Hyland OnBase. I used Hyland OnBase's workflows together with WorkView to create a more user-friendly interface, and we recorded all the company's meeting minutes. More recently, I developed a feature where the meeting is actually recorded, the audio is stored in Hyland OnBase, and artificial intelligence writes those meeting minutes.

This is an important use case because considerable time used to be lost creating these minutes. Now they usually come out one hour or an hour and a half later already drafted and reviewed by the client themselves, as this document goes into a review workflow. The executive secretary staff review it, check if everything is correct, listen to the audio, compare the information, ensure everything is in order, and then release it to whoever has the right to access these meeting minutes.

The main improvement is being able to locate documentation with Hyland OnBase. Since you link documents with data, you can create indexes and structure your entire document framework in an organized way within a single repository. You don't need to keep looking at paper; you see everything digitally.

I'd highlight the protocol area for Hyland OnBase, as I also use it for incoming documents at clients in the protocol and receiving area. Before, the protocol staff took around two or three days to distribute the documentation that arrived on a given day. It only reached the departments two or three days later because they had to separate the documents. Today, the document arrives, it is scanned, and instantly it goes to the department's incoming queue. Within hours that document that just arrived is already available in the department.

I appreciate working with Hyland OnBase because I can design the entire workflow for specific areas and take that flow and process into Hyland OnBase in a simplified way so the user can interact with the tool. What I find exceptional is the document storage itself; it's outstanding how quickly you can find documents, content within documents, or images. This is very important for locating certain topics. Even if you don't have index fields, you can search within the documents for that information and it brings everything back to you.

Besides the features of Hyland OnBase, there's also the practicality because everything is configured. I'm a full-stack developer and build some things when Hyland OnBase doesn't meet some requirement the user requested, but 95% of what I do is all handled natively within Hyland OnBase.

There are some particular aspects of Hyland OnBase, such as layouts or some modules that have just been built, that are not designed with the end user in mind. That's something they need to improve. However, even if it's not adequate for the end user, you can still take that and, with custom development, use those modules and APIs in a user-friendly way. They need to improve the interface and usability of Unity and think more about usability. In terms of tool usability, sometimes there are too many clicks to perform an action, which, if you developed it yourself, you could do in two clicks, whereas within Unity you need four or five clicks to do the same process.

I used Hyland OnBase for 11 years.

I experienced version issues when Hyland OnBase Unity went from version 13 to 15, and there were some bugs. Since then they've improved a lot, and now it's very stable.

It depends on how Hyland OnBase is configured. In the cloud it's easier to handle; you work with pods and other infrastructure elements. It depends a lot on what you want.

I always had good support as a customer of Hyland OnBase. There were cases where I had to talk directly with Hyland in the United States, and whenever I proved it was an issue on their side, they always followed up quickly and professionally and always resolved the problems.

I'd rate customer support for Hyland OnBase on a scale of 1 to 10 as a 10. I always had good responses and, regardless of the time, they always helped me.

Hyland OnBase was used only for document storage when I started with the company. There wasn't any other tool besides Hyland OnBase at that time.

The benefit is not headcount reduction, but I've seen a lot of time savings with Hyland OnBase, as demonstrated in the examples I mentioned.

There's also prevention of financial loss because I have some workflows designed specifically to validate certain processes, and in the past a lot of money was lost because calculations were done incorrectly. Now, by having that process inside Hyland OnBase, the configured process has prevented large losses from miscalculated values.

Hyland OnBase is a bit expensive here in Brazil. I think the price is high, but there's a return in terms of scalability and confidence in the tool because it's always there in the ECM magic quadrants. So there is value added.

I looked at Documentum, which is more focused on document storage, and also Pega before choosing Hyland OnBase. They all have their strengths, but what attracted me most to Hyland was how easy it is to configure your entire process.

I would give Hyland OnBase a rating of nine out of ten.

As I mentioned, you can do a lot natively, just with configuration. That nine is because of that. You can meet 95% of requirements with configuration alone. For the other 5% you have to develop to satisfy the client. If there were something that let you do more development inside the tool with regard to layout and usability, the tool would be a 10.

Hyland OnBase has evolved a lot in the AI features. I've been following it, and they've improved a lot. However, like with any AI, I have to be careful. I have to manage the AI so that it doesn't leak information from a governance perspective. As with all AI, we're at a certain stage now and I believe in the near future this will evolve a lot and will greatly help in building processes.

At the moment, I'm appreciating the accuracy and reliability of the results from Hyland OnBase's AI features. In terms of reliability, I'm always a bit cautious, not just with Hyland's AI, but with any AI. There always needs to be someone monitoring and seeing what is being done. You always have to audit to see if there are any failures because AIs tend to be very proactive and can end up leaking unnecessary information.

I've worked with private cloud, in the cloud, and on-premises for Hyland OnBase. I've worked in all those scenarios; it depends on the client. Each client organization decides where it will be hosted.

Currently, I'm using Hyland OnBase's own cloud when the solution is hosted in the cloud.

I'd recommend checking which modules of Hyland OnBase would meet your needs at that initial moment. I would start with Hyland OnBase's basic modules, which are the document part, WorkView, and others. Only as you become very familiar with it, after you've done the training and everything, would I start expanding to other modules.

For an example of how my team or department uses Hyland OnBase in our daily work, accounts payable uses it for processing and finalizing payments, and Hyland OnBase is also used for its mass import capabilities such as DIP, COLD, Mailbox Importer, and EDI, especially by outbilling areas to quickly bring in needed documents for the workflows.

Another major use of Hyland OnBase by our organization is that it has found more and more use in new departments to ease workflow, cut down on time, and reduce paper use.

Out of those features, the workflow engine has made the biggest difference for me because it is excellent for automating approval processes, and we use Hyland OnBase for legal requests, hardware requests, travel requests, corporate credit card requests, and file transfer requests.

WorkView is an incredible module for gathering and displaying summary information, and we utilize it highly in our subsidiary to manage our legal contracts, their financial billing process, and their travel. We also use the Document Import Process coupled with Unity API for writing custom code to automate processes to send and receive data from other systems that are not yet API enabled.

The impact of Hyland OnBase on our organization is that automating manual processes has had an incredible effect on our return on investment, and the man-hours saved by automating processes pays for the system, ranging from one to five hours.

I measured the man-hours saved through the tracking of workflows and automation processes.

Additionally, Hyland OnBase has allowed us to move away from moving paper around various departments, providing workflow management to keep approval inside the system and out of the email boxes, eliminating the need for paper storage, and saving storage costs with other vendors.

More timely updates to solution software support documentation also should be improved.

Positive

Hyland OnBase is a great product with a lot of features and flexibility for customization to implement various business needs, making external integration with various business systems easy. Overall, it is a robust solution that can support the demanding usage needs for multiple departments and is very stable, secure, and has been a reliable and easy, scalable solution for our organization.

I found this interview to be well done but suggest trying to be a little faster. I gave this review a rating of 9 out of 10.

My main use case for Hyland OnBase is that companies in Colombia use it for document retention projects, handling all document retention tables for all the data they use. They search for software or a platform like Hyland OnBase to manage this, and mostly all processes involve using the orchestration part of Hyland OnBase to integrate CRMs and ERPs to orchestrate these different programs, primarily for processes.

The orchestration with other systems, such as CRM or ERP, works primarily with how data is handled in Hyland OnBase, especially with WorkView. The connection of different tables and data makes it easier to connect to, for example, SAP or Oracle, because we structure data related to unstructured data, such as documents. We mostly take unstructured data from the CRM, organize it in Hyland OnBase, activate processes, and use the metadata of this data to send it to the ERP for handling a lot of documentation that is not structured.

About my main use case, the no-code or low-code capabilities of Hyland OnBase are powerful because they let you handle processes easily. It also requires managing processes with functional knowledge so that managing them in Hyland OnBase is much easier, as you don't need coding experience unless you want to do more complex things. You can create processes in 10 to 15 minutes, automate many tasks, and manage roles efficiently, making it easier for many users in your company to access the information they need, with clear rules.

Hyland OnBase positively impacts my organization, particularly in contract management, where numerous areas were using different contracts. With Hyland OnBase's feature to create documents based on metadata, contract agility has allowed contracts to be sent to the legal team quicker, and they know contracts are only modified in specific parts. The integration with a digital signature provider has accelerated this process; contracts that previously took about four weeks to sign now take less than a week to get signed and approved both internally and by the client.

I have noticed measurable benefits, such as reduced errors because everything is handled in one place, acting as an electronic content management software. With everything centralized, I minimize the chaos of having emails and CRMs everywhere. I control user access and interactions easily, leading to minimized errors. Implementing automated processes is straightforward, which I consider the main benefit of Hyland OnBase.

In my opinion, the best features Hyland OnBase offers include migrating to a software as a service model and enhancing the cloud part of Hyland OnBase, meaning you don't need a specific architecture in your enterprise to use it. The user experience and UI of Hyland OnBase have significantly improved in the past few years, especially with the implementation of AI, which is now being used for unstructured data, making it one of the best capabilities that Hyland OnBase has nowadays.

For example, when I have all documentation well organized, I can ask for KPIs or review many documents to have clear answers to what I want. I can compare this data because I have well-structured numerical data alongside the information within the document. The AI integration in recent releases of Hyland OnBase allows for better analysis and is a standout feature.

Regarding the features, the no-code and low-code aspect is excellent. As a user without technical expertise, if you understand your company's processes, you can implement them quickly and assign roles easily. It's crucial to use Hyland OnBase the right way by establishing simple rules and automating specific processes rather than trying to use it as an ERP, which is not its intended use.

I believe Hyland OnBase can improve its cost structure as a platform or software as a service because currently they only sell a few packages that come bundled with many modules likely not used by clients. There should be an option for clients to start with specific functionalities because the ROI for Hyland is difficult to demonstrate. Most use cases tend to cater to specific industries, which makes it challenging from a commercial perspective because companies mostly use it for compliance relating to document handling.

Regarding improvements, a better user interface is needed. Although they have been migrating toward having a unified platform, the original Hyland OnBase still has areas needing development in terms of aesthetics. It should have someone dedicated to designing the UI to be clean and responsive, as right now it's not mobile-friendly and could be more accessible via web exposure without needing an app.

I have been using Hyland OnBase for about four years, primarily for document retention projects, contract management, and the onboarding of fiduciary clients.

Hyland OnBase is stable.

Hyland OnBase's scalability is one of its most significant strengths. If you discover that one of your processes can be automated through Hyland OnBase, the authorization processes and clear flows make scalability across multiple areas of the company remarkably easy.

Customer support largely falls on us, as many aspects must be handled directly with Hyland. However, it primarily depends on the Hyland OnBase implementation team.

I have not previously used a different solution, as I started with Hyland OnBase.

However, I can say that automation processes that used to take four or three weeks now only require days, and users can be easily trained to implement their own processes. It is a user-friendly tool that encourages interaction. In terms of needing fewer employees, it doesn't necessarily reduce the workforce, but it enhances how effectively people use their time.

My experience with pricing, setup costs, and licensing highlights that one of the significant challenges for the commercial team in selling Hyland OnBase involves its high pricing, particularly in markets such as Colombia and Latin America. The pricing appears to be tailored more for the US or European markets, and there aren't smaller packages to demonstrate Hyland OnBase's capabilities effectively. Selling the complete suite is common, but if the client lacks use cases for the full software suite, return on investment can be elusive.

Before choosing Hyland OnBase, most people I encountered were considering Alfresco as an alternative.

I would rate Hyland OnBase a seven in its area but a six when compared with other software solutions because while it handles most of what you want from an enterprise content management tool, it becomes harder to sell the full package compared to other solutions that come from mixing programs such as business process management tools with document management tools.

The reasoning behind my ratings stems from recognizing how well Hyland OnBase serves its specific area as an enterprise content management tool but noting that compared to other solutions, such as those provided by Microsoft, the whole package can appear expensive when mixing similar functionalities.

I don't have much knowledge about Hyland OnBase's governance and security regarding its AI capabilities, but I perceive that the cloud component is better managed. I think the developers typically follow best practices for other elements.

The accuracy and reliability of Hyland OnBase's AI output largely depend on the quality of your company's data. If the data is good, the results are good. This is one of the advantages of using AI with specific, well-structured data, as it minimizes the risk of AI hallucinations since it utilizes only the documents present in your space.

Hyland OnBase is deployed in various ways within my organization as clients have different preferences; some use an on-premise solution, others utilize cloud services, and some have a mixed setup where a cloud provider hosts Hyland OnBase in different clouds. Its flexibility makes it agnostic in that sense.

My advice for others considering using Hyland OnBase is that if you're in the health sector or finance and banking sectors with numerous compliance requirements, then Hyland OnBase is well-suited for your needs.

As a business analyst, while working on a recent project, I used Hyland OnBase as an enterprise-like document management tool. It was used for storing, organizing, and retrieving invoices regarding our insurance project. I worked with the document management system specifically for managing invoices.

We used to receive pricing invoices from our customers, including customers in South Africa. We received those invoices and created a workflow automation. We navigated those invoices and fetched the required information by using OCR, which is already an integrated feature of Hyland OnBase. We extracted key information such as premiums, insurance policy names, premium coverage for the year, age, and particular PII information of the user. We sent them to our insurer. The person who was sitting in the back end performed verifications and then gave the underwriting result, and we provided the policy accepted or declined result. This entire workflow was automated by using Hyland OnBase.

Further, we managed documents including our training documents, business documentations, and business requirement documentations. We stored these in Hyland OnBase for our training and recording purpose for our next generation of colleagues to train them, whoever joined our new project.

Hyland OnBase offers features that are very much scalable. As the documentations, the size of the files, or number of files increase, it automatically scales itself. It is intuitive to use. It is easy for a newcomer to just get the KT and learn. There are technical support documentations, though there are fewer available from Hyland's side. Scalability is a major plus point. Customer support and technical service is also a good point for Hyland's side. It does not have any downtime. I have not faced it till now. All the services were up, fast, and reliable, and it is very secure. These are the features that stand out regarding Hyland OnBase.

During my project, as I already mentioned, Hyland OnBase can accommodate increasing document volumes and integrate additional users. During my project, the organization continued adding new documentation categories and increasing invoices that we saw. These were entirely integrated into Hyland OnBase without any further upgrade or storage upgrade, or affecting any system's performance. The architecture which Hyland OnBase works with has the capability of gradually increasing itself, rather than working on a fixed storage. That is how it was helpful to us.

I believe Hyland OnBase has impacted my organization positively by faster document retrieval that I mentioned earlier, intuitive setup, reduced manual processing, and comes with security. These insurance policies, underwriting, and invoices are very sensitive to the users as they contain PII information. From security aspects, it is very secure. It has increased the transparency of the processes and workflows. Every user who is involved in each of the steps is well aware. Even the manager gets an update. This is a very big plus point in seeing the transparency in this process. It has reduced the manual work and paperwork dependencies and also helped us to upskill more, make more business with less effort and person headcount. These are the helpful things.

More training videos, if they are more findable, would improve documentation and training documentations from Hyland's side, because there is a lack of documentation and training materials from Hyland's side in order to train new resources. Additionally, the use of AI should be introduced in the later features. If customer support is more quickly and easily reachable, it should be more useful. These are the three points.

The pricing structure could be more thought-out. If it were cheaper than it is now, I think it would be more useful and more companies could use it over other competitors.

If AI could be used more at an enterprise level, since we are purchasing at an enterprise level for the subscription of Hyland OnBase, I would say if those AI informations would stay within the enterprise and not go outside of our enterprise boundaries, it would be secure and maintain our privacy. This is the most important term in order to integrate AI into Hyland OnBase.

I have used Hyland OnBase for a year and a half.

Before using Hyland OnBase, the invoices used to come and we manually took out the key information details, which would take around a week's time, mainly four to five days. Now, with the onset of Hyland OnBase, this insurance workflow is done within one day. This much effort it has saved.

VDI and cloud was very easy. I was responsible for gathering documentations, making the BRDs and the UAT scenarios. The setup was easy and the document management system was very easy and handy. We can automatically get the required documentations without hovering or just searching around. It always has a clean interface where we can find whatever we need in a few seconds.

The two points I take off are for those improvement things which Hyland needs to work on that I talked about. If we generally speak about Hyland OnBase, it is a powerful enterprise management platform that is scalable, flexible, and secure in storing, retrieving, and making workflow automations. I am satisfied, but I would say it can look after the pricing, integrate more AI features, and improve training materials and documentations from their side.

I have not used AI as much because when I left the project, we were not using AI in Hyland OnBase. However, I have heard that they have integrated AI in recent releases. I am not sure about the accuracies of the AI integrated in Hyland OnBase.

My recommendation would be to have a focused business plan or use case. You can do a competitor analysis with Hyland OnBase and other products in the market. Hyland is a standout in every aspect because if you go ahead for your business use case, defining clear document classifications, then the metadata standards, then your workflow requirements before implementation, it would be better. Investing in document management for training materials is important because the platform has a learning curve, and people adoption significantly influences project success. Investing in user training is equally important, and also focusing from my role as a business analyst, involving business stakeholders early during project kickoff for requirement gathering and validation workflows through demos helps in ensuring we build a final solution that aligns with their business and operational needs. These are the things which users can consider before using Hyland OnBase. I gave this review a rating of 8.

My main use case for Hyland OnBase is implementing it as both a simple and complex document management system across many different market segments for the sole purpose of making scanned and virtual documents easily searchable and accessible. The workflow capabilities of the product, as well as the Unity web interface and the ability to seamlessly tie into most third-party applications to allow easy associated information lookups within Hyland OnBase, led to a very dynamic and game-changing product compared to how my organization was previously managing their information.

A specific example of how I have used Hyland OnBase for document management or workflow in my organization is the amazing integration with third-party applications. Being able to get documents and information through email, folder importing, mainframe screens, other applications, and XML/CSV streams was simple, powerful, and effective.

Regarding my main use case, it is very simple, effective, and it just works when it comes to content management systems. We rely on static folder structures for storing information or Excel access tables, which can easily become a mess. With Hyland OnBase, every document is unique, and access can be restricted and audited depending on user permission. It allows for a company to take control of their information and be more productive.

The best features Hyland OnBase offers include a powerful admin interface. The Unity application is a work in progress, and Hyland OnBase also has document storage, basic workflow activities, and Hyland OnBase security is top-notch.

Great support channels for resolving application issues is something I would add about the features, along with support for a wide variety of files that can be stored within the product. It is also easy to query the database to pull reports on usage.

Hyland OnBase has positively impacted my organization because we use the system internally to our departments, but it also helps the system by filling out web forms that help us gather information from our employees quickly and more effectively than through email or paper methods. It is also very beneficial because we are able to reduce our paper costs by collecting documents electronically and keeping them electronically through the life cycle of that document. We have increased visibility into where our bottlenecks are for processing documents. It has become easier to identify inefficient processes and pinpoint how to leverage the product to reduce the time and effort needed to process that document.

We can easily retrieve documents that need to be stored long-term, enabling us to reduce our paper by collecting documents electronically and keeping them electronically throughout the life cycle of that document. This has reduced the cost by fifty percent. We have increased visibility into where our bottlenecks are coming from, especially which processes are processing documents.

Hyland OnBase can be improved because Report Services is an additional license and should be included with the base product. The reason I take off that one point is that sometimes Report Services is an additional license, and that means extra cost.

I have been working in my current field for six years and two months.

Hyland OnBase is very stable and I have not experienced any downtime.

Hyland OnBase is very scalable because it can handle my organization's growth effectively.

The customer support for Hyland OnBase is fast and very responsive.

I previously used a different solution which was Microsoft Azure and Document Vantage on Demand.

I have seen a great return on investment with Hyland OnBase. We have been able to reduce staff by not needing temps and have achieved a great reduction of space due to not using file cabinets. It is nice to have instant images without getting up and looking for things.

My experience with pricing, setup cost, and licensing is that the price is relatively affordable, but as I mentioned, Report Services is an additional license. That means when I want to use Report Services, I prefer to pay more additional cost for using Report Services.

Before choosing Hyland OnBase, I evaluated other options such as Salesforce.com.

My advice for others looking into using Hyland OnBase is that it is more efficient, fast, and easy, making it a great business process management and workflow tool to manage the API. My organizational business areas are able to automate what was once manual tasks by leveraging the ability to define workflows that are congruent to internal business processes. Hence I am able to save a lot of time and cost. I would rate Hyland OnBase a nine out of ten.

Positive

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.

Hyland OnBase offered robust system features ranging from configuring indexing fields to building auto-import routines for regular file imports. 

It provided data security features, allowing restrictions on sensitive documents, such as who could view or modify them. 

The user interface was intuitive, and the product integrated well with other applications like Outlook and Salesforce, enabling easy document indexing and access.

We found the size of images to be a restriction, though this may have been due to the API used rather than the Hyland application. The application could potentially be more open-source, allowing integration with more solutions.

I used Hyland OnBase for approximately eight years, starting around 2015.

Hyland OnBase was a stable solution that worked effectively for us, providing traceability and data security.

We had an enterprise license, which allowed unlimited users and a number of workflow licenses. We never crossed the threshold of workflow licenses, as the workflow was executed via system licenses, not directly through user licensing.

We primarily worked with Fiserv for technical support and not directly with Hyland. The Fiserv team was helpful, although instances existed where their database was tricky to manage. 

Our vendor relationship facilitated integration with our system and offered additional service beyond the Hyland OnBase product.

We transitioned from a document image repository to Hyland OnBase.

The initial setup was complex, particularly building a custom accounts payable workflow module. This task was supported and guided by the vendor, Fiserv.

Our implementation was managed by Fiserv, who served as the vendor and reseller, providing key insights and support during the complex integration process.

As we had an enterprise license, we were not limited in terms of user access. We also paid for workflow licenses, which allowed up to 250 concurrent users.

Alfresco was an alternative used within the organization, but I only engaged with it as a generic user.

Hyland OnBase appeared more robust compared to Alfresco, but this perception might be influenced by deployment and configuration differences. Users appreciated the user interface and extensive integration capabilities.

I'd rate the solution eight out of ten.

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.

Positive

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.

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.

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.

I have been using Hyland OnBase for a year.

Eight people are using this solution. We have over a billion documents in our repository, it scales pretty well.

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.

Positive

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.

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.

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.

The dashboards and reporting are quite good.

The product does offer a low-code environment, which is great for non-technical teams. 

We found the setup process to be okay since they do offer a troubleshooting guide.

It is scalable and stable. 

The dashboards do have some room for improvement as compared to the other vendors which are there in the market. That said, it depends on the use case that the customer has. 

They need to focus on security for financial organizations and healthcare domains that are using it. For them, while the current dashboards are meeting their needs, the market is changing. They do need some transformation on top of it.

In terms of reporting, we don't have anything on the artificial intelligence side. For example, if one of my customers is uploading their invoice, they have an OCR feature which is known as Optical Character Recognition, and their system does read those things; however, in this solution, they don't have a mechanism, as of now, to improve it further. Therefore, if I have uploaded an invoice that includes my name, it should be able to suggest to me that there are other documents that already have this name in them. The search engines could use some artificial intelligence to make the solution much, much better.

If I'm using Google, and if I try to search for a name with a string, it will show me all the files which are coming with the name, which are all the listings of the files, before I add the complete name. Then it will start displaying the list of files. The search functionality in this product should offer a similar approach and make suggestions based on what you are typing. 

The troubleshooting guidelines could be more clear during the initial setup. 

I've been using the solution for the last six months.

It is stable and reliable. 

It is like a Windows application. If I have done an installation on my machine, then it will work properly. We will not run into any issues related to security or scalability if we have proper hardware in place. However, if I'm installing it on my laptop and I don't have the appropriate RAM to run it, then it will be challenging. Otherwise, it works nicely.

The solution is scalable. 

I've never escalated issues to technical support.

I have worked on Hyland OnBase only.

Installation-wise, there are sometimes some challenges. However, we do have some troubleshooting guides that help us troubleshoot the issues we are getting. At times, it includes a few different components, so there is room for improvement to help the troubleshooting guide become clearer. We can easily handle a one-time installation in the case of on-premise since, once it is installed on one of my machines, I can keep using the same setup again and again. It's easy to understand once you have done it. 

I'd rate the installation process a six out of ten in terms of ease of deployment. For the most part, it is just a step-by-step installation. 

There is no specific maintenance needed as such. That said, when there is a version upgrade, then there are certainly some challenges due to the fact that the technology is legacy now and, of course, the turnaround time is longer. If we run into any challenges, then the turnaround time to resolve issues is also more since the technology is older. 

I can't speak to the exact pricing. I don't have information about licensing. 

I'm a partner. I'm working with the Windows-based version of the solution. 

We are starting to launch these products on AWS, and that likely will make everything easier in the future (as opposed to on-premises deployments).

I'd rate the solution an eight out of ten. It needs a bit better usability. However, the security is good.