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?

This content is for subscribers. Please enter the password to access it.

  • This field is for validation purposes and should be left unchanged.
About Jennifer

Jennifer (aka Pixie) has over 30 years of experience in the Information Technology field, which includes 13+ years of Systems Administration, 16+ years of developing and implementing technical documentation and training, and 14+ years of supporting OnBase. She has extensive experience with OnBase, SQL, and a firm foundation in computer science. Despite this, she considers herself a well-adjusted nerd with hobbies including gardening (poorly), archery, and knitting in public.