---
title: "Sub-Process Node"
slug: "sub-process-node"
description: "Learn how to configure a Sub-Process node in your workflow for non-linear task navigation, enhancing user experience with flexible task management."
updated: 2025-12-01T20:08:39Z
published: 2025-12-01T20:08:39Z
canonical: "docs.unqork.io/sub-process-node"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.unqork.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Sub-Process Node

![A static image displaying the Sub-Process node on the Workflow canvas.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/image-1763568208412.png?sv=2026-02-06&spr=https&st=2026-10-26T09%3A54%3A04Z&se=2026-10-26T10%3A54%3A04Z&sr=c&sp=r&sig=nAbUz%2Bf3Wa1zRWZYrNeNleic3p7bHFDTHF05r%2F%2BdEjE%3D)The **Sub-Process node** acts as a container for [Task](/v1/docs/task-node) nodes in a [workflow](/v1/docs/introduction-to-workflow). While a workflow's navigation is linear, a Sub-Process node offers a non-linear flow to tasks in a workflow. In a Sub-Process, your end-user can complete their tasks in any order and freely navigate between them. The Sub-Process node must have two Task nodes to work correctly.

Sub-Process nodes also support the [Conditional Event](/v1/docs/conditional-event-node) node. You can use logic to take your end-user to different parts of your workflow based on their data. Only Task and Conditional Event nodes can be placed in a Sub-Process node.

You'll find the Sub-Process node in the list of nodes to the left of the [Workflow Builder](/v1/docs/introduction-to-workflow).

## Settings Menu Description

Let's explore the node's **Settings Menu**. This menu displays as a blue menu bar, either above or below the node, when you select the node itself. This node has these Settings Menu options:

| **Setting** | Description |
| --- | --- |
| Edit | Takes you to the Edit Sub-Process window, where you can configure related settings. |
| Delete | Removes the Sub-Process, related tasks, and Conditional Events from the workflow. |
| +/- button | Expands (+) or collapses (-) the Sub-Process node. By default, the node shows as expanded when you first add it to the pool. Don't worry about the large footprint of this node. After you've added it, clicking collapse (-) minimizes the node and hides the contents. |

### Edit Sub-Process Window Description

Click the **Edit** button to display the **Edit Sub-Process** window.

The following settings are available in the Edit Sub-Process window:![A static image displaying the End node on the workflow canvas, and the End node's confiugration panel with default settings.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Sub_Process_Node_description.jpg?sv=2026-02-06&spr=https&st=2026-10-26T09%3A54%3A04Z&se=2026-10-26T10%3A54%3A04Z&sr=c&sp=r&sig=nAbUz%2Bf3Wa1zRWZYrNeNleic3p7bHFDTHF05r%2F%2BdEjE%3D)

| **Setting** | Description |
| --- | --- |
| Label | Sets the name of your node. By default, the Label displays as `subprocess-1.` This label is optional. As a best practice, you should define labels by associating them with the role of the node. |
| Allow Navigation With Errors | When set to ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/toggle_ON(6).png?sv=2026-02-06&spr=https&st=2026-10-26T09%3A54%3A04Z&se=2026-10-26T10%3A54%3A04Z&sr=c&sp=r&sig=nAbUz%2Bf3Wa1zRWZYrNeNleic3p7bHFDTHF05r%2F%2BdEjE%3D) **(ON)**, your end-user can navigate to the next node without validating data on the current node. By default, this toggle is set to ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/toggle_OFF(6).png?sv=2026-02-06&spr=https&st=2026-10-26T09%3A54%3A04Z&se=2026-10-26T10%3A54%3A04Z&sr=c&sp=r&sig=nAbUz%2Bf3Wa1zRWZYrNeNleic3p7bHFDTHF05r%2F%2BdEjE%3D) **(OFF)**. |
| Validate When Leaving Group | When set to ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/toggle_ON(6).png?sv=2026-02-06&spr=https&st=2026-10-26T09%3A54%3A04Z&se=2026-10-26T10%3A54%3A04Z&sr=c&sp=r&sig=nAbUz%2Bf3Wa1zRWZYrNeNleic3p7bHFDTHF05r%2F%2BdEjE%3D) **(ON)**, your end-user can navigate through the current group of tasks in the Sub-Process. Data is only validated when the workflow reaches a node outside of the Sub-Process node. By default, this toggle is set to ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/toggle_OFF(6).png?sv=2026-02-06&spr=https&st=2026-10-26T09%3A54%3A04Z&se=2026-10-26T10%3A54%3A04Z&sr=c&sp=r&sig=nAbUz%2Bf3Wa1zRWZYrNeNleic3p7bHFDTHF05r%2F%2BdEjE%3D) **(OFF)**. |
| Close | Closes the Edit Sub-Process window, returning your focus to the pool. |

## Adding a Sub-Process Node

Set up a simple workflow that includes a [Start](/v1/docs/start-node) node, a Sub-Process node, three [Task](/v1/docs/task-node) nodes, and an [End](/v1/docs/end-node) node. For this example, your workflow guides end-users through a series of Sub-Process tasks. These Sub-Process tasks confirm the end-user's registration for Renters or Homeowners insurance.

> These instructions assume you set up your module and have a new workflow ready.

### Configure the Sub-Process Node

To add a Sub-Process node to your workflow:

1. Drag and drop a **Sub-Process** node in the **Authenticated** lane.
2. Connect the output port (right) of the **Start** node to the input port (left) of the **Sub-Process** node.

### Configure the Task Nodes

Add three Task nodes into the Sub-Process node.

1. Drag and drop three **Task** nodes inside the Sub-Process node.
2. For each **Task** node, click **Edit** and set the **Label** and **Module** settings as follows:

| **Label** | Module |
| --- | --- |
| Step 1 | Enablement Lab: Step 1 - Registration Info |
| Step 2 | Enablement Lab: Step 2 - Insurance Type |
| Step 3 | Enablement Lab: Step 3 - Confirmation |
3. Click **X** (Close).

> Task nodes in a Sub-Process act as though they are connected. There is no need to connect these nodes individually.

### Configure the End Node

1. Drag and drop an **End** node in the **Authenticated** swimlane.
2. Click **Edit****.**
3. In the **Label** field, enter `End`.
4. Click **X** (Close).
5. Connect the output port (right) of the **Sub-Process** node to the input port (left) of the **End** node.
6. Click **Save...**.
7. Click **Save**.

Your workflow looks like the following when complete:

[![A static image displaying a completed workflow using a Sub-Process node in the Workflow Builder.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Sub_Process_Node_example_complete_thumb_0_0.jpg?sv=2026-02-06&spr=https&st=2026-10-26T09%3A54%3A04Z&se=2026-10-26T10%3A54%3A04Z&sr=c&sp=r&sig=nAbUz%2Bf3Wa1zRWZYrNeNleic3p7bHFDTHF05r%2F%2BdEjE%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Sub%20Process%20Node%20example%20complete.jpg?sv=2026-02-06&spr=https&st=2026-10-26T09%3A54%3A04Z&se=2026-10-26T10%3A54%3A04Z&sr=c&sp=r&sig=nAbUz%2Bf3Wa1zRWZYrNeNleic3p7bHFDTHF05r%2F%2BdEjE%3D)

End-users, also known as Express Users, are the individuals accessing an application through Express View. In most cases, end-users are the customers using the product.

End-users, also known as Express Users, are the individuals accessing an application through Express View. In most cases, end-users are the customers using the product.