OnBase - it stores your docs
February 01, 2018
OnBase - it stores your docs
Score 7 out of 10
Vetted Review
Verified User
Overall Satisfaction with OnBase by Hyland
OnBase is being used by our entire organization. The primary purpose is for document storage. However, a good chunk of its use is also for workflow functionalities. For example, a document comes in of a certain type, someone looks at it and pushes a button, it goes to another person who pushes another button which moves it out of the workflow area.
- Document storage
- BASIC workflow activities
- BASIC forms for users to fill out/use
- Documentation - If you want basic functionality they do a pretty good job in detailing out an overview of aspects. However, when you get into the technical aspects of their documentation it falls flat. There were many instances where I didn't understand how an aspect would behave and had to call them in order to get the answer. Many times they even had to go directly to a developer in order to get my answers.
- Support - They try to push their clients to use third parties instead of working directly with them. Third parties are great for BASIC troubleshooting, and possibly could be used for training basic administrative functions. However, over time you grow in your OnBase knowledge and calls go something like this: Call support. Explain your situation. They are unsure. You try to convince them to call Hyland. They continue to research. You ask again to call Hyland. They finally do. Explain your situation all over again.
- Functionality - OnBase really tries to push you down a road that they want you to go. What I mean is that they offer a few different ways to access the OnBase data. A few years ago they came up with a new client (Unity) and really....really try to get customers to move to that. This means that other clients become an afterthought, even though that is the primary way your business may interact with OnBase. On one hand this may be okay, however, they also charge you to use this client they are pushing per server, and per client.
- The ROI can be seen by the basic workflow. You no longer have to ask "What status is X document in?"
- You can also realize ROI by replacing paper and space for paper with electronic means.
- The downside is that OnBase requires at least 1 full-time person to manage it.
We went with OnBase because other organizations we work with use it, so we wanted to use something similar. Also, other solutions are way more expensive.