Bug 1089341 - Guided rule editor: rule cannot be saved when using expression editor
Summary: Guided rule editor: rule cannot be saved when using expression editor
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.0.2
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ER3
: 6.0.2
Assignee: Toni Rikkola
QA Contact: Zuzana Krejčová
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-18 13:30 UTC by Zuzana Krejčová
Modified: 2015-01-05 10:59 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-06 19:54:06 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
screenshot - rule and modal (58.07 KB, image/png)
2014-04-18 13:30 UTC, Zuzana Krejčová
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1051059 0 unspecified CLOSED Guided rule editor expression editor broken on the right side of an operator 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1176165 0 unspecified CLOSED Guided Rule Editor: Too much recursion when using an expression 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1176554 0 high CLOSED Guided Rule Editor: Expression editor not available for a fact 2021-02-22 00:41:40 UTC

Internal Links: 1051059 1176165 1176554

Description Zuzana Krejčová 2014-04-18 13:30:27 UTC
Created attachment 887580 [details]
screenshot - rule and modal

Description of problem:
If you use the expression editor to build a field constraint, the guided rule cannot be saved. You always get an Error modal with message like this:
'Fact type "Fact1" has a field "field1" that has an operator set, but no value. Please add a value or remove the operator.'
This happens no matter if the expression is valid or not.

(Apart from this little bug, that safeguard is a very nice feature.)


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


Steps to Reproduce:
1. In a guided rule, add some 'Fact1' to the 'when' section, bind it to variable 'f1'.
2. Add another 'Fact1', and add a constraint on some 'field1' to it.
3. Select operator (e.g. 'equal to'), choose the expression editor to enter the 'value'.
4. Choose 'f1', then 'field1'.
5. Validate and try to save the rule.


Actual results:
Validation is okay, saving results in Error modal with message 'Fact type "Fact1" has a field "field1" that has an operator set, but no value. Please add a value or remove the operator.'
Rule is not saved.


Expected results:
Rule is saved (and validation results are still okay).

Comment 2 Zuzana Krejčová 2014-06-03 08:29:49 UTC
Works with ER3.


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