Bug 1189454 - Multiple-Instance Loop Characteristics and process variables are not linked
Summary: Multiple-Instance Loop Characteristics and process variables are not linked
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Eclipse Tooling
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Kris Verlaenen
QA Contact: Jozef Marko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-05 11:24 UTC by Jozef Marko
Modified: 2020-03-27 19:45 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 19:45:11 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
process and screenshots (510.46 KB, application/zip)
2015-03-31 12:16 UTC, Jozef Marko
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Eclipse Project 459209 0 None None None Never

Description Jozef Marko 2015-02-05 11:24:35 UTC
See the linked eclipse bugzilla.

Comment 1 Robert (Bob) Brodt 2015-02-12 16:30:34 UTC
Fixed. See linked eclipse BZ.

Comment 3 Jozef Marko 2015-02-16 11:37:01 UTC
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.

Comment 4 Jozef Marko 2015-03-31 12:16:41 UTC
Created attachment 1008991 [details]
process and screenshots

Comment 5 Jozef Marko 2015-03-31 12:23:40 UTC
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.

Comment 6 Robert (Bob) Brodt 2015-06-16 12:28:08 UTC
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?

Comment 7 Jozef Marko 2015-06-17 05:52:59 UTC
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.

Comment 8 Robert (Bob) Brodt 2015-06-17 13:51:04 UTC
Kris, do you know if MI iterators even need a data type in jBPM?

Comment 9 Robert (Bob) Brodt 2015-06-18 23:26:55 UTC
I've made some fixes to allow editing of MI iterators, this will be in builds 1.1.4.20150618* for Luna and Mars

Comment 10 Jozef Marko 2015-06-24 10:50:50 UTC
Fix looks good on BPMN2 Modeler 1.1.4.201506182307.

Comment 11 Jozef Marko 2015-09-16 07:45:56 UTC
Verified on:
jbds-9.0.0.CR1_jbdsis-9.0.0.Alpha1
BPMN2 Modeler - 1.2.1.201508191851


Note You need to log in before you can comment on or make changes to this bug.