Bug 724635 (BRMS-543) - Add "is null" and "is not null" to drop-down in Guided Editor
Summary: Add "is null" and "is not null" to drop-down in Guided Editor
Keywords:
Status: CLOSED NEXTRELEASE
Alias: BRMS-543
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: unspecified
Version: 5.1.0 GA
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ---
: 5.1.0.PostGA
Assignee: Tihomir Surdilovic
QA Contact:
URL: http://jira.jboss.org/jira/browse/BRM...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-25 00:06 UTC by Alessandro Lazarotti
Modified: 2011-03-16 03:05 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-16 03:05:09 UTC
Type: Feature Request

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker BRMS-543 0 Major Closed Add "is null" and "is not null" to drop-down in Guided Editor 2013-04-19 14:33:29 UTC
Red Hat Issue Tracker GUVNOR-1172 0 Major Resolved Guided Editor: Add "is null" and "is not null" to drop-down 2013-04-19 14:33:30 UTC

Description Alessandro Lazarotti 2011-01-25 00:06:37 UTC 
Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000005ib7x&sfdc.override=1
securitylevel_name: Public

Currently the way to do this is by using formula or free form drl.
I know that Guided Editor is a Business Analyst tool, so "is null" and "is not null" may not be the right words.
Maybe "exists" and "not exists" is better (or a different sentence), but it is important to analyst has a option related to this in drop-down box.
Comment 1 Alessandro Lazarotti 2011-01-25 00:07:24 UTC 
Link: Added: This issue related GUVNOR-1172
Comment 2 Alessandro Lazarotti 2011-01-25 00:37:38 UTC 
Definitely "exists" and "not exists" is not a great choice, because can be confused with "exists" drools keyword.
Comment 3 Tihomir Surdilovic 2011-03-16 03:05:09 UTC 
Committed to 5.1.x branch
Note You need to log in before you can comment on or make changes to this bug.