Description of problem: This BugZilla is raised to address the issue mentioned in this JIRA [1] so that the relevant fix can be incorporated in the future releases of JBoss Enterprise BRMS. Here is the issue description for reference: The 'DefaultGateway' property of a Diverging Inclusive OR generates the following output: <bpmn2:inclusiveGateway ... drools:dg="X" gatewayDirection="Diverging"> The expected format for jBPM5 should be: <bpmn2:inclusiveGateway ... default="X" gatewayDirection="Diverging"> The problem here is not only the xml attribute being used but within the Designer the user should be able to set the id of the default workflow, which is something he doesn't know in advance. The editor for this property should show a list of all the outgoing flows of the gateway (maybe showing their names) so the user can easily select the one he wants. [1] https://issues.jboss.org/browse/JBPM-3704 Version-Release number of selected component (if applicable): - jBPM5.2 - jBPM Designer Version: 2.3.1.GA How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: Workaround as suggested in the JIRA : Once the bpmn2 file is generated change the 'drools:dg' attribute for a 'default' attribute.
Tihomir Surdilovic <tsurdilo> made a comment on jira JBPM-3704 Updated the default selection to be a dynamic dropdown with sequence flow names and ids of all outgoing sequence flows of the gateway for easier selection.
Tihomir Surdilovic <tsurdilo> updated the status of jira JBPM-3704 to Resolved
Tihomir Surdilovic <tsurdilo> made a comment on jira JBPM-3704 desolved
Tihomir Surdilovic <tsurdilo> made a comment on jira JBPM-3704 resolved
https://github.com/droolsjbpm/jbpm-designer/commit/6e5bae53c
Please note that this issue is not fixed. The generated code still looks like: <bpmn2:inclusiveGateway ... drools:dg="X" name="" gatewayDirection="Diverging"> <!-- ... --> </bpmn2:inclusiveGateway> Moreover if I set the "DefaultGateway" parameter to some value and save the process then this value will not be present when the designer reloads. The value I have used is the same as the name of an outgoing connection.
Can you put steps to reproduce your issue? When doing a simple test it seems fine. Saving and re-opening process persists the default gateway selected by user. <bpmn2:exclusiveGateway ... default="_732C73F9-370E-4CE9-BA01-3226133513BA"> <bpmn2:incoming>_920D0EDF-A600-43CF-8358-478E93D55266</bpmn2:incoming> <bpmn2:outgoing>_732C73F9-370E-4CE9-BA01-3226133513BA</bpmn2:outgoing> <bpmn2:outgoing>_D9E80B18-0849-4DD6-ACCD-29660194466B</bpmn2:outgoing> </bpmn2:exclusiveGateway>
the editor is incorrect for inclusive gateways - putting back to assigned
fix for inclusive in designer master and 6.1.x branches: master - https://github.com/droolsjbpm/jbpm-designer/commit/e8c0182da3f816d61387e44be60dd90cf56ae724 6.1.x - https://github.com/droolsjbpm/jbpm-designer/commit/bc5646388
I think the commit needs to be backported also into 2.3.x branch, so it will end up in the patch.
fix in 2.3.x - https://github.com/droolsjbpm/jbpm-designer/commit/3e139c970d512ee594d5515b35f2a4a831626c76
Verified on latest patched binaries. Both attributes are now present (drools:dg and default).