Hide Forgot
Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000003hSwE&sfdc.override=1 securitylevel_name: Public Platform JIRA for [GUVNOR-675]Support for BigDecimal in Guided Editor
Link: Added: This issue incorporates GUVNOR-675
Toshiya, checked this with trunk and I don't see the problem (unless am not running the right test). Can you show again here how to reproduce this issue in Guvnor by describing your model, rule and a test scenario?
Added steps to reproduce, fact model and screen shots to GUVNOR-675 I still see the same issue with trunk.
Link: Added: This issue incorporates GUVNOR-1240
GSS prioritizes this 'High'. The customer has a strong need for it, some work has been done on it.
Rick, I agree we should get this fixed sooner than later. This has been lingering around for a long time. Is it OK if we hold off on this for post 5.2 release ? Unless the customer is asking that they need the fix immediately, I would recommend we defer it to next CP or 5.3. My only concern is around the amount of time needed to fix this.
We can control how BigDecimals are handled in certain places in Guvnor (i.e. most places I can think of, other than free-form DRL fields). If a field is a BigDecimal we can implicitly construct DRL like this (for example given): $new.setValue( new BigDecimal( 999.99 ) ); Furthermore, in Guvnor, we no longer escape numerical values in the LHS with quotes, so we'd now do this: $a : FactA( value == 999.99 ). Do you know if this is likely to now cause problems too?
> We can control how BigDecimals are handled in certain places in Guvnor (i.e. > most places I can think of, other than free-form DRL fields). If a field is a > BigDecimal we can implicitly construct DRL like this (for example given): > > $new.setValue( new BigDecimal( 999.99 ) ); That's nice. But let me correct, just in case... It should be $new.setValue( new BigDecimal( "999.99" ) ); > Furthermore, in Guvnor, we no longer escape numerical values in the LHS with > quotes, so we'd now do this: $a : FactA( value == 999.99 ). Do you know if this > is likely to now cause problems too? Yes, it will be an issue. It matches BigDecimal(999.99) but doesn't match BigDecimal("999.99").
If we're doing BigDecimal, it may be worth making sure that BigInteger works as well.
Should also add support for "BigDecimals" and "BigIntegers" to the Test Scenarios section.
Please verify this issue on ER5.
Please see comment #21. It has not been back-ported to 5.3.x. I proposed it is shifted to the subsequent release.
Update status to ON_QA. Please verify them against ER6.
This has been fixed in community release 5.4.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: JBoss BRMS 5.3 does not support type BigDecimals in the Guide Rule editor.