No

Figure 10.87 – Link Events Used for looping

The LinkEventDefinition element inherits the attributes and model associations of BaseElement (see Table 8.5) through its relationship to the EventDefinition element (see page 259). Table 10.98 presents the additional attributes of the LinkEventDefinition element.

Table 10.98 – LinkEventDefinition attributes

Message Event Definition

Figure 10.88 shows the variations of Message Events.

Figure 10.88 – Message Events

Figure 10.89 displays the class diagram for the MessageEventDefinition.

Figure 10.89 – MessageEventDefinition Class Diagram

The MessageEventDefinition element inherits the attributes and model associations of BaseElement (see Table 8.5) through its relationship to the EventDefinition element (see page 259). Table 10.99 presents the additional model associations of the MessageEventDefinition element.

Table 10.99 – MessageEventDefinition model associations

If the trigger is Multiple, there are multiple ways of starting the Process. Only one of them is necessary to trigger the start of the Process. The EventDefinition subclasses will define which triggers apply

For an End Event:

If the Result is Multiple, there are multiple consequences of ending the Process. All of them will occur. The EventDefinition subclasses will define which Results apply.

For an Intermediate Event within normal flow:

If the trigger is Multiple, only one EventDefinition is REQUIRED to catch the trigger. When used to throw, all of the EventDefinitions are considered and the subclasses will define which Results apply.

For an Intermediate Event attached to the boundary of an Activity:

If the trigger is Multiple, only one EventDefinition is REQUIRED to “catch” the trigger.

Figure 10.90 shows the variations of Multiple Events.

Figure 10.90 – Multiple Events

None Event

None Events are Events that do not have a defined EventDefinition. There are three (3) variations of None Events: a Start Event, a catch Intermediate Event, and an End Event (see Figure 10.91).

The None Start Event MAY be used for a top-level Process or any type of Sub-Process (except an

Event Sub-Process).

The None Start Event MAY NOT be used for an Event Sub-Process.

The catch None Intermediate Event MUST only be used in normal flow and, thus, MAY NOT be attached to the boundary of an Activity.

The None End Event MAY be used within any Sub-Process or Process.

Figure 10.91 shows the variations of None Events.

Figure 10.91 – None Events

Parallel Multiple Event

For a Start Event:

•If the trigger is Multiple, there are multiple triggers REQUIRED to start the Process. All of them are necessary to trigger the start of the Process. The EventDefinition subclasses will define which triggers apply. In addition, the parallelMultiple attribute of the Start Event MUST be set to true.

For an Intermediate Event within normal flow:

•If the trigger is Multiple, all of the defined EventDefinitions are REQUIRED to trigger the Event. In addition, the parallelMultiple attribute of the Intermediate Event MUST be set to true.

For an Intermediate Event attached to the boundary of an Activity:

•If the trigger is Multiple, all of the defined EventDefinitions are REQUIRED to trigger the Event. In addition, the parallelMultiple attribute of the Intermediate Event MUST be set to true.

Figure 10.92 shows the variations of Parallel Multiple Events.

Figure 10.92 – Multiple Events

Signal Event

Figure 10.93 – SignalEventDefinition Class Diagram

Figure 10.94 shows the variations of Signal Events.

Figure 10.94 – Signal Events

The SignalEventDefinition element inherits the attributes and model associations of BaseElement (see Table 8.5) through its relationship to the EventDefinition element (see page 259). Table 10.100 presents the additional model associations of the ConditionalSignalDefinition element.

Table 10.100 – SignalEventDefinition model associations

Terminate Event

Figure 10.95 shows the Terminate Event.