Bug 1242410
| Summary: | Default attribute in exclusive gateway lost during BPMN2 import | |||
|---|---|---|---|---|
| Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Martin Weiler <mweiler> | |
| Component: | jBPM Designer | Assignee: | Tihomir Surdilovic <tsurdilo> | |
| Status: | CLOSED EOL | QA Contact: | Jozef Marko <jomarko> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 6.1.0 | CC: | kverlaen, mweiler | |
| Target Milestone: | ER1 | |||
| Target Release: | 6.2.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1242824 (view as bug list) | Environment: | ||
| Last Closed: | 2020-03-27 20:03:58 UTC | 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: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1242824 | |||
Hi Martin, are you able to reproduce this problem on a smaller scale (small business process)? The attached one is fairly large and the issue is reproducible (but very hard to debug due to the size of the process). I tried to reproduce this issue with a gateways with 1 incoming and 2 outgoing connections without success. Just wondering if you can. Thanks. Hi Tiho, I failed to reproduce with the samples from the jBPM tests as well. If I manage to find a smaller/simpler process that shows the same problems, I will let you know. Was able to reproduce on small scale. master commit: https://github.com/droolsjbpm/jbpm-designer/commit/253549601 6.3.x commit: https://github.com/droolsjbpm/jbpm-designer/commit/2535496010b07170474422053ce13031d92948a6 Attached process imported and attribute Default was preserved for exclusive gateways. |
Description of problem: After importing a process definition with an exclusive gateway, where one of the outgoing connections is marked as the default gateway, with no condition expression defined, the designer issues the following validation errors: "Split node 'L4 Sending' [29] does not have a constraint for Connection L4 Sending [type=DROOLS_DEFAULT]" Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Create a new process in the business-central designer 2. Import the attached BPMN2 file Actual results: Designer reports validation errors. Expected results: No validation errors related to the exclusive gateway. Additional info: Exclusive gateway definition *BEFORE* the import: <bpmn2:exclusiveGateway id="_33DDA623-C86C-4B00-A90E-9B803D416D61" drools:bgcolor="#f0e68c" drools:selectable="true" drools:bordercolor="#FF6600" drools:dg="No : _49C48C17-F4B9-44EA-ABC4-F1A239057A84" name="L4 Sending" gatewayDirection="Diverging" default="_49C48C17-F4B9-44EA-ABC4-F1A239057A84"> <bpmn2:incoming>_5941FF39-76E0-44D0-BD62-98C782420CFA</bpmn2:incoming> <bpmn2:outgoing>_B610EC4E-2A9A-4C6E-ACA9-09907F83EA81</bpmn2:outgoing> <bpmn2:outgoing>_49C48C17-F4B9-44EA-ABC4-F1A239057A84</bpmn2:outgoing> </bpmn2:exclusiveGateway> Note that the 'default' attribute contains the reference to one of the outgoing connections. Defintion *AFTER* the import (using view sources view): <bpmn2:exclusiveGateway id="_9B77EAFD-7EC6-44A6-99C3-7618750BD9ED" drools:bgcolor="#f0e68c" drools:selectable="true" drools:bordercolor="#FF6600" drools:dg="No : _49C48C17-F4B9-44EA-ABC4-F1A239057A84" name="L4 Sending" gatewayDirection="Diverging"> Note the missing 'default' attribute.