Blocks are containers for related actions or decisions that happen within a stage. They typically represent a sub-process that delivers a specific outcome—like submitting a request, approving it, or handling an exception.
| Property | Purpose |
|---|---|
Name | The name of the block that will appear on the process builder screen. |
Description | Helpful description as to what is the purpose of the block. |
Execution Flow | Option of 3:
See below notes. |
Default path | |
Next block | Points to the block that will be executed once the current block is complete. |
Alternative paths | You can create multiple alternative paths that will direct the flow to other blocks if the condition is met. |
Path name | Specify in a word or more what this path represents. For example, rejection, cancellation. Review etc… |
Alternative next block | Defines the block to begin when the current one finishes. |
Condition | Specify the condition at which the block should run. An alternative block can only be triggered when the condition is met. |
Block Flow Types
Block Flow Type | Description | Example |
|---|---|---|
Sequential | Steps run one after another, in a fixed order. Each step must complete before the next begins. | Employee onboarding: Submit documents → Manager review → HR approval. |
Parallel | All steps start at the same time (if assigned). Ideal for tasks distributed across teams. | Employee onboarding: IT sets up laptop while Facilities prepares desk access — both at once. |
Switch | Only one path runs, based on data or user input. Used for conditional branching. | Employee onboarding: If hire is remote, skip building access and send remote welcome pack instead. |
Block Alternative Paths
When you add an alternative path you will notice a number near the drop down arrow that represents the Next block. See below where there are 4 alternative paths. When you click on that icon the system highlights the actual bocks that are the alternative paths.
A block can be removed by clicking on the “Delete parent block” button.
