Bug 1129607 - Integer enums break data table in guided rule template
Summary: Integer enums break data table in guided rule template
Keywords:
Status: VERIFIED
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: DR3
: 6.1.0
Assignee: manstis
QA Contact: Lukáš Petrovický
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-13 10:47 UTC by Zuzana Krejčová
Modified: 2016-08-01 01:16 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)

Description Zuzana Krejčová 2014-08-13 10:47:49 UTC
Description of problem:
Using an Integer enumeration in template data corrupts the whole row of data. If another cell in the row uses select box (enumeration), it cannot be edited after you select an integer value. Simple cells (not using enumerations/select boxes) can be edited, but the values are not saved. Other rows are not influenced at all.


Steps to Reproduce:
1. Create POJO/data object EnumFact with fields: Integer fi1, Integer fi2, String fs1, String fs2.
2. Create an enumeration:
'EnumFact.fi1' : ['1', '2']
'EnumFact.fs1' : ['firstValue', 'secondValue']
3. Create a guided rule template, add EnumFact condition, add restriction on all of the 4 fields, for each choose 'equals' operator and template key.
4. Switch to Data tab, add a row. Select value for 'fi1', try to select value for 'fs1'. Type '123' into cell for 'fi2' and 'asd' into cell for 'fs2' (all on the same row).
5. Save, close and reopen, switch to Data tab.


Actual results:
In step 4, value for 'fs1' cannot be selected, the popup with the select box does not appear.
In step 5, the data table contains an empty row.


Expected results:
In step 4, value for 'fs1' can be selected, in step 5, the data is persisted and all values entered in step 4 are still there.


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