Embedding sub-process workflows
The sub-process element is used to enhance process readability by logically grouping certain steps and present the user with high level steps. The element contains other activities, gateways, events, and so on which form a process that is part of another process. It enables you to collapse the process steps and treat them as a single element.
A Sub-Process can only be used inside a parent process. It cannot be invoked by another process by using a Call Activity. A process that is defined in a Sub-Process element is not reusable, that is, other processes cannot call this process through the Call Activity element.
The following illustration shows an example of embedded sub-process workflow.
Before you begin
Start to create the workflow, as described in Designing-a-simple-workflow.
To create a sub-process workflow
- Drag the Sub Process element onto the canvas.
- Double-click the Sub Process element to open it. Drag to expand the element further if you need more room.
The Start and End elements are already provided. - Drag elements to design the subprocess.
- Double-click to collapse the subprocess, so you can move the subprocess as a single activity.
When a Sub Process element is moved anywhere on the canvas, the subprocess it contains moves with it, even if the element is open. - Draw sequence flows from other elements to add one input to and one output from the Sub Process element.
- (Optional) Map input parameters to the subprocess if any of the elements it contains require inputs.
Required licensing
SaaS subscribers who use BMC Helix ITSM or BMC-Helix-Virtual-Agent-Basic-service are entitled to this feature.
Where to go from here
Complete remaining aspects of the workflow, as described in Workflows-for-service-fulfillment.