Red Hat Bugzilla – Bug 1286912
Process Designer does not manage Intermediate CompensateEvent
Last modified: 2016-07-31 21:11:48 EDT
Created attachment 1100717 [details] problematic business process with Intermediate CompensateEvent Description of problem: In Business-Central, Process Designer can not manage Intermediate CompensateEvent correctly. same business process is displayed correctly with JBDS8. Version-Release number of selected component (if applicable): 6.1.x. How reproducible: import the attached sample bpmn2 file which is included in source code archive. i.e. jbpm-6.2.0.Final-redhat-4/jbpm-bpmn2/src/test/resources/compensation/BPMN2-Compensation-IntermediateThrowEvent.bpmn2 Steps to Reproduce: 1. login Business Central and create business process 2. import BPMN2-Compensation-IntermediateThrowEvent.bpmn2 3. Actual results: diagram gets garbled and the following errors are shown. - Process '' [xxxxx.aaaa]: Start node '' [1] has no outgoing connection. - Process '' [xxxxx.aaaa]: Process has no end node. Expected results: diagram is displayed correctly without any error/warning Additional info:
master PR https://github.com/droolsjbpm/jbpm-designer/pull/114 6.3.x PR: https://github.com/droolsjbpm/jbpm-designer/pull/115
master :https://github.com/droolsjbpm/jbpm-designer/commit/2958d53d05681ff376c125191d518361337a42cc 6.3.x: https://github.com/droolsjbpm/jbpm-designer/commit/a1180cd979a25ef44f1fadf0605200a9fb053adc
Just FYI - the attached process does not include bpmi info and cannot be just imported into designer as it is. You can recreate it quickly with designer itself to test if needed.
The process has to be imported via git, not the import feature of the Designer (I suppose that is what the original report meant) - in both 6.1.x and 6.2.1. That should be okay. The process now doesn't open in the full Designer, but in an XML editor, where it is editable - since it is missing BPMNDI information, as Tihomir pointed out. This is a big improvement over 6.1.x and I think a result of other BZs as well. The server log no longer contains the errors.