-
Feature Request
-
Resolution: Fixed
-
L3 - Default
-
None
Scenario
A user has two different Error End Events, each referencing a different <error /> and a "catch-all" error start event in an event subprocess. Since the start event can catch two different errors, the user wants to reason about which error has been caught by the start event by storing error code and error message as variables. While it is currently possible to specify an error message when throwing an error from delegation code with new BpmnError(code, message) it is not possible to do so when defining the error end event.
Feature Description
Given:
- An error end event which references a BPMN Error definition with camunda:errorMessage defined as in the following example:: <bpmn:error id="Error_1x1ymni" name="INVALID_DATA" errorCode="1231" camunda:errorMessage="The data provided is invalid" />
- An error start event which uses camunda:errorMessageVariable="foo"
When
The end event is executed
Then
The start event is triggered and after executing it, the variable foo contains the value "The data provided is invalid".
This is the controller panel for Smart Panels app
[CAM-9994] I can define a BPMN Error Throw Event with an error message
| Link | New: This issue is depended on by SUPPORT-5568 [ SUPPORT-5568 ] |
| Remote Link | New: This issue links to "Modeler Issue (Web Link)" [ 12819 ] |
| Description |
Original:
It is possible to define a BPMN Error Throw Event with an error message in the Modeler.
However, the error message is not parsed by the engine and is lost. This should be made possible. Hint: This is where the parsing happens: https://github.com/camunda/camunda-bpm-platform/blob/1ee1f47ce32cb13b30852522c1415bbce7c96c6d/engine/src/main/java/org/camunda/bpm/engine/impl/bpmn/parser/BpmnParse.java#L417-L434 The {{Error}} class is used, which doesn't contain any message properties. |
New:
It is possible to define a BPMN Error Throw Event with an error message in the Modeler.
However, the error message is not parsed by the engine and is lost. This should be made possible. Hint: This is where the parsing happens: https://github.com/camunda/camunda-bpm-platform/blob/1ee1f47ce32cb13b30852522c1415bbce7c96c6d/engine/src/main/java/org/camunda/bpm/engine/impl/bpmn/parser/BpmnParse.java#L417-L434 The {{Error}} class is used, which doesn't contain any message properties. Possible Usage scenario: A user has two different Error End Events, each referencing a different {{<error />}} and a "catch-all" error start event in an event subprocess. Since the start event can catch two different errors, the user wants to reason about which error has been caught by the start event by storing error code and error message as variables. While it is currently possible to specify an error message when throwing an error from delegation code with new {{BpmnError(code, message)}} it is not possible to do so when defining the error end event. |
| Description |
Original:
It is possible to define a BPMN Error Throw Event with an error message in the Modeler.
However, the error message is not parsed by the engine and is lost. This should be made possible. Hint: This is where the parsing happens: https://github.com/camunda/camunda-bpm-platform/blob/1ee1f47ce32cb13b30852522c1415bbce7c96c6d/engine/src/main/java/org/camunda/bpm/engine/impl/bpmn/parser/BpmnParse.java#L417-L434 The {{Error}} class is used, which doesn't contain any message properties. Possible Usage scenario: A user has two different Error End Events, each referencing a different {{<error />}} and a "catch-all" error start event in an event subprocess. Since the start event can catch two different errors, the user wants to reason about which error has been caught by the start event by storing error code and error message as variables. While it is currently possible to specify an error message when throwing an error from delegation code with new {{BpmnError(code, message)}} it is not possible to do so when defining the error end event. |
New:
*Scenario:*
A user has two different Error End Events, each referencing a different {{<error />}} and a "catch-all" error start event in an event subprocess. Since the start event can catch two different errors, the user wants to reason about which error has been caught by the start event by storing error code and error message as variables. While it is currently possible to specify an error message when throwing an error from delegation code with new {{BpmnError(code, message)}} it is not possible to do so when defining the error end event. **Given:** * An error end event which references a a BPMN Error definition with {{camunda:errorMessage}} defined as in the following example:: {{<bpmn:error id="Error_1x1ymni" name="INVALID_DATA" errorCode="1231" camunda:errorMessage="The data provided is invalid" />}} * An error start event which uses {{camunda:errorCodeVariable="foo"}} ** When** The end event is executed ** Then ** The start event is triggered and after executing it, the variable {{foo}} contains the value "The data provided is invalid". ---- Previous description It is possible to define a BPMN Error Throw Event with an error message in the Modeler. However, the error message is not parsed by the engine and is lost. This should be made possible. Hint: This is where the parsing happens: https://github.com/camunda/camunda-bpm-platform/blob/1ee1f47ce32cb13b30852522c1415bbce7c96c6d/engine/src/main/java/org/camunda/bpm/engine/impl/bpmn/parser/BpmnParse.java#L417-L434 The {{Error}} class is used, which doesn't contain any message properties. |
| Description |
Original:
*Scenario:*
A user has two different Error End Events, each referencing a different {{<error />}} and a "catch-all" error start event in an event subprocess. Since the start event can catch two different errors, the user wants to reason about which error has been caught by the start event by storing error code and error message as variables. While it is currently possible to specify an error message when throwing an error from delegation code with new {{BpmnError(code, message)}} it is not possible to do so when defining the error end event. **Given:** * An error end event which references a a BPMN Error definition with {{camunda:errorMessage}} defined as in the following example:: {{<bpmn:error id="Error_1x1ymni" name="INVALID_DATA" errorCode="1231" camunda:errorMessage="The data provided is invalid" />}} * An error start event which uses {{camunda:errorCodeVariable="foo"}} ** When** The end event is executed ** Then ** The start event is triggered and after executing it, the variable {{foo}} contains the value "The data provided is invalid". ---- Previous description It is possible to define a BPMN Error Throw Event with an error message in the Modeler. However, the error message is not parsed by the engine and is lost. This should be made possible. Hint: This is where the parsing happens: https://github.com/camunda/camunda-bpm-platform/blob/1ee1f47ce32cb13b30852522c1415bbce7c96c6d/engine/src/main/java/org/camunda/bpm/engine/impl/bpmn/parser/BpmnParse.java#L417-L434 The {{Error}} class is used, which doesn't contain any message properties. |
New:
*Scenario:*
A user has two different Error End Events, each referencing a different {{<error />}} and a "catch-all" error start event in an event subprocess. Since the start event can catch two different errors, the user wants to reason about which error has been caught by the start event by storing error code and error message as variables. While it is currently possible to specify an error message when throwing an error from delegation code with new {{BpmnError(code, message)}} it is not possible to do so when defining the error end event. *Given:* * An error end event which references a a BPMN Error definition with {{camunda:errorMessage}} defined as in the following example:: {{<bpmn:error id="Error_1x1ymni" name="INVALID_DATA" errorCode="1231" camunda:errorMessage="The data provided is invalid" />}} * An error start event which uses {{camunda:errorCodeVariable="foo"}} *When* The end event is executed *Then* The start event is triggered and after executing it, the variable {{foo}} contains the value "The data provided is invalid". ---- Previous description It is possible to define a BPMN Error Throw Event with an error message in the Modeler. However, the error message is not parsed by the engine and is lost. This should be made possible. Hint: This is where the parsing happens: https://github.com/camunda/camunda-bpm-platform/blob/1ee1f47ce32cb13b30852522c1415bbce7c96c6d/engine/src/main/java/org/camunda/bpm/engine/impl/bpmn/parser/BpmnParse.java#L417-L434 The {{Error}} class is used, which doesn't contain any message properties. |
| Description |
Original:
*Scenario:*
A user has two different Error End Events, each referencing a different {{<error />}} and a "catch-all" error start event in an event subprocess. Since the start event can catch two different errors, the user wants to reason about which error has been caught by the start event by storing error code and error message as variables. While it is currently possible to specify an error message when throwing an error from delegation code with new {{BpmnError(code, message)}} it is not possible to do so when defining the error end event. *Given:* * An error end event which references a a BPMN Error definition with {{camunda:errorMessage}} defined as in the following example:: {{<bpmn:error id="Error_1x1ymni" name="INVALID_DATA" errorCode="1231" camunda:errorMessage="The data provided is invalid" />}} * An error start event which uses {{camunda:errorCodeVariable="foo"}} *When* The end event is executed *Then* The start event is triggered and after executing it, the variable {{foo}} contains the value "The data provided is invalid". ---- Previous description It is possible to define a BPMN Error Throw Event with an error message in the Modeler. However, the error message is not parsed by the engine and is lost. This should be made possible. Hint: This is where the parsing happens: https://github.com/camunda/camunda-bpm-platform/blob/1ee1f47ce32cb13b30852522c1415bbce7c96c6d/engine/src/main/java/org/camunda/bpm/engine/impl/bpmn/parser/BpmnParse.java#L417-L434 The {{Error}} class is used, which doesn't contain any message properties. |
New:
*Scenario:*
A user has two different Error End Events, each referencing a different {{<error />}} and a "catch-all" error start event in an event subprocess. Since the start event can catch two different errors, the user wants to reason about which error has been caught by the start event by storing error code and error message as variables. While it is currently possible to specify an error message when throwing an error from delegation code with new {{BpmnError(code, message)}} it is not possible to do so when defining the error end event. *Given:* * An error end event which references a a BPMN Error definition with {{camunda:errorMessage}} defined as in the following example:: {{<bpmn:error id="Error_1x1ymni" name="INVALID_DATA" errorCode="1231" camunda:errorMessage="The data provided is invalid" />}} * An error start event which uses {{camunda:errorCodeVariable="foo"}} *When* The end event is executed *Then* The start event is triggered and after executing it, the variable {{foo}} contains the value "The data provided is invalid". ---- Previous description It is possible to define a BPMN Error Throw Event with an error message in the Modeler. However, the error message is not parsed by the engine and is lost. This should be made possible. Hint: This is where the parsing happens: https://github.com/camunda/camunda-bpm-platform/blob/1ee1f47ce32cb13b30852522c1415bbce7c96c6d/engine/src/main/java/org/camunda/bpm/engine/impl/bpmn/parser/BpmnParse.java#L417-L434 The {{Error}} class is used, which doesn't contain any message properties. |
| Description |
Original:
*Scenario:*
A user has two different Error End Events, each referencing a different {{<error />}} and a "catch-all" error start event in an event subprocess. Since the start event can catch two different errors, the user wants to reason about which error has been caught by the start event by storing error code and error message as variables. While it is currently possible to specify an error message when throwing an error from delegation code with new {{BpmnError(code, message)}} it is not possible to do so when defining the error end event. *Given:* * An error end event which references a a BPMN Error definition with {{camunda:errorMessage}} defined as in the following example:: {{<bpmn:error id="Error_1x1ymni" name="INVALID_DATA" errorCode="1231" camunda:errorMessage="The data provided is invalid" />}} * An error start event which uses {{camunda:errorCodeVariable="foo"}} *When* The end event is executed *Then* The start event is triggered and after executing it, the variable {{foo}} contains the value "The data provided is invalid". ---- Previous description It is possible to define a BPMN Error Throw Event with an error message in the Modeler. However, the error message is not parsed by the engine and is lost. This should be made possible. Hint: This is where the parsing happens: https://github.com/camunda/camunda-bpm-platform/blob/1ee1f47ce32cb13b30852522c1415bbce7c96c6d/engine/src/main/java/org/camunda/bpm/engine/impl/bpmn/parser/BpmnParse.java#L417-L434 The {{Error}} class is used, which doesn't contain any message properties. |
New:
*Scenario:*
A user has two different Error End Events, each referencing a different {{<error />}} and a "catch-all" error start event in an event subprocess. Since the start event can catch two different errors, the user wants to reason about which error has been caught by the start event by storing error code and error message as variables. While it is currently possible to specify an error message when throwing an error from delegation code with new {{BpmnError(code, message)}} it is not possible to do so when defining the error end event. *Given:* * An error end event which references a a BPMN Error definition with {{camunda:errorMessage}} defined as in the following example:: {{<bpmn:error id="Error_1x1ymni" name="INVALID_DATA" errorCode="1231" camunda:errorMessage="The data provided is invalid" />}} * An error start event which uses {{camunda:errorCodeVariable="foo"}} *When* The end event is executed *Then* The start event is triggered and after executing it, the variable {{foo}} contains the value "The data provided is invalid". ---- Previous description It is possible to define a BPMN Error Throw Event with an error message in the Modeler. However, the error message is not parsed by the engine and is lost. This should be made possible. Hint: This is where the parsing happens: https://github.com/camunda/camunda-bpm-platform/blob/1ee1f47ce32cb13b30852522c1415bbce7c96c6d/engine/src/main/java/org/camunda/bpm/engine/impl/bpmn/parser/BpmnParse.java#L417-L434 The {{Error}} class is used, which doesn't contain any message properties. |
| Description |
Original:
*Scenario:*
A user has two different Error End Events, each referencing a different {{<error />}} and a "catch-all" error start event in an event subprocess. Since the start event can catch two different errors, the user wants to reason about which error has been caught by the start event by storing error code and error message as variables. While it is currently possible to specify an error message when throwing an error from delegation code with new {{BpmnError(code, message)}} it is not possible to do so when defining the error end event. *Given:* * An error end event which references a a BPMN Error definition with {{camunda:errorMessage}} defined as in the following example:: {{<bpmn:error id="Error_1x1ymni" name="INVALID_DATA" errorCode="1231" camunda:errorMessage="The data provided is invalid" />}} * An error start event which uses {{camunda:errorCodeVariable="foo"}} *When* The end event is executed *Then* The start event is triggered and after executing it, the variable {{foo}} contains the value "The data provided is invalid". ---- Previous description It is possible to define a BPMN Error Throw Event with an error message in the Modeler. However, the error message is not parsed by the engine and is lost. This should be made possible. Hint: This is where the parsing happens: https://github.com/camunda/camunda-bpm-platform/blob/1ee1f47ce32cb13b30852522c1415bbce7c96c6d/engine/src/main/java/org/camunda/bpm/engine/impl/bpmn/parser/BpmnParse.java#L417-L434 The {{Error}} class is used, which doesn't contain any message properties. |
New:
*Scenario:*
A user has two different Error End Events, each referencing a different {{<error />}} and a "catch-all" error start event in an event subprocess. Since the start event can catch two different errors, the user wants to reason about which error has been caught by the start event by storing error code and error message as variables. While it is currently possible to specify an error message when throwing an error from delegation code with new {{BpmnError(code, message)}} it is not possible to do so when defining the error end event. *Given:* * An error end event which references a BPMN Error definition with {{camunda:errorMessage}} defined as in the following example:: {{<bpmn:error id="Error_1x1ymni" name="INVALID_DATA" errorCode="1231" camunda:errorMessage="The data provided is invalid" />}} * An error start event which uses {{camunda:errorMessageVariable="foo"}} *When* The end event is executed *Then* The start event is triggered and after executing it, the variable {{foo}} contains the value "The data provided is invalid". ---- Previous description It is possible to define a BPMN Error Throw Event with an error message in the Modeler. However, the error message is not parsed by the engine and is lost. This should be made possible. Hint: This is where the parsing happens: https://github.com/camunda/camunda-bpm-platform/blob/1ee1f47ce32cb13b30852522c1415bbce7c96c6d/engine/src/main/java/org/camunda/bpm/engine/impl/bpmn/parser/BpmnParse.java#L417-L434 The {{Error}} class is used, which doesn't contain any message properties. |
nikola.koevski you write that "It is possible to define a BPMN Error Throw Event with an error message in the Modeler." I did not find that feature. Where do you define the error message for a error throw event in the modeler?