-
Key: BPMN2-129
-
Legacy Issue Number: 14676
-
Status: closed
-
Source: International Business Machines ( Ms. Suzette Samoojh)
-
Summary:
The ErrorEventDefinition contains an errorCode and references an Error class. Wouldn't it make sense for errorCode to be moved into the Error class. I'd expect that all usages of that Error class would specify the same errorCode.
Same pattern is there for Escalation.
-
Reported: BPMN 2.0b1 — Thu, 19 Nov 2009 05:00 GMT
-
Disposition: Resolved — BPMN 2.0
-
Disposition Summary:
(a) Insert new subsection, under 8.3, for Escalation.
An Escalation identifies a business situation that a process may need to react to.
Insert Figure
(Escalation_MM.jpg)
The Escalation element inherits the attributes and model associations of Base Element through its relationship to RootElement.
New table, with attributes
name: The descriptive name of the escalation
structureRef: An ItemDefinition that defines the payload of the escalation
(b) Move the "errorCode" attribute from Table 10.89 to Table 8.43
(c) Move the "escalationCode" attribute from Table 10.90 to new table for Escalation
(d) Replace Figure 8.20 with
(Error_MM.jpg)
(e) Replace Figure 10.70 with
(EventDefinitions_MM.jpg)
(f) Replace Figure 10.75 with
(ErrorEventDefinition_MM.jpg)
(g) Replace Figure 10.77 with
(EscalationEventDefinition_MM.jpg)
(h) Table 8.64 (schema snippet): Updated XSD snippet to add the errorCode attribute to tError
<xsd:element name="error" type="tError" substitutionGroup="rootElement"/>
<xsd:complexType name="tError">
<xsd:complexContent>
<xsd:extension base="tRootElement">
<xsd:attribute name="name" type="xsd:string"/>
<xsd:attribute name="structureRef" type="xsd:QName"/>
<xsd:attribute name="errorCode" type="xsd:string"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
New table under 8.3.18, for the Escalation schema snippet
<xsd:element name="escalation" type="tEscalation" substitutionGroup="rootElement"/>
<xsd:complexType name="tEscalation">
<xsd:complexContent>
<xsd:extension base="tRootElement">
<xsd:attribute name="name" type="xsd:string"/>
<xsd:attribute name="structureRef" type="xsd:QName"/>
<xsd:attribute name="escalationCode" type="xsd:string"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
(j) Table 10.101: Updated XSD snippet to remove the errorCode attribute from tErrorEventDefinition
<xsd:element name="errorEventDefinition" type="tErrorEventDefinition" substitutionGroup="eventDefinition"/>
<xsd:complexType name="tErrorEventDefinition">
<xsd:complexContent>
<xsd:extension base="tEventDefinition">
<xsd:attribute name="errorRef" type="xsd:QName"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
(k) New table under 10.4.8, for the EscalationEventDefinition schema snippet
<xsd:element name="escalationEventDefinition" type="tEscalationEventDefinition" substitutionGroup="eventDefinition"/>
<xsd:complexType name="tEscalationEventDefinition">
<xsd:complexContent>
<xsd:extension base="tEventDefinition">
<xsd:attribute name="escalationRef" type="xsd:QName"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
Disposition: Resolved -
Updated: Fri, 6 Mar 2015 20:57 GMT
BPMN2 — Error vs ErrorCode & Escalation vs EscalationCode
- Key: BPMN2-129
- OMG Task Force: BPMN 2.0 FTF