Subprocess node

Use the subprocess node to execute one entitlement workflow from another. Subprocesses simplify the workflow by using one node to represent a previously defined workflow sequence. The Subprocess node is not available in Operation workflows. Subprocess nodes are typically used for the following reasons:

Organization

Workflows can become complicated when there are many parallel branches that must run. Placing large blocks of processing into a subprocess can sometimes help.

Reusability

Subprocess workflows that define generic processing can be included in multiple workflows.

A subprocess can use any predefined entitlement workflow of the same service type or global workflows. However, the workflow must be located within the same organization.

We must map the parameters required by the child workflow to relevant data items in the parent workflow. The subprocess node provides the set of input and output parameters for the Subprocess. While the parameter names and types are fixed by the subprocess node, we can configure the value of each parameter.

The Activity ID and the Subprocess property are the only required properties for the subprocess node.

Parent topic: Workflow elements