The Fork operator passes its input to two or three blocks downstream.
It's useful when designing a parallel portion of the workflow where you need to process the same information with different models.
The use of the Fork operator is not mandatory, because it is also possible to directly connect a block to two or three downstream blocks. However, using this operator makes the diagram more readable and tidy. If Fork is used, when you need to join the outputs of multiple blocks it is suggested you use a Join block for symmetry.
A Fork block must have one input connection and two or three output connections to other blocks to be considered valid.
It can be the first block of the workflow.
The output of a Fork block is the exact replica of its input.
Block properties can be set by editing the block.
A Fork operator block has these properties:
- The unique block ID and the service version, displayed in the title bar (read only, displayed also in the block tooltip in the canvas).
- Block name