Performing Sub Functions Using Function Call Life Cycles - Workflow - English - Foundation 22.1 - OnBase - Premier - external - Standard - Premier - Standard

Workflow

Platform
OnBase
Product
Workflow
Release
Foundation 22.1
License
Premier
Standard

One use for function call life cycles is to provide additional functionality. If there is a set of rules and actions that needs to be performed in a variety of different locations within one or more life cycles, using a function call life cycle keeps the code segmented, to make it easy to follow and to maintain. A function call life cycle treats these documents as primary documents, meaning actions execute quicker. A simple function call life cycle consists of one queue with the logic configured as System Work. Upon completion of the System Work, the document is removed from the life cycle. Function calls can be utilized in this capacity to provide for uninterrupted user activity. If a document cannot be processed further due to missing information, a Workflow user can route that document to a function call life cycle. Users assigned to this secondary life cycle can address the issue(s) surrounding the document and funnel it back to the main life cycle to continue processing.