Bug 846487
| Summary: | jBPM Designer corrupts diagrams with ambiguous gateways | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | Phil Simpson <psimpson> | ||||
| Component: | jBPM 5 | Assignee: | Kris Verlaenen <kverlaen> | ||||
| Status: | VERIFIED --- | QA Contact: | |||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | BRMS 5.3.0.GA | ||||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
Ambiguously placed gateway nodes within a process diagram caused errors in which Process Designer was no longer able to reopen the diagram. This issue caused a technical error in which the user was unable to open or edit the process model. This has been resolved by showing validation errors with ambiguous gateway nodes and allowing Process Designer to open the invalid process.
|
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 the designer part in 2.3.x branch. This will become testable once https://bugzilla.redhat.com/show_bug.cgi?id=827002 is closed as the Guvnor fix for that is needed here as well. verified for brms-standalone 5.3.1 ER1 Validation shows errors and user can save/open the (invalid) process. Thank you for the Release Notes information. - Doug |
Created attachment 602873 [details] Unrecoverable BPMN2 diagram Description of problem: If a diagram contains a gateway whose direction cannot be determined (i.e an incomplete diagram under development), the bpmn2 that is saved cannot be reopened, thus rendering the diagram unrecoverable. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1.Create a new BPMN2 diagram 2.Add Start Event, gateway, end event in sequence (see attached) 3.Save the diagram 4. Attempt to reopen the diagram Actual results: 400 Sorry, a technical error occurred. Please contact a system administrator. Expected results: diagram should open normally Additional info: