When merging the merge events, you can optionally specify which of the merge events will be transferred to the resulting fragment using the eventmode attribute for the mergehandling XML element in the merger configuration. Valid values are STARTEVENT, ENDEVENT and IMPORTTIME, with a default value of IMPORTTIME.
The following event types exist:
Type |
Description |
Start event |
A standard event has no predecessor (outgoing connection only). |
Coupling event |
A coupling event has both predecessors and successors (incoming and outgoing connection). |
End event |
An end event has no successors (incoming connection only). |
Key-based merge
When using a key-based merge, the behavior when merging merge events is as follows:
eventmode |
Description |
IMPORTTIME |
The event imported later is transferred regardless of the event type. Default value |
STARTEVENT |
The event imported later that is not an end event is transferred. An end event is only transferred if two end events are being merged. |
ENDEVENT |
The event imported later that is not an start event is transferred. A start event is only transferred if two start events are being merged. |
Merge based on sort order
When using a merge based on sort order, the selected event types are given priority directly when merging as the process instance is always broken down into individual fragments of the form Event-Function-Event before the merge. If two merge events of the same type are being merged, the one imported later is transferred.