End Node

To end a process, simply drag the End Node from the Nodes Pane to the Design Canvas and connect one or more other Nodes to it.

Open

Configuration

1. Provide a meaningful title. A descriptive title can help administrators understand where in the workflow the End Node was hit. Named End Nodes can be very helpful when building / testing / debugging new workflows.

2. Optionally select the Delete Process option to Delete the process and it’s associated document data when this node is hit.

   1. Delete completed process to keep your process database well maintained. Pruning process data no longer needed can keep your environment running with optimal performance. Smaller process collections are also easier for admins to work with.

   2. Delete processes that are extraneous. Some workflow process may create “dead” processes. For example, a scenario where a coversheet is used for indexing, then separated and split into a new process that is discarded. Unnecessary processes can be discarded in the workflow, minimizing and confusion downstream about processes in a batch that are necessary.

3. Optionally select the Process Portal to move completed processes to. Moving completed processes can help both administrators and end users by removing completed processes from searches that represent active work. Admins can create additional searches for future access to historical data migrated out of the active work queue.

Usage

Before publishing a GlobalCapture Workflow, it must include at least one End Node. While you can save incomplete workflows, the GlobalCapture designer prevents you from putting them into production.  You can connect the Nodes in your process to a single End Node, or use multiple End Nodes if it's more convenient. When designing large or complex Workflows with conditional logic, there may be multiple endpoints and it can be easier to simply end a process at each stopping point rather than drawing connections spanning large portions of the design canvas.