Sei sulla pagina 1di 10

6/8/2017 Process Execution > Guidance for automation

Guidance for automation

Overview
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 www.bizagi.com.

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

Activities
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.

http://help.bizagi.com/process-modeler/en/index.html?guidance_for_automation.htm 1/10
6/8/2017 Process Execution > Guidance for automation

Events

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

http://help.bizagi.com/process-modeler/en/index.html?guidance_for_automation.htm 2/10
6/8/2017 Process Execution > Guidance for automation


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

http://help.bizagi.com/process-modeler/en/index.html?guidance_for_automation.htm 3/10
6/8/2017 Process Execution > Guidance for automation


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.

http://help.bizagi.com/process-modeler/en/index.html?guidance_for_automation.htm 4/10
6/8/2017 Process Execution > Guidance for automation


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

http://help.bizagi.com/process-modeler/en/index.html?guidance_for_automation.htm 5/10
6/8/2017 Process Execution > Guidance for automation


Gateways
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

http://help.bizagi.com/process-modeler/en/index.html?guidance_for_automation.htm 6/10
6/8/2017 Process Execution > Guidance for automation



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.

http://help.bizagi.com/process-modeler/en/index.html?guidance_for_automation.htm 7/10
6/8/2017 Process Execution > Guidance for automation

http://help.bizagi.com/process-modeler/en/index.html?guidance_for_automation.htm 8/10
6/8/2017 Process Execution > Guidance for automation


Connectors

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

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

Sub-process
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 parents global data.

http://help.bizagi.com/process-modeler/en/index.html?guidance_for_automation.htm 9/10
6/8/2017 Process Execution > Guidance for automation

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.


Execution

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

http://help.bizagi.com/process-modeler/en/index.html?guidance_for_automation.htm 10/10