Unqork documentation is available in two workspaces: UnqorkAI for the latest AI-first platform, and legacy Unqork for previous versions. Use the drop-down near the logo to switch.

Sub-Process Node

Prev Next

The Sub-Process node groups a set of nodes into a collapsible, reusable container in the workflow canvas. It can be placed in the Authenticated swimlane. Use it to organize complex workflows into logical sections and to define role-based swimlanes for access control.

Add a node to it by dragging a Task node onto the Sub-Process node — the container grows to hold it, and the task takes on the sub-process's swimlane and task type. Drag a nested task back a swimlane to remove it from the container.

How to read settings tables

The tables below describe each configurable option as it displays in the UnqorkAI platform. Values are formatted as follows: inline code — a value to type exactly as shown | Bold — a value selected from a drop-down, radio button, tab, or choice chip | ON/OFF — toggle state | ✓ — checkbox checked | ☐ — checkbox unchecked

Settings

Setting Field Type Default Description
Label label Text input subprocess-{n} A display name for the node. Supports template expressions (for example, subprocess-{{ data.number }}).
Allow Navigation with Errors allowNavigationWithErrors Toggle OFF When set to ON, this setting lets end-users navigate forward even when validation errors are present.
Validate When Leaving Sub-Process validateOnLeavingGroup Toggle OFF When set to ON, this setting validates all fields when an end-user exits the subprocess.

Placement Constraints

  • The Sub-Process node can be placed in the Authenticated swimlane. It cannot be placed in an Automated swimlane.
  • Only Task nodes can be nested inside a Sub-Process node. A Sub-Process node cannot contain another Sub-Process node.
  • Any links already connected to a task are removed when you drag it into a Sub-Process node. Nested tasks run in left-to-right order inside the container, so their sequence comes from their position rather than from links you draw.
  • A task carrying a boundary event — an Error, Timed Event, or Conditional Event node — is refused. Remove the attached event first, then drag the task in.

Changelog

Date Change
— Initial publication.