Bug 1189454
| Summary: | Multiple-Instance Loop Characteristics and process variables are not linked | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Jozef Marko <jomarko> | ||||
| Component: | Eclipse Tooling | Assignee: | Kris Verlaenen <kverlaen> | ||||
| Status: | CLOSED EOL | QA Contact: | Jozef Marko <jomarko> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 6.1.0 | CC: | jomarko, kverlaen | ||||
| 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:45:11 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: |
|
||||||
|
Description
Jozef Marko
2015-02-05 11:24:35 UTC
Fixed. See linked eclipse BZ. Test concerning this issue: https://github.com/jbosstools/jbosstools-integration-stack-tests/blob/master/tests/org.jboss.tools.bpmn2.ui.bot.test/src/org/jboss/tools/bpmn2/ui/bot/complex/test/testcase/ComplexMultiInstanceLoopCharacteristicsTest.java Input Data collection for MultiInstanceSubProcess can be only variable from local process variables. Verified on BPMN2 Modeler 1.1.2.201502121708. Fix not included in jbds-8.0.2.GA_jbdsis-8.0.0.CR2. Created attachment 1008991 [details]
process and screenshots
Please open the bpmn process from the attachment. I have successfully select process variable(VariableTwo) where is desired collection. But if I want to specify iterator, I obtain error tagged with red (1) in problemsView.png. I can specify data type of iterator if I double-click to line, where is error (1) displayed. But there should be option to specify iterator data type in area tagged with red (2) in file properties.png. Actually, the data type for the iterator should automatically be set to the same data type as the collection, no? In this case, the user should not have to change the data type of the iterator...unless it is possible that the engine does type conversion from collection items to iterator type. For example providing a collection of numbers formatted as Strings would allow an Integer iterator to be used, and the engine would convert the Strings in the collection to Integer on-the-fly. Is this possible? I think, It is good idea to set Iterator data type to data type of collection. But can't declare collection variable like java.util.ArrayList<Integer>. What I can declare is java.util.ArrayList. I don't know if engine can do type inferring during runtime. The same for type conversion. I am not sure about it. I am not engine developer. I think, Kris should know the answer. Kris, do you know if MI iterators even need a data type in jBPM? I've made some fixes to allow editing of MI iterators, this will be in builds 1.1.4.20150618* for Luna and Mars Fix looks good on BPMN2 Modeler 1.1.4.201506182307. Verified on: jbds-9.0.0.CR1_jbdsis-9.0.0.Alpha1 BPMN2 Modeler - 1.2.1.201508191851 |