Subprocesses

Subprocesses enable quick re-use of Models, by dragging and dropping them to the canvas and incorporating them in a new Model. This is particularly useful for common and recurring functionality, which can be modelled once and then re-used wherever it occurs in a system.

To embed a Model as a subprocess in another model, drag the Subprocess action to the canvas, dropping it where the subprocess will be placed. Next, select the Model to be imported. Models are displayed within their relevant project and release, and are sorted by version:

The Model will be added to the canvas as a collapsed block:

Click the “plus” button to expand the subprocess box. Next, use Arrows to connect the Start and End points of the subprocess into the existing Model.

Actions from the master model can be connected to the Start and End points of the subprocess. The Start and End points of the Subprocess can equally connect to any action in the existing model.

The Start and End points serve as the inputs and outputs of the subprocess, incorporating its logic into the master model. Looping is not possible, meaning that an End point of a Subprocess cannot be connected to the block in the master model from which that same subprocess is connected.

If a model is being used as a subprocess in another model, and its start and end points are removed, this will create a break in the logic of the master flow. The following warning is therefore displayed when a start or end point in an model used as a subprocess elsewhere is removed:

All Subprocesses in a given model can be expanded and collapsed simultaneously, using the “Expand” and “Collapse” option in the Format tab of the Model Editor.