Explore topic-wise InterviewSolutions in .

There are three types of subprocesses that you can model in a BPD. Their characteristics are described in the following table.

Subprocess

A non-reusable subprocess that exists only within the PARENT process

Characteristics

Each subprocess must contain at least one start event with an implementation type of None.

Activity names must be unique with respect to the top-level process activities, and all other subprocesses and event subprocesses under the same top-level process.

Variable Scope

Inherits variables from the parent process and can contain local private variables VISIBLE only within the subprocess.

Variable names declared in a subprocess cannot be the same as variable names declared in any of its parent processes. If there are multiple layers of embedding, with subprocesses contained within other subprocesses, variable names must be unique throughout the entire subprocess hierarchy.

Linked process

A call to another reusable process.

Characteristics

The process called by the linked process activity can contain multiple start events, but must contain at least one start event with an implementation type of None.

Variable Scope

Variable data is local to each process, therefore data mapping is required to pass data into and out of the linked process.

Event subprocess

A specialized type of non-reusable subprocess that is not PART of the normal sequence flow of its parent process, and which might occur zero or MANY times during the execution of the parent process.

Characteristics

Must contain a single start event, which can be one of:

1. Timer
2. MESSAGE
3. Error

Event subprocess execution can interrupt parent process or can run in parallel.

Activity names must be unique with respect to the top-level process activities, and all other subprocesses and event subprocesses under the same top-level process.

Boundary events are not supported on an event subprocess.

Variable Scope

Inherits variables from the parent process and can contain local private variables visible only within the subprocess.

Variable names declared in an event subprocess cannot be the same as variable names declared in any of its parent processes. If there are multiple layers of embedding, with event subprocesses contained within other subprocesses, variable names must be unique throughout the entire subprocess hierarchy.

There are three types of subprocesses that you can model in a BPD. Their characteristics are described in the following table.

Subprocess

A non-reusable subprocess that exists only within the parent process

Characteristics

Each subprocess must contain at least one start event with an implementation type of None.

Activity names must be unique with respect to the top-level process activities, and all other subprocesses and event subprocesses under the same top-level process.

Variable Scope

Inherits variables from the parent process and can contain local private variables visible only within the subprocess.

Variable names declared in a subprocess cannot be the same as variable names declared in any of its parent processes. If there are multiple layers of embedding, with subprocesses contained within other subprocesses, variable names must be unique throughout the entire subprocess hierarchy.

Linked process

A call to another reusable process.

Characteristics

The process called by the linked process activity can contain multiple start events, but must contain at least one start event with an implementation type of None.

Variable Scope

Variable data is local to each process, therefore data mapping is required to pass data into and out of the linked process.

Event subprocess

A specialized type of non-reusable subprocess that is not part of the normal sequence flow of its parent process, and which might occur zero or many times during the execution of the parent process.

Characteristics

Must contain a single start event, which can be one of:

Event subprocess execution can interrupt parent process or can run in parallel.

Activity names must be unique with respect to the top-level process activities, and all other subprocesses and event subprocesses under the same top-level process.

Boundary events are not supported on an event subprocess.

Variable Scope

Inherits variables from the parent process and can contain local private variables visible only within the subprocess.

Variable names declared in an event subprocess cannot be the same as variable names declared in any of its parent processes. If there are multiple layers of embedding, with event subprocesses contained within other subprocesses, variable names must be unique throughout the entire subprocess hierarchy.