Description of problem: I compared the Web BPMN Designer to Eclipse BPMN Designer and BPMN specification and here are the things which needs to improve: - start message not interruption event has wrong image - there should be a letter icon inside - start escalation not interruption event has wrong image - there should be an escalation icon inside - start signal not interruption event has wrong image - there should be an signal icon inside - for error start event there should not be option "Is Interrupting" - for compensation start event there should not be option "Is Interrupting" missing event: - cancel boundary intermediate event - there is an end cancel event, so we should be able to catch it - compensation throw intermediate event Create new category for Boundary Events as it is in Eclipse BPMN Designer. I set the blocker flag because of the missing events. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 892890 [details] Process with link events I noticed another important problem. It is not possible to add Link events and configure them. As you can see from the attached process definition, link events are supported and looks well but I cannot add them from the palette.
Please ignore the previous comment, it is for another BZ 1091374 This one is supposed to be here: I noticed another important problem. It is not possible to add Link events and configure them. Also when I import a process containing the link events, the process definition is not opened due to UnsupportedOperationException: Event definition not supported: org.eclipse.bpmn2.impl.LinkEventDefinitionImpl
With Bob Brodt in the BZ 1150074, we have found out that "Is Interrupting" attribute should be available ONLY in a start event which is in an event sub-processes. Currently BPMS 6.1.0.DR3 has this attribute in every intermediate and start event. Instead "CancelActivity" attribute should be visible in every intermediate boundary event. For details, see "Table 10.92 – Possible Values of the cancelActivity Attribute" in the BPMN2 specification (e.g. error boundary event should not have the "cancelActivity" attribute visible or have it read-only because it should be always true). Thanks