Bug 1120264 - gateway expression editor not show custom object fields
Summary: gateway expression editor not show custom object fields
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: jBPM Designer
Version: 6.0.2
Hardware: All
OS: All
medium
urgent
Target Milestone: ---
: ---
Assignee: Tihomir Surdilovic
QA Contact: Kirill Gaevskii
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-16 14:58 UTC by Jey
Modified: 2020-03-27 19:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 19:07:09 UTC
Type: Feature Request
Embargoed:


Attachments (Terms of Use)

Description Jey 2014-07-16 14:58:05 UTC
Description of problem:

exclusive Gateway expression editor not showing / listing fileds  and contraints on the process variable object. It shows only standard java type String , Integer etc.

Also, now showing any contraints for java.util date object.


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


How reproducible:

create simple flwo with exclusive gateway with process variable that should be custom obeject example Employ object with attribute Name (String),address (String), Id(Integer)

go to exclusive gate express editor - you will see only process variable and contraints field shows only "is null", doesn't list any fields on employee object

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Kris Verlaenen 2014-07-16 18:19:31 UTC
The expression editor only has limited scope, it only supports primitive datatypes and a selected set of operations on them.  For more complex constraints, users need to use the text editor to type the constraint themselves.

Comment 3 Tihomir Surdilovic 2014-12-12 13:56:29 UTC
The text-based editor is available by clicking on the "Script" tab on the expression editor. It's auto-complete feature (activated by ctrl-z) displays all available data objects as well.


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