Bug 975922 - GRE constraint operator list box problems when re-opening file
Summary: GRE constraint operator list box problems when re-opening file
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.0.0
Hardware: Unspecified
OS: Mac OS
high
high
Target Milestone: DR2
: 6.1.0
Assignee: manstis
QA Contact: Jiri Locker
URL:
Whiteboard:
: 994476 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-19 15:31 UTC by Jeff DeLong
Modified: 2020-03-27 19:47 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-03-27 19:47:25 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
GRE (1.34 MB, image/tiff)
2013-06-19 15:31 UTC, Jeff DeLong
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1000464 0 unspecified CLOSED Guided Editor doesn't work with 'contains' and 'excludes' operators 2021-02-22 00:41:40 UTC

Internal Links: 1000464

Description Jeff DeLong 2013-06-19 15:31:38 UTC
Created attachment 763020 [details]
GRE

Description of problem:

GRE constraint operator list box problems when re-opening file.  When I re-open the rule that the constraint is no longer less than but has reverted to --- please choose ---
And the drop down box only has four choices

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


How reproducible:


Steps to Reproduce:
1.Create a GRE rule
2.Add a condition with a constraint with a literal value, for example field less than value
3.Save the file and re-open it

Actual results:

--- please choose ---

Expected results:

less than

Additional info:

Comment 2 Lukáš Petrovický 2013-07-28 17:30:14 UTC
This has been wrongly filed for BPMS. Moving to BRMS.

Comment 4 Jiri Locker 2013-08-22 08:13:03 UTC
*** Bug 994476 has been marked as a duplicate of this bug. ***

Comment 5 Jiri Locker 2013-08-22 08:15:51 UTC
This affects numerical field constraints. For a quick demonstration, open Bankruptcy history in mortgages project.

Comment 6 Jiri Locker 2013-08-26 19:29:39 UTC
String fields are affected too:
- When using "greater than" or other comparing operators or "matches" and "sounds like", the select box is reset to "--- please choose ---" after reopening the rule.

With both String and numerical fields:
- When using "equals to" the operator is reloaded correctly however the select box options are reduced to "equals to", "not equals to", "is null" and "is not null".
- "is null" after reopening: field [equal to] [Choose ...] (expression builder), similarly with "is not null".

In most cases the "cursed" operator usage is indicated by alert "Are you sure you want to discard unsaved data?" showing up even after saving the changes.

Comment 8 Jiri Locker 2013-09-26 15:17:57 UTC
Fixed in ER3.

Comment 12 Jiri Locker 2013-10-22 16:57:30 UTC
The issue recurred in ER4. It now affects <= and >= operators.

Comment 14 Jiri Locker 2013-11-29 17:42:47 UTC
Fixed in ER5.

Comment 15 Zuzana Krejčová 2014-06-03 10:26:41 UTC
This happens again with Number.

Steps to reproduce:
1. Add Number to [when] section, add restriction using the expression editor.
2. Choose intValue.
3a. Choose 'greater than' operator. OR
3b. Choose 'equals' operator.
4. Type in a literal value, save, reopen.

For 3a, the operator is reset to '--- please choose ---', for 3b, operator stays the same. In both cases, operator options are reduced to 'equals to', 'not equals to', 'is null' and 'is not null'.

Comment 17 Jiri Locker 2014-09-11 13:07:37 UTC
Scenario described in comment 15 now works as expected.


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