Bug 996964

Summary: Guided Decision Table: spaces as values allowed but ignored
Product: [Retired] JBoss BRMS Platform 6 Reporter: Zuzana Krejčová <zkrejcov>
Component: Business CentralAssignee: manstis
Status: CLOSED EOL QA Contact: Lukáš Petrovický <lpetrovi>
Severity: low Docs Contact:
Priority: low    
Version: 6.0.0CC: etirelli, lpetrovi, rzhang
Target Milestone: DR4Keywords: Reopened
Target Release: 6.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Known Issue Summary: Users can enter blank space as a value in a cell (for which the data-type is a String) and those spaces will be there if you edit the cell again. However, the blank space will be ignored in the source, along with the whole fact pattern. This can be problematic when the value required in a constraint or action is a space or spaces. Currently there is no workaround to this issue. Cause: Consequence: Fix: Result:
 Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-27 19:34:37 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á 2013-08-14 11:30:27 UTC 
Description of problem:
You can enter "            " as a value into a cell. Those spaces will be there if you edit the cell again. Yet they are ignored in the source, along with the whole fact pattern:
1. | //from row number: 1
2. | rule "Row 1 gdt"
3. |     dialect "mvel"
4. |     when
5. |     then
6. | end

This is inconsistent behaviour.


Version-Release number of selected component (if applicable):
kie-wb 6.0 CR1


Expected results:
Either the spaces as value are not allowed at all or they are respected as normal value of a field.
Comment 4 manstis 2013-10-16 12:25:07 UTC 

*** This bug has been marked as a duplicate of bug 996976 ***
Comment 5 manstis 2013-10-24 15:21:18 UTC 
>> manstis 2013-10-16 07:14:33 EDT

>> The only scenario where this is potentially valid is where a field's 
>> data-type is String and the value is a space or spaces. Can you confirm this? 
>> Obviously the other scenario where there's an action to update an existing 
>> fact where the pattern is excluded remains a valid - and flawed - scenario.

> Zuzana Krejčová 2013-10-24 08:26:47 EDT

> You are right.