Bug 996964 - Guided Decision Table: spaces as values allowed but ignored
Summary: Guided Decision Table: spaces as values allowed but ignored
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: DR4
: 6.1.0
Assignee: manstis
QA Contact: Lukáš Petrovický
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-14 11:30 UTC by Zuzana Krejčová
Modified: 2020-03-27 19:34 UTC (History)
3 users (show)

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


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1198020 0 high CLOSED Guided editor does not escape bad characters - GDT, GRT Data table 2021-02-22 00:41:40 UTC

Internal Links: 1198020

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.


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