Bug 847381
| Summary: | JBPM designer: ConditionType property on a sequence flow not saved | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | Phil Simpson <psimpson> | ||||
| Component: | jBPM 5 | Assignee: | Kris Verlaenen <kverlaen> | ||||
| Status: | VERIFIED --- | QA Contact: | |||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | BRMS 5.3.0.GA | ||||||
| Target Milestone: | ER2 | ||||||
| Target Release: | BRMS 5.3.1 GA | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
Previously, it was possible for users to set a condition type on sequence flows in the Process Designer; however, the condition type was not stored on the process when the process was saved. This has been resolved by removing the ability to set a condition type.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | Type: | Bug | |||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
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. thanks! Verified for BRMS 5.3.1 ER3, designer 2.3.1-DEV Property "ConditionType" is missing in Properties Bar. |
Created attachment 603615 [details] DefaultFlow ConditionType 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): How reproducible: Always 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 Actual results: ConditionType is set to standard, and the hash mark across the displayed sequence flow has disappeared Expected results: The ConditionType is retained as DefaultFlow Additional info: