Workflow typically represents some of the most critical functionality for the business. Significant risk reduction for these critical processes can be achieved in an Incremental Parallel Upgrade.
OnBase Workflow previously had two underlying approaches to deployment: Classic and Core-based. Both the Classic and Core-based deployment models allow for the offloading of processing effort to back-end servers. The Classic path leverages the processing power of the local workstation to perform client-side processing, while the Core-based leverages the OnBase Application Server(s) for server-side processing. As of version 7.2 of OnBase, the Classic Workflow model was deprecated, and the Core-based model is the implementation going forward. Workflow configuration is now performed in OnBase Studio.
Also in versions 7.2 and higher of the software, Workflow Timers can be processed in a Windows-based service running on a server that has the Core installed, instead of in an instance of the Classic Client. The Workflow Timer Service can process more than one timer concurrently and takes advantage of additional processor cores. Timer work performed on the upgraded software should be performed on an upgraded timer server.
When transitioning Workflow Timer processing and/or Classic to Core-based Workflow, for better risk management, do not change these during an upgrade. Transition them in a later phase or with another project. It is important to understand and document what solutions have been deployed, what third party applications interact with those solutions, and if there is any custom code that needs to be updated, including simple scripts attached to Workflow actions, script hooks, or embedded into E-Forms. Challenges in upgrades (for all enterprise-based applications) are often traced back to a piece of forgotten custom code.
When planning an incremental Workflow upgrade, consider using an approach of targeting specific workflows that only specific groups of users access. This allows the initial upgrade, training, and support efforts to be limited in scope. If upgrading Core-based workflows in parallel, new OnBase Application and/or Web Servers will need to be deployed with the proper version clients pointing to the correct server versions.
Take care to ensure that the versions of OnBase Clients configured to use Application Servers are on matching versions. OnBase users performing Core-based Workflow activities in the Web or Unity Clients natively connect to the proper Application Server.
It is advised not to ingest or purge documents using legacy software during an IPUP.
In OnBase 14 and later, Core-based Workflow is configured in the OnBase Studio application.