Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1256732

Summary: Guided DT, Analysis: issues with 'is null' and 'is not null' operators not detected correctly
Product: [Retired] JBoss BRMS Platform 6 Reporter: Zuzana Krejčová <zkrejcov>
Component: Business CentralAssignee: Toni Rikkola <trikkola>
Status: CLOSED EOL QA Contact: Lukáš Petrovický <lpetrovi>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2.0CC: kverlaen, lpetrovi
Target Milestone: ---   
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:34:49 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:

Description Zuzana Krejčová 2015-08-25 10:56:48 UTC 
Description of problem:
A rule/row with 'Fact( fieldInt != null , fieldInt == 0 )' will give an 'Impossible match' warning.
A rule/row with 'Fact( fieldInt == 0 )' will also give an 'Impossible match' warning, if the cell for 'fieldInt != null' column is unchecked.

The two cases above are okay for String type fields (Integer/numerical type fields are affected).

A rule/row with 'Fact( fieldString == null , fieldString == "sth" )' should result in an 'Impossible match' warning, but doesn't.

The case above is okay for an Integer type field (String type fields are affected).

A rule/row with 'Fact( field != null )' or 'Fact( field == null )' and some action will give a 'Rule has no restrictions and will always fire' warning.



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