pe-bpmn-editor_otsend
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
pe-bpmn-editor_otsend [2018/04/23 17:05] admin |
pe-bpmn-editor_otsend [2018/04/23 23:30] admin [Group specific restrictions] |
||
|---|---|---|---|
| Line 7: | Line 7: | ||
| ===== Required input parameters ===== | ===== Required input parameters ===== | ||
| - | group (with OTReceive task) | + | group (with [[pe-bpmn-editor_otreceive|OTReceive]] task) |
| ===== Required output objects ===== | ===== Required output objects ===== | ||
| Line 23: | Line 23: | ||
| ===== Group specific restrictions ===== | ===== Group specific restrictions ===== | ||
| - | **Restriction:** there must be exactly one OTReceive and one OTSend task in a stereotype group\\ | + | **Restriction:** there must be exactly one [[pe-bpmn-editor_otreceive|OTReceive]] and one OTSend task in a stereotype group\\ |
| **Error:** element with OTReceive stereotype is missing from the group | **Error:** element with OTReceive stereotype is missing from the group | ||
| Line 29: | Line 29: | ||
| **Error:** both group tasks must be on separate lane | **Error:** both group tasks must be on separate lane | ||
| - | **Restriction:** OTReceive task of the stereotype group must be directly connected (through message flow) to the OTSend task of the same group\\ | + | **Restriction:** [[pe-bpmn-editor_otreceive|OTReceive]] task of the stereotype group must be directly connected (through message flow) to the OTSend task of the same group\\ |
| - | **Error:** element with OTReceive stereotype in this group must be directly connected (through message flow) to the element with OTSend stereotype and there must be no other connections between them | + | **Error:** element with [[pe-bpmn-editor_otreceive|OTReceive]] stereotype in this group must be directly connected (through message flow) to the element with OTSend stereotype and there must be no other connections between them |
| - | **Restriction:** OTSend task from the stereotype group must be in the flow (in incoming path, but not in outgoing path) of OTReceive task from the same stereotype group\\ | + | **Restriction:** OTSend task from the stereotype group must be in incoming path, but not in outgoing path of [[pe-bpmn-editor_otreceive|OTReceive]] task from the same stereotype group\\ |
| **Error:** element with OTSend stereotype in this group must be before element with OTReceive stereotype | **Error:** element with OTSend stereotype in this group must be before element with OTReceive stereotype | ||
| Line 38: | Line 38: | ||
| **Warning:** all group tasks are possibly not parallel | **Warning:** all group tasks are possibly not parallel | ||
| - | **Restriction:** all tasks from the same stereotype group that have common ExclusiveGateway elements in their flows must exist in all paths that start from these common ExclusiveGateways\\ | + | **Restriction:** all tasks from the same stereotype group that have common ExclusiveGateway elements in their paths (all tasks have the same ExclusiveGateway in their paths) must exist in all paths that start from these common ExclusiveGateways\\ |
| **Warning:** group task is possibly not accessible to the rest of the group | **Warning:** group task is possibly not accessible to the rest of the group | ||
| **Restriction:** there must be at least one StartEvent element on the model (to run parallelity checks)\\ | **Restriction:** there must be at least one StartEvent element on the model (to run parallelity checks)\\ | ||
| **Warning:** StartEvent element is missing | **Warning:** StartEvent element is missing | ||
pe-bpmn-editor_otsend.txt · Last modified: 2020/03/02 14:59 by pullonen
Page Tools
