Execution

When the incoming flow is activated, the [Sub-process] element activates the [Simple] start event of the process specified in the [Which process to run?] field.

As a result, the actual version of the sub-process is launched as a new independent process instance.

If any of the incoming and bi-directional process parameters are populated in the [Process parameters] block of the [Sub-process] element, the sub-process will run with those parameter values.

If you save another version of the sub-process as “actual” after the [Sub-process] element has been launched, the element will continue executing the version that was actual at the time of the [Sub-process] element activation. The new sub-process version will be used on the new activation of the [Sub-process] element. The active instance of the sub-process version that was “actual” when the [Sub-process] element was launched will continue running normally.

The sub-process log page, which displays the sub-process tasks on the [Process elements] detail in the order of their execution, is available as a separate process instance in the [Process Log] section and as a clickable process task in the [Process elements] detail of the parent process.

Completion

The [Sub-process] element is considered complete when the corresponding sub-process instance completes its execution.

Upon completion, the [Sub-process] element updates its parameter values from the corresponding parameters of the completed sub-process instance and activates its own outgoing flows.

Execution

When its incoming flow is activated, the [Sub-process] element starts looping through the data collection. For each item of the data collection, the [Sub-process] element runs a new instance of the process specified in the [Which process to run?] field by activating the [Simple] start event of the sub-process.

As a result, the currently actual version of the sub-process launches as a new independent process instance for each item in the data collection as soon as the previous sub-process instance is complete. Read more in the “Working with collections” article.

The incoming and bidirectional sub-process parameters (specified in the [Process parameters] block of the [Sub-process] element) can be mapped either to process elements from the same data collection or to non-collection elements. Non-collection process parameters will be re-used in all sub-process instances.

If you save another version of the sub-process as “actual” after the [Sub-process] element has been launched, any new sub-process instance will use the newest actual version to date. This means that the first instance of the sub-process and any other instances that ran before updating the actual version of the sub-process will use the previous version. We do not recommend saving another sub-process version as actual until all instances of the sub-process are either complete or canceled.

Note that the sub-process creates a separate instance in the [Process Log] section, which displays the sub-process tasks in its [Process elements] detail in the order of their execution. The parent process instance displays the link to the list of sub-process instances as a regular clickable process task in its own [Process elements] detail.

Completion

Upon completion of all sub-process instances, the element creates an entry in the outgoing data collection and populates the entry with parameter values from the corresponding parameters of the completed sub-process instance. After that, the next sub-process instance will be launched.

The [Sub-process] element is considered complete when the last sub-process instance is complete. Upon completion of the last instance, the [Sub-process] element updates the outgoing data collection and activates its own outgoing flows. Read more in the “Working with collections” article.

Execution

When its incoming flow is activated, the [Sub-process] element starts looping through the data collection. For each item of the data collection, the [Sub-process] element runs a new instance of the process specified in the [Which process to run?] field by activating the [Simple] start event of the sub-process.

As a result, the currently actual version of the sub-process launches as a new independent process instance for each item in the data collection immediately, barring limitations on the number of active background processes. Read more in the “Working with collections” article.

The incoming and bidirectional process parameters specified in the [Process parameters] block of the [Sub-process] element can be mapped either to process elements from the same data collection or to non-collection elements. Non-collection process parameters will be re-used in all sub-process instances.

If you save another version of the sub-process as “actual” after the [Sub-process] element has been launched, any new sub-process instance will use the newest actual version to date. Changing the sub-process actual version immediately after running a parallel multi-instance sub-process will not affect the first instance and any other instances that have already launched. Any instances that run after the change will use the new version. We do not recommend saving another sub-process version as actual until all instances of the sub-process are either running, complete or canceled.

Note that the sub-process creates a separate instance in the [Process Log] section, which displays the sub-process tasks in its [Process elements] detail in the order of their execution. The parent process instance displays the link to the list of sub-process instances as a regular clickable process task in its own [Process elements] detail.

Completion

Upon completion of each instance, the [Sub-process] element creates an entry in the outgoing data collection and populates the entry with parameter values from the corresponding parameters of the completed sub-process instance.

Note that the order of data entries in the collection cannot be predicted.

The [Sub-process] element is considered complete when the last remaining sub-process instance is complete. Upon completion of the last instance, the [Sub-process] element updates the outgoing data collection and activates its own outgoing flows. Read more in the “Working with collections” article.

Which process to run?

Specify a business process to use as the sub-process:

• you can select an existing Creatio business process to use it as a sub-process from the drop-down list

• you can add a new process via the Process Designer by clicking , if the needed process is not available on the list

 – opens the process selected as a sub-process in a new Process Designer window.

Note that to be eligible as a sub-process, a business process must start with a [Simple] start event.

Execution method

Only available in the multi-instance mode. To enable the multi-instance mode, map at least one of the process parameters to a data collection. Read more in the “Working with collections” article.

Select one of the two execution methods:

• [Sequential]. Sub-process instances run successively; a new sub-process instance runs upon completion of the previous instance. This is the default method.

• [Parallel]. Sub-process instances run simultaneously; the [Sub-process] element does not wait for the completion of the already running instances before running a new instance. Sub-process instances may complete in a different order.

Process parameters

When you select an existing Creatio process from the list, the parameters of the selected process are displayed in this block of the [Sub-process] setup area. You can populate the parameter values to run the sub-process with these values. During the execution of the sub-process, these values can be populated or updated, based on the logic of each specific sub-process. You can also map subsequent elements of the parent process to these parameters.

To add/edit/delete the element parameters, modify the process selected in the [Which process to run?] field.

Before making any changes to a business process, which is used as a sub-process, make sure that such changes will not affect other processes. For example, if you edit data type of a parameter and change it from the “Lookup” value to “Boolean” in a business process, this may lead to errors in any processes that use it as a sub-process.

Please check the [Used as sub-process in processes] detail of the [Launch options] tab in the Process Library before modifying an existing process. If this process has any sub-processes of its own, they will be displayed in the [Sub-processes] detail of the [Sub-processes] tab.