Events
| Spec Page | Spec Rule Text | RuleId |
|---|---|---|
217 |
If any of the EventDefinitions for the Event is associated with an element that has an ItemDefinition (such as a Message, Escalation, Error, or Signal), the following constraints apply: |
|
217, 234 |
If the Event is associated with multiple EventDefinitions, there MUST be one Data Input (in the case of throw Events) or one Data Output (in the case of catch Event) for each EventDefinition. The order of the EventDefinitions and the order of the Data Inputs/Outputs determine which Data Input/Output corresponds with which EventDefinition. |
|
217, 234 |
For each EventDefinition and Data Input/Output pair, if the Data Input/Output is present, it MUST have an ItemDefinition equivalent to the one defined by the Message, Escalation, Error, or Signal on the associated EventDefinition. |
|
264 |
For executable Processes (isExecutable = true), if the trigger is Conditional, then a FormalExpression MUST be entered [attribute condition of ConditionalEventDefinition]. |
|
270 |
The Message [attribute messageRef of MessageEventDefinition] MUST be supplied (if the isExecutable attribute of the Process is set to true). |
|
270 |
This attribute [operationRef of MessageEventDefinition] specifies the Operation that is used by the Message Event. It MUST be specified for executable Processes. |
|
273 |
The return type of the attribute timeDate [of TimerEventDefinition] MUST conform to the ISO-8601 format for date and time representations. |
|
273 |
The return type of the attribute timeCycle [of TimerEventDefinition] MUST conform to the ISO-8601 format for date and time representations. |
|
273 |
The return type of the attribute timeDuration [of TimerEventDefinition] MUST conform to the ISO-8601 format for date and time representations. |