Bug 1189365

Summary:	isExecutable="false" should not be removed from BPMN file by BPMN 2 Diagram Editor
Product:	[Retired] JBoss BPMS Platform 6	Reporter:	ksuzumur
Component:	Eclipse Tooling	Assignee:	Kris Verlaenen <kverlaen>
Status:	CLOSED EOL	QA Contact:	Jozef Marko <jomarko>
Severity:	medium	Docs Contact:
Priority:	low
Version:	6.0.3	CC:	jomarko, rrajasek
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-27 20:10:35 UTC	Type:	Feature Request
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description ksuzumur 2015-02-05 06:22:48 UTC

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:

Comment 1 Kris Verlaenen 2015-02-05 14:49:17 UTC

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.

Comment 2 Jozef Marko 2015-02-13 12:41:06 UTC

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

Comment 3 Robert (Bob) Brodt 2015-02-26 16:32:39 UTC

This should be fixed now in 1.0.4.Final and 1.1.2.Final of BPMN2 Modeler.

Comment 4 Jozef Marko 2015-04-02 10:43:58 UTC

Verified on jbds-8.1.0.CR1_jbdsis-8.0.1.CR1 - BPMN2 Modeler 1.1.2.Final