Sub-Processes

A Sub-Process is a set of Activities that have a logical sequence that meet a clear
purpose. A Sub-Process is a Process in itself, whose functionality is part of a larger
Process. The larger process is known as the Parent process, and the Sub-Process itself
is mentioned as the Child process.
When an instance of a Sub-Process is created, the child process inherits the parent
process case number by default.

A Sub-Process is a component of a Process. It is used to divide Processes into smaller units for
assessment purposes. For example, an order-to-cash financial Process might be composed of
several Sub-Processes such as accounts payable, purchasing, and general accounting. Any of
these Sub-Processes might expose the Business Entity to risk and can be improved by using
controls.

Subprocesses are an integral concept in Sterling B2B Integrator, because building

a business process once, but using it as a subprocess in multiple other business
processes, simplifies future maintenance.

Any business process can be a subprocess. The term subprocess indicates a

business process that is invoked as part of another business process (the initiating
process is called the parent process).

When you modify a process model that is called as subprocess by multiple business
processes, you make one set of modifications – in the subprocess – but all of the parent
business processes use the updated subprocess when they run.

In this way, subprocesses work with the design concept of reusability; by identifying
simple units of work that appear in more than one business process, and designing your
subprocesses to be as generic as possible, you can save a great deal of time. The
following illustration shows how a subprocess fits into a larger business process model:
You can configure Sub-Processes either Embedded or Reusable. Furthermore, they
can be Transactional or Multiple, correspondingly:

SUB- DESCRIPTION
PROCESS

Embedded Embedded Sub-Processes can be configured

as Transactional

Reusable Reusable Sub-Processes can be configured

as Multiple

Transactiona This Sub-Process is defined as Embedded

l

Multiple This Sub-Process is defined as Reusable.

Sub-Process Properties
According to the type, Sub-Processes have different properties as shown below:

SUB-
CONSIDERAT SUB- CONSIDERAT
PROCESS PROPERTIES PROPERTIES
IONS PROCESS IONS
TYPE

•Is a Basic •Error, Basic

compound Properties Cancellation Properties
activity that •Display and •Display
contains other Name: This is the Compensation Name: This is
activities, display name of Events must the display
Embedded
gateways, the Sub-Process Transaction be associated name of the
Sub-
events, etc., that is shown in al Sub- to a Sub-Process that
Process Process
and is fully the Work Portal. Transaction is shown in the
dependent on •Name: This is Process. Work Portal.
the parent the name of the •It is defined •Name: This is
process; it Sub-Process in as an the name of the
does not exist database. It Embedded Sub-Process in
as a separate cannot be Sub-Processes. database.
process. It modified. •Description: Di
shares the •Description: Dis splays additional
same plays additional information for
information or information for the Sub-Process.
data with the the Sub-Process.
parent
process, and Runtime
can have a Properties
Transactional •Duration: Deter
definition. mines the
•Embedded maximum time
Processes are that a Sub-
not meant to Process can be
be reusable. active
•Cannot be (unfinished) to
configured as consider that it is
SUB-
CONSIDERAT SUB- CONSIDERAT
PROCESS PROPERTIES PROPERTIES
IONS PROCESS IONS
TYPE

multiple Sub- still on time.

Processes. •Priority: Indicat
•It can be set es the order on
as which Bizagi will
Transactional activate or
Sub-Process execute Sub-
Processes.
•Is
Asynchronous:
Enables
asynchronous
behavior for the
Sub-Process.
•Retries: Determ
ines the number
of times that the
asynchronous
task must be
executed
automatically if
an error is
thrown.
•Retry
Interval: An
interval of time in
minutes that
must be fulfilled
before retrying
the automatic
execution of
asynchronous
task in case of
error.
•Show
Feedback: The
system will
execute
immediately the
Work Portal if this
option is enabled
and a wait page
will be displayed
while the request
is Processed; if
this option is
disabled, then the
asynchronous
task is executed
later in the Bizagi
scheduler and the
user is send to
the default page
depending on the
case.
•Timeout: Allows
defining a
SUB-
CONSIDERAT SUB- CONSIDERAT
PROCESS PROPERTIES PROPERTIES
IONS PROCESS IONS
TYPE

maximum interval
in seconds, in
which the
execution of the
asynchronous
task is possible;
the system
automatically
cancels the
operation when
the time is
reached.

•Is an activity Basic •Can be Basic

that Properties created as Properties
references •Display Sequential or •Display
another Name: This is the Parallel Name: This is
process, display name of •Parallel the display
Reusable
independent the Sub-Process multiple Sub- name of the
Sub-
to the parent that is shown in Processes are Sub-Process that
Process
process the Work Portal. identified by is shown in the
definition; it •Name: This is three vertical Work Portal.
can be called the name of the Multiple •Name: This is
from other Sub-Process in Sub-Process the name of the
process database. lines Sub-Process in
definitions. •Description: Dis •Sequential database.
Reusable sub- plays additional multiple Sub- •Description: Di
processes can information for Processes are splays additional
be defined as the Sub-Process. identified by information for
multiple sub- three the Sub-
processes. horizontal
Process.
•This Sub-
lines
Process can be
•It is defined
integrated or
as a Reusable
standalone:
Sub-Process
oIf integrated
is chosen, the
parent Process
continues
when the Sub-
Process is
finished.
oIf standalone
is chosen, the
parent Process
continues with
the next
Activity as
soon as the
Sub-Process is
started.
•The Reusable
Sub-Processes
cannot be
transactional,
and can be
SUB-
CONSIDERAT SUB- CONSIDERAT
PROCESS PROPERTIES PROPERTIES
IONS PROCESS IONS
TYPE

configured as
a multiple
Sub-Process.
•The Reusable
Sub-Process
can be set as
multiple.

Sub-Processes can be represented in an expanded or collapsed way:

Expanded Sub-Processes
When the Sub-Process is expanded all its details can be seen within the limits.

In the following diagram, the Travel Request Process is depicted with an

expanded Booking Sub-Process. The Activities within the Sub-Process are part of the
main Process. This is a single Process represented in a single diagram.

Collapsed Sub-Processes
When the Sub-Process is collapsed, the details of the Sub-Process cannot be viewed.
The plus sign (+) indicates that the shape is a Sub-Process and it has a lower level of
detail.

In the next diagram, the Travel Request Process is depicted with a

collapsed Bookings Sub-Process.

The details of the Bookings Sub-Process are depicted in a separate diagram.