BPMN Errors can be viewed (summary) and deleted individually

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

What should we do?

Currently the user might create BPMN errors (e.g., using Error Boundary Events) (or equal concept: messages, signals, …). These created errors (again, or messages, signals, …) will then exist on a global scope and can not be (I) viewed or (II) deleted (unless the user goes into the XML view).

With this epic we want to allow this:

• Have a design concept, that defines how global BPMN Errors may be viewed and potentially deleted on diagram root level
• Implement the BPMN Error overview feature
• Implement the “Delete BPMN Error” feature
• For the entire concept: keep in mind that this concept is in a first step implemented for BPMN errors, but should in principle also be useable for other global entities (e.g., messages, signals).

Why should we do it?

There are multiple reasons why we need this.

• Various users requesting it (see #136 #1930)
• It supports the RPA use case (where in the future also the bridge will send BPMN Errors)

Also related to https://github.com/camunda/camunda-modeler/issues/861 and https://github.com/camunda/camunda-modeler/issues/1554

[andreasgeier]

FYI - I consider this in the UI Architecture topic.

[MaxTru]

Hi @felix-mueller,

@andreasgeier already prepared a concept for it as part of the reworked overall UI. It basically features a seperate DataView which allows to view (and edit/delete) all global entities (such as errors, messages, …).

Implementing this concept however requires some dedicated OKR capacities, and from my understanding this is not the most burning topic for Q4. Can you please check with @volkergersabeck ?

If this is a burning issue for cloud and we don’t plan this for Q4, then one could implement as a temporary plan B solution a behavior, that would delete all unreferenced entities (e.g., after every save).

Hope these hints help.