<%@ Page Language="C#"%> Bizagi Modeler > User Interface explained > Palette > Events <% if(!RequestUserAgentHelper.IsGoogleBot()){ %> <%} %>

Events

<< Click to Display Table of Contents >>

Navigation:  Bizagi Modeler > User Interface explained > Palette >

Events

Overview

An Event is something that happens during the course of the Process, affecting the Process flow and normally has a trigger or result.

To make an event a throw or a catch event, right click on it and select Is Throw. This option will enable or disable its behavior (applies for certain events described below) .

 

Start Events

 

ELEMENT

DESCRIPTION

NOTATION

Start Event

Indicates where a particular Process starts. It does not have any particular behavior.

Start event

Message Start Event

Is used when a message arrives from a participant and triggers the start of the Process.

Message start event

Timer Start Event

Is used when the start of a Process occurs on a specific date or cycle time (e.g., every Friday)

Timer start

Conditional Start Event

This type of Event triggers the start of a Process when a condition becomes true.

Conditional start

Signal Start Event

The start of the Process is triggered by the arrival of a signal that has been broadcast from another Process.

 

Note that the signal is not a message; messages have specific targets, signals do not.

Signal start event

Parallel Multiple Start Event

Indicates that there are multiple triggers required to start the Process. ALL triggers must be triggered before the Process is instantiated.

Parallel multiple start

Multiple Start Event

This means that there are multiple ways of triggering the Process. Only one of them is required.

Multiple start

 

Intermediate events

 

ELEMENT

DESCRIPTION

NOTATION

Intermediate Event

Indicates where something happens somewhere between the start and end of a Process. It will affect the flow of the Process, but will not start or (directly) terminate the Process.

Intermediate event

Message Event

Indicates that a message can be sent or received.

 
If a Process is waiting for a message and it is caught the Process will continue its flow.

 
A catch Message Event waits for a message to arrive and once the message has been received, the Process will continue. The Event marker in this instance will be unfilled.

 

A throw Message Event sends a message to an external participant. The filled Event marker is allocated to the throw message.

Message intermediate event

Timer Event

Indicates a delay within the Process. This type of Event can be used within the sequential flow indicating a waiting time between activities.

Timer intermediate

Escalation Event

The Event indicates an escalation through the Process.

Escalation intermediate

Compensation Event

Enables the handling of compensations. When used within the sequential flow of a Process they indicate that compensation is necessary.

Compensate intermediate

Conditional Event

This Event is triggered when a condition becomes true.

Conditional intermediate

Link Event

This Event is used to connect two sections of the Process.

Link Events can be used to create looping situations or to avoid long Sequence Flow lines.

If there are two link events on a process (one catch and one throw) the Modeler will understand they are linked together. If there is one catch and two throw, the Modeler will understand both throws are received by the catch. If there are several catch and throw events the name of the 'pairs' must match for the Modeler to understand which throw belongs to which catch.

Link intermediate

Signal Event

These Events are used to send or receive signals within or across the Process. A signal is similar to a signal flare that is shot into the sky for anyone who might be interested to notice and then react.

 
If the Event is used to throw the signal, the signal Event marker will be filled. Alternatively, the unfilled Event marker is allocated to catch the message.

Signal intermediate

Multiple Event

This means that there are multiple triggers assigned to the Event.

 
When used to catch the trigger, only one of the assigned triggers is required and the Event marker will be unfilled.

Multiple intermediate

Parallel multiple Event

This means that there are multiple triggers assigned to the Event. Unlike the normal Multiple Intermediate Event, ALL of the assigned triggers are required for the Event to be triggered.

Parallel intermediate

 

Intermediate Events Attached to an Activity Boundary

 

ELEMENT

DESCRIPTION

NOTATION

Message Event

If a message Event is attached to the boundary of an activity, it will change the normal flow into an exception flow when a message is received.

 

If the Event interrupts the activity to which it is attached, the boundary of the Event is solid, if not it is dashed.

Attached Message intermediate event

Timer Event

If a Timer Event is attached to the boundary of an activity, it will change the normal flow into an exception flow when a cycle time is completed or a specific time-date is reached.

 

If the Event interrupts the Activity to which it is attached, the boundary of the Event is solid, if not it is dashed.

Attached Timer intermediate

Escalation Event

If attached to the boundary of an Activity, the Intermediate Event catches an Escalation.

 

If the Event interrupts the Activity to which it is attached, the boundary of the Event is solid, if not it is dashed.

Attached Escalation intermediate

Error Event

 

 

 

A catch Intermediate Error Event can only be attached to the boundary of an Activity.

 

It reacts to (catches) a named Error, or to any Error if a name is not specified.

 

An Error Event always interrupts the Activity to which it is attached, i.e., there is not a non-interrupting version of this Event. Thus the boundary of the Event is always solid.

Error Intermediate

Cancel Event

 

 

 

 

This Event is used within a Transaction Sub-Process and must be attached to the boundary of one.

 

It shall be triggered if a Cancel End Event is reached within the Transaction Sub-Process. It also shall be triggered if a Transaction Protocol Cancel Message has been received while the transaction is being performed.

 

A Cancel Event always interrupts the Activity to which it is attached, i.e., there is not a non-interrupting version of this Event. Thus the boundary of the Event is always solid.

Cancel Intermediate

Compensation Event

When attached to the boundary of an Activity, this Event is used to catch the Compensation Event. When it occurs, the compensation activity will be performed.

 

Interrupting a non-interrupting aspect of other Events does not apply in the case of a Compensation Event, thus the boundary of the Event is always solid.

Attached Compensation intermediate

Conditional Event

If a Conditional Event is attached to the boundary of an Activity, it will change the normal flow into an exception flow when a business condition is fulfilled.

 

If the Event interrupts the Activity to which it is attached, the boundary of the Event is solid, if not it is dashed.

Attached Conditional intermediate

Signal Event

If a Signal Event is attached to the boundary of an Activity, it will change the normal flow into an exception flow when a signal is received.

 

If the Event interrupts the Activity to which it is attached, the boundary of the Event is solid, if not it is dashed.

Attached Signal intermediate

Multiple Event

When attached to the boundary of an Activity, it will change the normal flow into an exception flow when one of the assigned triggers is caught.

 

If the Event interrupts the Activity to which it is attached, the boundary of the Event is solid, if not it is dashed.

Attached Multiple intermediate

Parallel multiple Event

Unlike the Multiple Event, when attached to the boundary of an Activity, it will change the normal flow into an exception flow when ALL of the assigned triggers are caught.

 

If the Event interrupts the Activity to which it is attached, the boundary of the Event is solid, if not it is dashed.

Attached Parallel intermediate

 

End Events

 

ELEMENT

DESCRIPTION

NOTATION

End Event

Indicates when the Process ends.  

End event

Message End

Indicates that a message is sent when the flow has ended.

Message end

Escalation End

Indicates that an Escalation is necessary when the flow ends.

Escalation end

Error End

Indicates that a named Error should be generated. All currently active threads of the Process are terminated. The Error will be caught by a Catch Error Intermediate Event.

Error end

Cancel End

Is used within a Transaction Sub-Process. It indicates that the Transaction should be canceled and an alternative flow can be performed.

Cancel end

Compensation End

Handles compensations. If an activity is identified, and it was successfully completed, the activity will be compensated.

Compensation end

Signal End

Indicates that a signal is sent when the flow has ended.

Signal end

Multiple End

This means that there are multiple consequences of ending the flow. All of them will occur.

Multiple end

Terminate End

Ends the Process and all its activities immediately.  

Terminate end