Red Hat Bugzilla – Bug 847381
JBPM designer: ConditionType property on a sequence flow not saved
Last modified: 2013-10-10 20:19:32 EDT
Created attachment 603615 [details]
Description of problem:
If a ConditionType of DefaultFlow is assigned to a sequence flow, it is not saved in the bpmn2, and the ConditionType reverts to Standard the next time the process diagram is opened.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Assign a ConditionType of DefaultFlow to a sequence flow in a bpmn2 diagram (see attached)
2.save & close the diagram
3.reopen the diagram
ConditionType is set to standard, and the hash mark across the displayed sequence flow has disappeared
The ConditionType is retained as DefaultFlow
Fixed in 2.3.x Designer branch. There is now only one condition type available ("None") which is the only one we use. Users are no longer able to change this property.
The select element for property "Condition Type" have 3 options: Conditional Flow, Default Flow, Standard.
If I choose Default Flow, Save and Close Asset, Open asset again, then Sequence flow loose value of "Condition Type" and is set to Standard.
For BRMS 5.3.1 ER1 and designer 2.3.1-DEV.
Nice catch - fixed in 2.3.x branch now, ConditionType property is no longer editable.
Verified for BRMS 5.3.1 ER3, designer 2.3.1-DEV
Property "ConditionType" is missing in Properties Bar.