To join building block components within a task path workflow

The procedure to join building block components within a task path workflow is as follows:

1. Prerequisite procedural steps are covered separately in the topic To configure the workflow structure of a task path definition. Refer to these before proceeding to step 2.
2. With the Path tab activated, use the Version drop-down field to ensure that the correct variant of the task path workflow structure is displayed.
3. Within the design area, highlight the relevant building block component for which inter-related workflow connections will be established. The connection node icon () is overlaid onto the building block.
4. Using the standard 'drag and drop' technique, click on an available connection node and project it onto a desired target building block 1. A connection (join) is established between the two components and the arrow direction indicates the workflow hierarchy 2.
5. Where the source node originates from a Decision building block, the Join Condition window is displayed, ready to select the custom criteria used to channel the workflow down this particular path: (a) Using the Join condition drop-down field, multi-select all valid outcome checks for this task path branch, or choose the All option, as required 1; (b) Click on Confirm - A connection (join) is established from the Decision building block.
6. Repeat steps 3 and 5 to establish further building block connections within the task path workflow structure 3.
7. Click on Save.

Tip

1 Where only a small number of parameter values are not required, activate the All tick box first and then deselect individual items from the full list, as appropriate; the All tick box will be automatically removed once an item is deselected.

Note

1 By definition, an automatic completion building block is an endpoint for a task path workflow and therefore cannot be configured as a predecessor of a subsequent component.

2 System validation rules ensure that the integrity of connections between mandatory and optional building blocks is upheld i.e. an optional building block cannot be established as a predecessor of a mandatory building block; similarly, where the commencement of a building block component is steered by the attribute Link start date to void date, task-oriented workflow rules dictate that it cannot be nominated as a predecessor of another building block within the overall structure.

3 Only a single connection can be established between the same two building blocks.

See related topics...

Understanding the task path creator

To configure the workflow structure of a task path definition

To remove a building block connection from a task path workflow