Guidance for automation

<< Click to Display Table of Contents >>

Navigation:  Process Execution >

Guidance for automation


Bizagi Studio is the construction environment that transforms processes designed with Bizagi Modeler into applications without the need for programming.

Bizagi offers a set of tools that enables you to graphically define the model associated with a business process (flowchart, business rules, user interface, etc.). This model is stored into a database, then is interpreted and executed in production by Bizagi BPM Server without having to use intermediate code. Bizagi Studio is available for free download from our site


To model processes that are executable in Bizagi Studio, you need to consider the following.



Activities represent work or tasks carried out by members of the organization. Bizagi Studio only supports some of the types of activities. You can define your tasks as User Task, Service Task, Receive Task, Send Task, Script Task, Manual Task or Business Rule Task.


Process Execution8



Start Events

The start event indicates the start of the process. Bizagi Studio supports several start events:


Start Event (it does not have any particular behavior)

Message Start Event

Timer Start Event

Signal Start Event

Conditional Start Event

Parallel Multiple Start Event

Multiple Start Event


Process Execution9


Intermediate Events

Intermediate events indicate where something happens somewhere between the start and the end of a Process. Bizagi Studio allows you to include five types of intermediate event in your processes.


Timer Intermediate Event

Message Intermediate Event

Signal Intermediate Event

Link Intermediate Event

Compensate Event

Escalation Event

Conditional Event

Parallel Multiple Event

Multiple Event


Process Execution10


When you include a message or a signal event in the diagrams, you must indicate if the event is used to Throw or to Catch.


Click here for more information about how to communicate between processes.


Process Execution11


End Events

End events indicate when a process ends. Bizagi Studio supports the following end events.


Terminate End Event

Message End Event

Signal End Event

Compensate End Event

Error End Event

Cancel End Event

Multiple End Event






Gateways indicates a variation in process flow whether depending on an expression or intending to create parallel flows.


Parallel Gateway

Inclusive Gateway

Event-based Gateway

Exclusive Event-based Gateway

Parallel Event-based Gateway

Complex Gateway


Process Execution12



Multiple Pools and Lanes

Multiple pools are not supported by the Bizagi BPM Suite. The processes that can be executed in Bizagi Studio must contain only one pool.

You can include several lanes to define and differentiate elements in the process: for example roles and departments.


Process Execution13


Process Execution14



To execute your model, you can use Sequence Flow Connectors Process Execution15   to connect the different elements in the process.

You can also include the association connector Process Execution16 to link artifacts to an element.



Bizagi Studio supports four types of sub-processes, each sub-process has a special behavior:


Embedded: When you define a Sub-process as Embedded, which is the default Sub-process, it will be dependent on the parent Process and consequently have visibility of the parent’s global data.

Reusable: A Reusable Sub-process is defined when an activity within a Process calls another predefined Process. The Process that is called is not dependent on the parent.

Multiple: A multiple Sub-process is instantiated several times. It could be executed in Parallel or in Sequence.

Transactional: The transactional Process is a Sub-process which behavior is controlled through a transaction protocol.


Click here for more information about transactional sub-processes.





Once you have completed the process modeling you can run it on the Bizagi BPM Suite.