Bug 1268812
| Summary: | Validation of sequence flow condition expression doesn't work for the first parameter when comparing a numeric variable | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Jiri Locker <jlocker> | ||||
| Component: | jBPM Designer | Assignee: | Tihomir Surdilovic <tsurdilo> | ||||
| Status: | CLOSED EOL | QA Contact: | Jiri Locker <jlocker> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 6.2.0 | CC: | kverlaen | ||||
| Target Milestone: | --- | Keywords: | Regression | ||||
| 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:05:00 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: |
|
||||||
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: