If you have been using OnBase Workflow timers for some time, you may be familiar with the original Classic based options for scheduling timers to run from an open client or a Windows service. Next came the much lauded core based Workflow Timer Service which allowed multi-threaded processing. It can’t get much better than that, right? So, why would Hyland introduce yet another core-based timer service in version 16?
Nov 14, 2016
What's New in OnBase