Bug 1136162
| Summary: | Multi Instance Activity variable id set incorrectly via JBDS BPMN2 Editor | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Stelios Kousouris <stkousso> | ||||
| Component: | Eclipse Tooling | Assignee: | Kris Verlaenen <kverlaen> | ||||
| Status: | CLOSED EOL | QA Contact: | Jozef Marko <jomarko> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 6.0.2 | CC: | mbaluch | ||||
| 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 19:39:37 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: | |||||||
| Attachments: |
|
||||||
This has already been reported and was fixed in May, 2014. Please retest with version 1.1.0 of the editor, available here: http://download.eclipse.org/bpmn2-modeler/updates/luna/1.1.0/ Verified on JBDSIS 8.0.0.Alpha2. The ID is now correctly set to 'registrationItem'. |
Created attachment 933584 [details] BPMN2 Editor Multi-Instance Process Description of problem: The variable of a multi-instance subprocess does not get its ID set when created via the JBDS BPMN2 Editor. Version-Release number of selected component (if applicable): 6.0.2 How reproducible: Steps to Reproduce: Created a multi-instance subprocess via the JBDS JBPM Tooling and assigned the Collection to a variable "registrationItem" passing a List in. The local instance variable has been defined as : "registrationItem". However, the editor ONLY defines the name and not the ID in the underlying XML (see below) <bpmn2:multiInstanceLoopCharacteristics id="MultiInstanceLoopCharacteristics_1"> <bpmn2:loopDataInputRef>DataInput_1</bpmn2:loopDataInputRef> <bpmn2:inputDataItem xsi:type="bpmn2:tDataInput" id="DataInput_2" itemSubjectRef="_String" name="registrationItem"/> </bpmn2:multiInstanceLoopCharacteristics> The result is when I access "registrationItem" to get null. But when I manuall change the ID to "registrationItem" (see below) it now has a value. <bpmn2:multiInstanceLoopCharacteristics id="MultiInstanceLoopCharacteristics_1"> <bpmn2:loopDataInputRef>DataInput_1</bpmn2:loopDataInputRef> <bpmn2:inputDataItem xsi:type="bpmn2:tDataInput" id="registrationItem" itemSubjectRef="_String" name="registrationItem"/> </bpmn2:multiInstanceLoopCharacteristics> Additional info: When I change the ID and try the process works. However, if I modify and resave the process via the JBDS BPMN2 Editor the ID becomes again DataInput_2 so I had to change my references to "DataInput_2" for my scripts/assignements to work.