Bug 797149 - BigDecimal 99.99B have to be copied and pasted into RHS of a Guided Rule
Summary: BigDecimal 99.99B have to be copied and pasted into RHS of a Guided Rule
Keywords:
Status: MODIFIED
Alias: None
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: BRM (Guvnor)
Version: BRMS 5.3.0.GA
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: future
Assignee: manstis
QA Contact: Lukáš Petrovický
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-24 11:41 UTC by Zuzana Krejčová
Modified: 2020-04-27 01:13 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)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 724448 0 high MODIFIED [GUVNOR-675]Support for BigDecimal in Guided Editor 2021-02-22 00:41:40 UTC

Internal Links: 724448

Description Zuzana Krejčová 2012-02-24 11:41:03 UTC
Description of problem:
BigDecimal 99.99B have to be copied and pasted into RHS of a Guided Rule, although it can be typed into the LHS.


Version-Release number of selected component (if applicable):
BRMS 5.3.0 ER4


Steps to Reproduce:
1. Create a new model with a fact with BigDecimal field.
2. Create a new guided rule, insert the fact to the 'when' part, select a constraint - the BigDecimal field.
3. Insert the fact to the 'then' part of the rule, select the same field.

  
Actual results:
99.99B can be typed as a value in the 'when' part, it can't be typed as a value in the 'then' part of a rule. It has to be copied and pasted there.


Expected results:
Both field's values input fields should act the same way.



Additional info:
This is closely related to https://bugzilla.redhat.com/show_bug.cgi?id=724448 - Support for BigDecimal in Guided Editor.

Comment 4 Ryan Zhang 2012-03-21 09:55:53 UTC
Please verify this issue on ER5.

Comment 7 Ryan Zhang 2012-04-23 07:40:32 UTC
Update status to ON_QA. Please verify them against ER6.

Comment 9 manstis 2012-05-02 12:30:07 UTC
This has been fixed in community release 5.4.


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