> For the complete documentation index, see [llms.txt](https://docs.work-relay.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.work-relay.com/processes/process-actions/process-actions-types/start-subprocess.md).

# Start Subprocess

### Generic Process Action properties

This action has generic properties, as other process actions:

* **Name** - give action a name in order to search for it easy, otherwise system will use ID of this Action.
* **Step** - the step action is added at. This property can't be edited manually, but it will be updated if move this action to other step or connector.
* **Type** - main property which determines what Action will do and it's configuration. Once action is created, type can't be changed.
* **Status** - you can activate or deactivate an action temporary (e.g., for debug).
* **Start Type** - can be set to "Before step" or "After step". 

{% hint style="info" %}
This option is available only when action is added to the step. If action is added to a connector, it will be executed like "After step", where step is the outgoing step of this connector.
{% endhint %}

* **Execute** - specify if Action will be executed always or when some conditions are matched.
* **Description** - used internally only for admin's goals.

### Configuration:

* Provide other Subprocess settings:\
  \
  **Version -** user can select specific process version.\
  **Lock Parent -** the parent step will not proceed until this sub-flow is complete.\
  **Restart Process -** the system will restart the sub process if it was started before.\
  **Inherit variables -** user can use variables set in parent flow inside the sub flow.

<figure><img src="/files/bsMSNQry6PHe2o5R28RT" alt=""><figcaption></figcaption></figure>

* Provide at least one **condition** to search the records to begin the workflow.

<figure><img src="/files/krGWrqedMmhthlDng5On" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
If user configures Subprocess on the same Data Source object, the following condition will be added automatically:

**Name** = name of the field that determines unique record, usually it is "ID" or "Record ID"\
**Operator** = "equals"\
**Value** = merge field calling the field that determines unique record
{% endhint %}