Bug 1268812 - Validation of sequence flow condition expression doesn't work for the first parameter when comparing a numeric variable
Summary: Validation of sequence flow condition expression doesn't work for the first p...
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: jBPM Designer
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Tihomir Surdilovic
QA Contact: Jiri Locker
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-05 10:57 UTC by Jiri Locker
Modified: 2020-03-27 19:05 UTC (History)
1 user (show)

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


Attachments (Terms of Use)
Expected error message (33.29 KB, image/png)
2015-10-05 10:57 UTC, Jiri Locker
no flags Details

Description Jiri Locker 2015-10-05 10:57:22 UTC
Created attachment 1079906 [details]
Expected error message

Description of problem:
The condition expression editor generally doesn't allow a non-numeric parameter (including an empty value) when comparing a numeric variable. This validation stopped working for the first parameter, e.g. it allows expressions like (var => "", var between "" and 10).

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

How reproducible:
-

Steps to Reproduce:
1. Open a simple process.
2. Click canvas, in Properties panel bring up Variable definitions.
3. Define an integer variable named "intVar".
4. Select any sequence flow (arrow between two nodes), bring up Expression editor.
5. In the Editor tab, select "intVar" variable, select "is greater than" condition, do not provide any value.
6. Click Ok (or select the Script tab).

Actual results:
Validation doesn't detect the incorrect (empty) value, no error displayed.

Expected results:
Error message as illustrated on the attached screenshot (notice that validation works for the second parameter, so "between" condition with both parameters empty still fails the validation).

Additional info:


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