Hyland OnBase vs ServiceNow Orchestration comparison

"The product's initial setup phase is not difficult."

"Its most valuable aspect is its flexibility"

"I like the cloud and its integrability."

"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."

"The solution's most valuable features are integration and flexibility."

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

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

"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 interface of the solution is very user friendly and it is easily accessible via a simple URL. This makes it easier to complete the UI based tasks but using other features require expertise in languages like Java. But along with that, there are limitation in terms of network connectivity testing and administrator faces regular challenges in conducting connectivity tests due to these limitations."

"Employee onboarding, de-boarding, and other service-provision features make the process easier and it saves us a lot of time."

"The iTerm suite is also crucial for visibility and optimization."

"It's probably the best product out there."

"Orchestration is commonly utilized by major corporations. The process of linking methods in ServiceNow, known as the RTS chain to parent methods, is executed seamlessly and efficiently. It's quite impressive and significant in its impact."

"The data visualization is good."

"It has competitive AI capabilities."

"It's scalable."

"We need to troubleshoot why our reports didn't get downloaded in a day. There is a workflow feature which powerful but also complicated."

"An area for improvement would be the training - getting our people up to speed on how to use it required more training than we expected due to the complexity of the solution."

"The migration is a bit difficult in the tool."

"For user experience, they would have to do more with the interface. It is not easy to work with and is a little messy. It is getting better, but it is not yet good enough. Other products are comparatively doing better in terms of the user interface. I have been hearing about Box, which is very easy to use and learn for the users. OnBase has to work on this aspect. It should have BPM capabilities. We compete with tools that provide the BPM feature and support those standards. They can do better in terms of the pricing model. It is a really expensive tool in Latin America. They should have different prices for different regions."

"The application could potentially be more open-source, allowing integration with more solutions."

"The solution’s initial setup is a little difficult."

"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 dashboards do have some room for improvement as compared to the other vendors which are there in the market."

"The automatic remediation needs enhancement, particularly integrating ServiceNow with tools like SolarWinds and Logic Monitor. It is functional, but it needs improvement."

"There is still room for more integrations. Or, it would be nice to bundle multiple products together rather than selling everything as a model as that turns out to be a bit costly."

"I would like a user experience module to be added."

"The flow rate for releases and updates is very, very slow and does not meet customers' objectives for scalability."

"There should be connectors to cover at least the top industry applications, and they should be easier to configure in a plug-and-play fashion."

"We cannot perform GUI automation using the tool."

"From my space, the only thing that I can say is the spinning up with Google Cloud Services."

"Frequent upgrades may negatively impact the performance of instances. Therefore, for now, I don't recommend any additional upgrades."

"They can do better in terms of the pricing model. It is a really expensive tool in Latin America. They should have different prices for different regions."

"There are a number of different types of licenses. There are concurrent licenses, individual licenses and imaging licenses."

"The tool's price is high."

"The solution costs around $6,000 per month."

"OnBase is reasonably priced."

"The cost of the solution is based on the number of plugins, conductors and integrations used and is charged annually. The licensing cause has been increasing gradually which makes it difficult to access. Initially offer free features but over the time the charges rise which make it an expensive solution with limited features. Along with that, the integration issues persist and require additional middle where and internet connectivity for effective usage."

"Pricing is custom to every customer."

"The solution is costly and orchestrations are very expensive."

"ServiceNow doesn't give a clear cost indication. They have different contracts with different organizations and it's all about negotiation, so you don't know how they are doing at the cost level."

"It is not very expensive."

"In terms of price, this solution is at the higher end of what you'll find."

"This is an expensive product, but it is the best in the market considering the features and lack of competitors."

"It is quite expensive because we've had some customers come back and say it's quite pricey because in order for them to go ahead with Orchestration, they must have already been paying for Discovery, service mapping, and a few other things."