Subprocess development

The Process Editor is the same as normal Processes, with the exception that you can only have a Manual Trigger, since Subprocesses can only be executed by calling them from other Processes. In addition, you can only have one Trigger instead of having multiple Triggers with different parameters. The Return Element lets you define what will be returned to the calling Process.

From the Manual Trigger, you can define the parameters of the Subprocess. These parameters are passed from the calling Process to the Subprocess. You can add as many parameters as you need. You can define key, default value, as well as a description for the parameter. In addition, you can set the parameter as a secret if you don’t want that parameter to be logged. This is useful if you want to pass secrets, such as credentials, to the Subprocess. You can also choose to not log any of the parameters by turning the “Do not log trigger parameters” option on.

The Key of the parameters determine which variable the data, provided by the calling Process, is stored in. You can access the data using the reference #trigger.data.

After you are finished with editing the Subprocess, you can save the Subprocess as you would normally save Processes. When the Subprocess is finished, you can deploy the Subprocess to any Environment you want. The Subprocess is run in the same Agent Group as the calling Process, so the Subprocess first needs to be deployed to the same Agent Group as the calling Process before it can be used. If you have multiple Agent Groups in the same Environment, it is possible to select which Agent Group the Subprocess is executed in by using a remote Subprocess, but we will talk about that later.

The next article is Introduction to Using Subprocesses in other Processes