Skip to main content

Overview

The Start Embedded Subprocess node enables the initiation of subprocesses within a parent process, offering a range of features and options for enhanced functionality.
Start Embedded Subprocess node on the process canvas
Call activity or embedded subprocess? On the process canvas, both nodes are rounded rectangles with a box-and-plus icon. A call activity node has a thicker border and a bolder icon. A start embedded subprocess node has the same thin border as other task nodes. In the node palette, they are named Call Activity and Start Embedded Subprocess. To decide which one a phase needs, see Call Activity or embedded subprocess.

Usage Considerations

Data Management

Embedded subprocesses offer advantages such as:
  • Segregated sections from a subprocess can be utilized without rendering them over the parent process.
  • Data is stored within the parent process instance, eliminating the need for data transfer.
  • Embedded subprocesses are visible in the navigation view.

Runtime Considerations

Important runtime considerations for embedded subprocesses include:
  • The child process must have only one swimlane.
  • Runtime swimlane permissions are inherited from the parent.
  • Certain boundary events are supported on Start Embedded Subprocess node, except for Timer events (currently not implemented).
Embedded subprocesses cannot support multiple swimlanes in the actual implementation.

Example

Let’s explore this scenario: Imagine you’re creating a process that involves a series of steps, each akin to a sequential movement of a stepper. Now, among these steps, rather than configuring one step from scratch, you can integrate a pre-existing process, treating it as a self-contained unit within the overarching process.

Step 1: Design the Embedded Subprocess

1

Access FlowX.AI Designer

Log in to the FlowX.AI Designer where you create and manage process flows.
2

Create a New Process

Start by creating a new process or selecting an existing process where you want to embed the subprocess.
3

Navigation Areas

Design your navigation areas to match your needs.
Navigation view of a parent process: a stepper with three steps, the Start Embedded Subprocess node assigned to the Offer review step
Make sure you allocated all your user tasks into the navigation area accordingly.
4

Design Subprocess

Within the selected process, design the subprocess by adding necessary tasks, events and so on. Ensure that the subprocess is contained within a single swimlane.
A process to embed, with a single swimlane named Default
To initiate a process with an embedded subprocess, designate the root Navigation Area of the subprocess as an inheritance placeholder Parent Process Area label in the Navigation Areas. Ensure that the navigation hierarchy within the Parent Process Area can be displayed beneath the parent navigation area within the main process interface.
Navigation view of the process to embed: its user task sits under a Parent Process area
Make sure you allocated all your user tasks into the navigation area accordingly.

Step 2: Configure Start Embedded Subprocess Node

1

Add Start Embedded Subprocess Node

Within the parent process, add a Start Embedded Subprocess Node from the node palette to initiate the embedded subprocess.
Process Nodes palette with the Start Embedded Subprocess and Call Activity nodes
2

Specify Subprocess

Select the node and open Node details. In the Node Config tab, under General Config, enter a Node name, optionally choose a Process Stage, and select the process to embed from the dropdown below them. Processes from the current project are listed under Local. The icon next to the dropdown opens the selected process in a new tab. Click Save.
Node Config tab of a Start Embedded Subprocess node with Node name, Process Stage and the selected process

Step 3: Customize Subprocess Behavior

Alternative flows configured in the main process will also be applied to embedded subprocesses if they share the same name.
1

Customize Data Handling

Within the subprocess, handle data as needed. Remember that data is stored within the parent process instance when using embedded subprocesses.
2

Implement Boundary Events

Implement boundary events within the subprocess if specific actions need to be triggered based on certain conditions.
Running parent process: the embedded subprocess's screen renders as step 2 of the parent's stepper

Step 4: Test Integration

1

Test Functionality

Test the integration of the embedded subprocess within the parent process. Ensure that the subprocess initiates correctly and interacts with the parent process as expected.
2

Verify Data Flow

Verify that data flows correctly between the parent process and the embedded subprocess. Check if any results produced by the subprocess are correctly captured by the parent process.
Parent process with a Start Embedded Subprocess node between two Call Activity nodes
For further details on other ways of configuring and utilizing subprocesses, refer to the following resources:

Subprocess Configuration

Start Subprocess action

Process design principles

Subprocess lifecycle, Call Activity vs. User Task action, async constraints.
Last modified on November 5, 2026