Camunda Modeler supports BPMN Errors triggered via RPA Bridge

This is an epic issue which may be broken down into multiple tasks, if needed

What should we do?

As part of the April CamBPM release, the RPA Bridge will support the triggering of BPMN errors. This shall be supported by the Camunda Modeler.

An example looks like this:

    <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="CamundaErrorEventDefinition1" errorRef="Error_0x9vl7b" expression="${true}" />
        <camunda:errorEventDefinition id="CamundaErrorEventDefinition2" errorRef="Error_0x9vl7c" expression="${processVar}" />
      </bpmn:extensionElements>
      <bpmn:incoming>Flow_04k3izd</bpmn:incoming>
      <bpmn:outgoing>Flow_1s764or</bpmn:outgoing>
    </bpmn:serviceTask>

In particular we need to (see child issues for more details):

Priority 1

• Improve existing bpmn-js-properties-panel UI for eventDefinitions. See issue for details
• Support camunda:errorEventDefinition for external ServiceTasks in Camunda Moddle
• Implement new UI component supporting camunda:errorEventDefinition for external ServiceTasks. See issue for details
• Support camunda:errorEventDefinition for external ServiceTasks with ElementTemplates
  • Decide a concept, how camunda:errorEventDefinition can be configured using ElementTemplates (See https://miro.com/app/board/o9J_lZ7EwN0=/ and respective issues)
  • Allow scopes to be an Array (rather than an Object as it is currently). Ensure backwards compatability (ie. still be able to scopes being an Object) see issue for details
  • Support global entity bpmn:Error by adding new scoped binding type. See issue for details
  • Implement new element template binding camunda:errorEventDefinition which allows to link an bpmn:error using the errorRef property see issue for details
  • Adjust the elementTemplates jsonSchema to ensure compatibility (array scopes, error scopes, error event definition binding). See issue for details.
  • Support the transfer of all attributes on copy/pasting a service task defining a camunda:ErrorEventDefinition. (See issue for details)
  • Ensure the removal of camunda:ErrorEventDefinition-related attributes when changing the service task type from external to any other. (See issue for details)
• Update element templates docs (https://github.com/camunda/camunda-modeler/issues/2161)
• Release + integrate element-templates-json-schema@0.3.0

Priority 2

• Allow the reorder of camunda:errorEventDefinitionss of a given serviceTask by adding a “dragging” features for the list of collapsbiles
• Adjust the elementTemplates jsonSchema
• Add support for all global entites (based on the concept established with bpmn:Error
• Add support for all eventDefinitions (based on the concept established with camunda:errorEventDefinition

Why should we do it?

The Camunda Modeler shall support the BPMN Error Trigger via RPA Bridge use case. See https://jira.camunda.com/browse/CAM-12040 for the CamBPM implementation.

Context CamBPM implementation: https://jira.camunda.com/browse/CAM-12040 Concept-board https://miro.com/app/board/o9J_lZ7EwN0=/

[MaxTru]

Integration Test with Cawemo Team

30.03.2021

Scope

(See [sep. issue] for integration test with platform team)

Setup

• Camunda Modeler nightly from 30.03.2021
• Cawemo Staging env. as of 30.03.2021 (Enterprise Beta)
• Cloud Connect 3.0.0

Test Cases

No.	Case	Result
1	Template with single error: (1) can be applied (2) all values present (3) validation is the same	✔️
2	Template with single error updated: (1) update dialog is offered (2) update works	✔️
3	Template with multiple errors: (1) can be applied (2) all values present (3) validation is the same	✔️
4	Template with multiple errors updated: (1) update dialog is offered (2) update works	✔️

Evaluation

• Integration Test completed successfully
• 1 bug found: restored milestones will lead to duplicate id+version combination (hence yield error in the Modeler). See issue: https://github.com/camunda/cawemo/issues/7599

[MaxTru]

Could you @MaxTru give this a final review and close this issue if we’re done?

Will do