Intermediate Event

None

Basic Properties

•Display Name: This is the display name of the Event that is shown in the Work Portal.

•Name: This is the name of the Event in database.

•Description: Displays additional information for the Event.

•Can reassign: If enabled, the Event can be reassigned by the user during the process. By default, the property is disabled. For more information about this option, refer to the Work Reassignment documentation.
This feature is not available in mobile devices.

•Priority: Indicates the order on which Bizagi will activate or execute Events.

•Can release: If enabled, the Event can be released by the user during the process. By default, the property is disabled. For more information about this option, refer to the Work Reassignment documentation.
This feature is not available in mobile devices.

•Notify on assignment: When enabled, this property notifies about the assignment to all users that have been assigned to an Event.

•Help text: In this option, the user can configure a help text for the Event.

•URL Help: In this option, the user can configure a URL that contains help text for the Event. The configured URL will be opened in a new tab in your browser.

•Message when activity is completed: Defines the message shown when the intermediate event is finished. If no message is defined, the Process will show the Global Form.

Message Event

•If a Process is waiting for the message, it will be paused until the message arrives or it will change the flow for exception handling.

•To use a throw Message, there has to be a corresponding catch Message Event that catches the message. It can be a Message Intermediate Event or a Message Start Event.  

•The shape in the Process that throws the message should be configured to identify the target Process and the target Element.

•The catch and throw messages must have the same name and they must be in different Processes.

•For further information about how to configure Events please refer to the Message Exchange documentation.

Basic Properties

•Display Name: This is the display name of the Event that is shown in the Work Portal.

•Name: This is the name of the Event in database.

•Description: Displays additional information for the Event.

Timer Event

•The length or the time assigned to the Timer Intermediate Event can be fixed or variable and is defined in minutes. The minutes assigned correspond to the wait time that must be considered. For example, if the Process flows arrives to an Event Timer which has defined duration of 120 minutes at 17:00 (5:00 p.m.) on Friday and the work shift has been defined from Monday to Friday at 9:00 (9:00 a.m.), then the Process will wait before continuing to the following Activity.

•For further information about how to configure Timer Events please refer to the Timers Duration documentation.

Basic Properties

•Display Name: This is the display name of the Event that is shown in the Work Portal.

•Name: This is the name of the Event in database.

Runtime Properties

•Duration: The time in hours and minutes that must transpire before the Event triggers. The calendar associated to the organization in the Working Time Schema is considered for this calculation. Maximum values are:

o35791393 (Hours)

o59 (Minutes)

Link Event

•Link Event uses are limited to a single Process level. That is, they are used only within the same Process.

•The throw Event should have no outgoing transitions. The catch Event should have no incoming transitions. Bizagi will automatically convert the link Event to a throw Event as soon as the diagram is saved.

•The catch and throw links must have the same display name.

•There can be only one Catch Link for one Throw Link.

Basic Properties

•Display Name: This is the display name of the Event that is shown in the Work Portal.

•Name: This is the name of the Event in database.

•Description: Displays additional information for the Event.

Signal Event

•A signal is sent globally to any Signal catch event shape that is active. To know which signal is caught the shape must have the same Name as the Signal throw event. Any active configured Signal Catch event will listen to the thrown signal and will pass on the process token.

•This shape has a throw and a catch option, which is to send a Signal or receive a Signal. When used to throw the signal, the shape is filled. When used to catch the signal, the shape is unfilled.

Basic Properties

•Display Name: This is the display name of the Event that is shown in the Work Portal.

•Name: This is the name of the Event in database. It cannot be modified.

•Description: Displays additional information for the Event.

Conditional Event

•A Boolean condition must be defined.

Basic Properties

•Display Name: This is the display name of the Event that is shown in the Work Portal.

•Name: This is the name of the Event in database. It cannot be modified.

•Description: Displays additional information for the Event.

Message Event

•The shape in the Process that throws the message should be configured to identify the target Process and the target Element.

•These event and throw messages must have the same name and they must be in different Processes.

Basic Properties

•Display Name: This is the display name of the Event that is shown in the Work Portal.

•Name: This is the name of the Event in database.

•Description: Displays additional information for the Event.

Timer Event

•If it is used as time control for a Manual Activity, it will be diagrammed within the Activity (bottom).

•When activated the Event interrupts the Activity to which it is attached.

•For further information about how to configure Timer Events please refer to the Timers Duration documentation.

Basic Properties

•Display Name: This is the display name of the Event that is shown in the Work Portal.

•Name: This is the name of the Event in database.

•Duration: The time in minutes that must transpire before the Event triggers. The calendar associated to the organization in the Working Time Schema is considered for this calculation.

Error Event

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

•For further information please refer to the Transactional Sub-process documentation.

Basic Properties

•Display Name: This is the display name of the Event that is shown in the Work Portal,

•Name: This is the name of the Event in database.

•Description: Displays additional information for the Event.

Cancel Event

•This Event is used within a Transactional Sub-Process and must be attached to the boundary of it.

•It will be triggered if a Cancel End Event is reached within the Transaction Sub-Process. It also will 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.

•For further information please refer to the Transactional Sub-process documentation.

Basic Properties

•Display Name: This is the display name of the Event that is shown in the Work Portal

•Name: This is the name of the Event in database.

•Description: Displays additional information for the Event.

Compensation Event

•This Event is used to catch the Compensation Event. When it occurs, a Compensation Activity will be performed.

•For further information please refer to the Transactional Sub-process documentation.

Basic Properties

•Display Name: This is the display name of the Event that is shown in the Work Portal

•Name: This is the name of the Event in database. It cannot be modified.

•Description: Displays additional information for the Event.

Signal Event

•This shape is only able to receive signals.

Basic Properties

•Display Name: This is the display name of the Event that is shown in the Work Portal.

•Name: This is the name of the Event in database. It cannot be modified.

•Description: Displays additional information for the Event.