In this pattern, the boundary event is a compensation event.
Element construct
<scope name =ncname
variableAccessSerializable="yes|no"
standard-attributes>
<compensationHandler>
Target Process
</compensationHandler>
Source Process
</scope>
BPEL comments
1 A <scope> element is created and all subsequent constructs for this pattern reside within the scope.
2 The ncname of the scope attribute is taken from the name of the process that has the boundary event attached to it. "BPMN Process".name
3 The boundary event definition is obtained from the sequence flow definition. "Sequence Flow". "Initiating Event"
4 The boundary event stereotype must be ONLY be "compensation" and its value determined from "BPMN Event".Stereotype
5 The standard-attributes are determined from the process symbol that the boundary event is attached to.
6 The sequence flow flowing out from the boundary event must connect to another symbol. All the subsequent activities sit within the <catchAll> element occupying the position indicated by the "Target Process"
7 In case the Source Process itself has detail by way of children diagrams or embedded activities, these will occupy the placeholder position indicated by "Source Process".
