-
Sub-task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
-
None
The BPMN parser is able to parse error trigger definitions like
<bpmn:serviceTask id="ServiceTask_2" name="Generate quote" camunda:type="external" camunda:topic="RPA">
<bpmn:extensionElements>
<camunda:inputOutput>
<camunda:inputParameter name="productName">${product}</camunda:inputParameter>
<camunda:inputParameter name="count">${count}</camunda:inputParameter>
<camunda:inputParameter name="price">${price}</camunda:inputParameter>
<camunda:outputParameter name="pdfStorage">${pdfStorage}</camunda:outputParameter>
</camunda:inputOutput>
<camunda:properties>
<camunda:property name="bot" value="PDFQuoteGenerator" />
</camunda:properties>
<camunda:errorEventDefinition id="CamundaErrorEventDefinition" errorRef="Error_0x9vl7b" expression="${true}" />
</bpmn:extensionElements>
<bpmn:incoming>Flow_04k3izd</bpmn:incoming>
<bpmn:outgoing>Flow_1s764or</bpmn:outgoing>
</bpmn:serviceTask>
Hints:
- camunda:errorMessageVariable and camunda:errorCodeVariable are only evaluated when catching an error and are not supported for this use-case.
TODO: - Evaluate if it makes sense to implement this for all activities that can accept variables
- Primary Scope are External Tasks