Red Hat Bugzilla – Bug 1189365
isExecutable="false" should not be removed from BPMN file by BPMN 2 Diagram Editor
Last modified: 2018-01-30 07:37:35 EST
Description of problem: isExecutable="false" should not be removed from BPMN file by BPMN 2 Diagram Editor. When isExecutable Attribute value is unchecked in BPMN 2 Diagram Editor, isExecutable="true" is removed from the BPMN file. It means isExecutable="false". In current release BPMS6.0.3, the attribute is not used in jBPM 6 to define some behavior. The customer requirement is that if isExecutable Attribute is used for some behavior in future release, they want to check the isExecutable Attribute value(true or false) in XML. Version-Release number of selected component (if applicable): BPMN 6.0.3 JBDS 8.0 Early Access BPMN2 Modeler - Diagram Editor 1.1.1.201412181844 BPMN2 Modeler - Diagram Editor 1.1.2.201501301814 How reproducible: Uncheck "Is Executable" Attribute in Process -> Attributes Actual results: When isExecutable Attribute value is unchecked in BPMN 2 Diagram Editor, isExecutable="true" is removed from the BPMN file. Expected results: When isExecutable Attribute value is unchecked in BPMN 2 Diagram Editor, isExecutable="false" is set in the BPMN file. Additional info:
Bob, the BPMN2 XSD defines this as an optional attribute with no default, so I guess there would be value in allowing isExecutable="false" in the XML.
Test concerning this issue: https://github.com/jbosstools/jbosstools-integration-stack-tests/blob/master/tests/org.jboss.tools.bpmn2.ui.bot.test/src/org/jboss/tools/bpmn2/ui/bot/complex/test/testcase/ComplexSpecialCharactersAndLenghtsTest.java
This should be fixed now in 1.0.4.Final and 1.1.2.Final of BPMN2 Modeler.
Verified on jbds-8.1.0.CR1_jbdsis-8.0.1.CR1 - BPMN2 Modeler 1.1.2.Final