OR Split Task

An OR Split Task is like the Decision Task, but it allows you to create multiple conditions and decision paths since it is not just limited to a yes or no answer.

The following table details the OR-Split Task functionality.

Progression Task	OR Split Task Description
	The OR Split task allows the designer to specify many conditions and paths for the work item. The first matching decision-condition applied to the work item determines the workflow path that will be followed. For example after indexing, where an invoice had its account information and invoice amount entered before it entered workflow, an OR Split Task is used to enforce business policy on “Invoice Processing” which could specify different workflow paths depending whether this invoice: • Amount is within the amount covered by the supplied PO number index, • Should have a PO number index value assigned before resuming processing • Should be processed as a non-PO invoice along a different path. • Should follow which path based on different invoice-amount ranges. • Should follow a default path with no condition specified (always True) as the last condition evaluated. The first condition in the OR Split Task that matches the work item’s index state becomes the path for the current work item.

Progression Task

OR Split Task Description

The OR Split task allows the designer to specify many conditions and paths for the work item. The first matching decision-condition applied to the work item determines the workflow path that will be followed.

For example after indexing, where an invoice had its account information and invoice amount entered before it entered workflow, an OR Split Task is used to enforce business policy on “Invoice Processing” which could specify different workflow paths depending whether this invoice:

• Amount is within the amount covered by the supplied PO number index,

• Should have a PO number index value assigned before resuming processing

• Should be processed as a non-PO invoice along a different path.

• Should follow which path based on different invoice-amount ranges.

• Should follow a default path with no condition specified (always True) as the last condition evaluated.

The first condition in the OR Split Task that matches the work item’s index state becomes the path for the current work item.

The tabs for multiple types of tasks that the OR Split Task has in common with other tasks are listed with x-marks in the grid (above) and they are explained in detail in a previous section (Task Definition – Common Tabs