<< Click to Display Table of Contents >> Navigation:  Modules > Workflow Automation > Decision Trees > Nodes > Invoking Workflow

At each node of the Decision Tree, the very first action that may be performed is to invoke a workflow.  The thought is that the previous node resulted in an outcome that now requires some sort of attempt to gather information, notify, or possibly even automatically remediate.  Therefore, the workflow is envisioned as being used to act on the results of a previous test or condition.

Once the workflow acts, then the condition and/or test of the current node can proceed.  This is especially true if the workflow is designed to somehow result in the remediation of the issue detected in the upstream testing.  The condition and/or test of the current node might be to check to make sure the issue was indeed remediated before proceeding with further testing.

Therefore, whenever a workflow is specified to be fired by a node, the processing of the tree will be suspended until the workflow completes.  If multiple workflow threads are created (due to a record set from a previous test being used), then all threads must complete before the tree will begin processing again.  Processing of the tree will be suspended until either all the outstanding workflow threads have completed, or the timeout is reached.

Workflows that contain Process, then Decision process points will necessarily not complete while the tree is being processed.  Such workflows will cause processing of the tree to be suspended.  Workflows that contain only Process, then Forward decision points will complete while the tree is being processed, allowing the processing of the tree to continue.