Intermediate Events Properties
Intermediate Event
Considerations
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 the 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.
This feature is not available on 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.
This feature is not available on mobile devices. - Notify on assignment: When enabled, this property notifies all users assigned to an Event.
- Help text: The user can configure a help text for the Event.
- URL Help: The user can configure a URL that contains help text for the Event, which will open in a new browser tab.
- 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
Considerations
- 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.
- In order 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 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 the database.
- Description: Displays additional information for the Event.
Timer Event
Considerations
- The length or 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 before the process can continue.
- In order for the shape to operate properly, the scheduler service for the corresponding application must be enabled.
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 the database.
Runtime Properties
- Duration: The time in hours and minutes that must transpire before the Event triggers.
The calendar associated with the organization in the Working Time Schema is considered for this calculation.
Maximum values:- 35,791,393 (Hours)
- 59 (Minutes)
Link Event
Considerations
- Link Events are limited to a single Process level (within the same Process).
- The throw Event should have no outgoing transitions.
- The catch Event should have no incoming transitions.
- Bizagi automatically converts 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 the database.
- Description: Displays additional information for the Event.
Signal Event
Considerations
- 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 both throw and catch options:
- Throw signal: The shape is filled.
- Catch 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 the database (cannot be modified).
- Description: Displays additional information for the Event.
Conditional Event
Considerations
- 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 the database (cannot be modified).
- Description: Displays additional information for the Event.
Intermediate Events Attached to an Activity Boundary
Message Event (Attached)
Considerations
- The shape in the Process that throws the message should be configured to identify the target Process and the target Element.
- These events and throw messages must have the same name and 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 the database.
- Description: Displays additional information for the Event.
Timer Event (Attached)
Considerations
- If 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.
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 the database.
- Duration: The time in minutes before the Event triggers, considering the Working Time Schema.
Error Event
Considerations
- 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.
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 the database.
- Description: Displays additional information for the Event.
Cancel Event
Considerations
- This Event is used within a Transactional Sub-Process and must be attached to its boundary.
- It will be triggered if a Cancel End Event is reached within the Transaction Sub-Process or if a Transaction Protocol Cancel Message is received.
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 the database.
- Description: Displays additional information for the Event.
Compensation Event
Considerations
- This Event is used to catch the Compensation Event and triggers a Compensation Activity.
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 the database (cannot be modified).
- Description: Displays additional information for the Event.
Signal Event (Attached)
Considerations
- 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 the database (cannot be modified).
- Description: Displays additional information for the Event.