Sub-Processes

<< Click to Display Table of Contents >>

Navigation:  Bizagi Studio > Process wizard > Model Process > Modeling for execution >

Sub-Processes

Overview

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. This helps identify which sub-process belongs to which parent process. You can configure if the case number is inherited, for more information click Use Parent case number.

 

In Bizagi Sub-Processes configuration is done as soon as a task is converted into a Sub-Process via the Sub-Process Configuration Wizard. This will be explained in detail in the following sections.

 

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.

 

Subprocesses1

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.

 

Subprocesses2

 

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

 

Subprocesses3

 

All Processes modeled in Bizagi are potential Sub-Processes.

 

Sub-Process Properties

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

 

ELEMENT

CONSIDERATIONS

PROPERTIES

Sub process

Embedded Sub-Process

Embedded Sub-Processes contain a set of Activities that are dependent of the Parent Process; they share the same information or data. They have a clear objective and so, can be defined with a beginning and an end.

Embedded Processes are not meant to be reusable.

Cannot be configured as multiple Sub-Processes.

Basic Properties

 

Display Name: This is the display name of the Sub-Process that is shown in the Work Portal.

 

Name: This is the name of the Sub-Process in database. It cannot be modified..

 

Description: Displays additional information for the Sub-Process.

 

Runtime Properties

 

Cost: Indicates the cost of Tasks.

 

Duration: Determines the maximum time that a Sub-Process can be active (unfinished) to consider that it is still on time.

 

Priority: Indicates the order on which Bizagi will activate or execute Sub-Processes.

 

Is Asynchronous: Enables asynchronous behavior for the Sub-Process.

 

Retries: Determines 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 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.

Reusable sub processReusable Sub-Process

This Sub-Process can be integrated or standalone:

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 configured as a multiple Sub-Process.

Basic Properties

 

Display Name: This is the display name of the Sub-Process that is shown in the Work Portal.

 

Name: This is the name of the Sub-Process in database.

 

Description: Displays additional information for the Sub-Process.

TransactionTransactional Sub-Process

Error, Cancellation and Compensation Events must be associated to a Transaction Process

Basic Properties

 

Display Name: This is the display name of the Sub-Process that is shown in the Work Portal.

 

Name: This is the name of the Sub-Process in database.

 

Description: Displays additional information for the Sub-Process.

Multi Instance loop sub-process

Multi Instance parallel loop sub-process

Multiple Sub-Process

They can be created in two ways: Sequential or Parallel

 

Parallel multiple Sub-Processes are identified by three vertical lines Multiple identifier2

 

Sequential multiple Sub-Processes are identified by three horizontal lines Multiple identifier1

Basic Properties

 

Display Name: This is the display name of the Sub-Process that is shown in the Work Portal.

 

Name: This is the name of the Sub-Process in database.

 

Description: Displays additional information for the Sub-Process.