Bug 1124755 - Implement editor for CollectionExpression of multi-instance sub process component
Summary: Implement editor for CollectionExpression of multi-instance sub process compo...
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: jBPM Designer
Version: 6.0.2
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Tihomir Surdilovic
QA Contact: Kirill Gaevskii
Depends On:
TreeView+ depends on / blocked
Reported: 2014-07-30 08:54 UTC by Anton Giertli
Modified: 2018-12-06 17:31 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed:
Type: Enhancement

Attachments (Terms of Use)

Description Anton Giertli 2014-07-30 08:54:39 UTC
Description of problem:

Currently user need to enter the value for CollectionExpression in the simple text field. This is quite error pron and in contradiction with other data editors which are present designer.

Documentation states the following:
The variable must be an array or be of the java.util.Collection type.

What I suggest is to implement some sort of drop down menu or other editor which will lists all the process variables which fulfils this condition.

Let's have following process variables defined:

myString: java.lang.String
myInteger: java.lang.Integer
myArray: java.lang.String[]
myList: java.util.List

In the multi-instance sub process component, following values would be available for selection for the CollectionExpression attribute:


Version-Release number of selected component (if applicable):

bpm 6.0.x
How reproducible:

Steps to Reproduce:
1. crate multi-instance sub process component in the designer
2. try to fill CollectionExpression value - no suggestions available

Actual results:
Editor for CollectionExpression is a text input.

Expected results:
Editor for CollectionExpression is a drop down menu or any sort of editor which will hold the list of appropriate values so user can choose without having to type it manually.

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