Ad-Hoc workflow is a user-driven process and is dependent on the user’s ability to correctly assign the index values for the process Status Index Field at the end of their task in order for the work move to the next task in the process.
With Ad-Hoc workflow, there is no process enforcement and no business rules that automatically test for the conditions that determine what actions should be taken.
For example, a business rule might define: “If the amount is greater than $1000 then send it to a manager for approval; otherwise the current operator is allowed to continue processing it”. Ad-Hoc workflow is driven by user knowledge and action and does not process or enforce business rules. The user must know the rules and adhere to them.
For instance in this example: The Ad-Hoc workflow user must either know or consult a policy table to determine the proper next ‘Assign To’ and/or Status value to allow the current item to be located by an appropriate worker and processed properly as the next step in the item’s processing.
Furthermore at the next step when one or many related documents for the item will be also needed for its processing, the Ad-Hoc workflow user must know how to process the item (i.e., its procedures for this step) as well as what related documents must be located and used.
Basic Ad-Hoc workflow is available with the base DocuPhase product capabilities.