Support Article

Decimal Property Truncating Scale when used with a Qualifier

Summary

User has a property (Decimal) with Qualifier set as pyCurrency and to another property (text). For locale ja_JP, the decimals of the amount field is truncated in Pega 7.2.

For example, 13.11 is returned as 13. This is happening at data retrieval as the truncated value is present in the pxResults page.

In PRPC 6.3 this is not the case with same settings and control rules applied.

Error Messages

Not applicable

Steps to Reproduce

1.Set user locale to ja_JP. 
2.Launch SI Manager portal.
3.Click on Search Portal.
4.Select Payments/Message from Select Table drop-down.
5.Select Payment Details/Message Details from Select List drop-down.
6.Select LON from Branch dropdown and then click Find.
7.Observe the Debit amount/Amount Column. (Here multiple results are shown in a repeat grid).
 

Root Cause

Each property qualifier provides additional information at runtime about the property, and may alter the behavior in computations or presentation of the property. Hence, in cases where Qualifier is used, Qualifier value(ex..MSGCCY/.DBTCCY) should be provided at first than the Property value(ex..MSGAMT/.DBTAMT). Here, Order is important and it matters. If qualifier value is not provided first, it is not taken into consideration.

So, while retrieving the values through a listview, order of retrieving values becomes important.

Resolution

Perform the following local-change would resolve the issue:

1.Change the order of .MSGAMT and .MSGCCY property in listview rules Message all ,RelatedUTI all and Transaction_Ref all of class PegaResearch-Commbank-Message. For example:



2.Change the order of .DBTAMT and .DBTCCY  property in listview rules RelatedUTI all and Transaction_Ref all of class PegaResearch-Commbank-PaymentTXN.

 

Published January 12, 2017 - Updated December 2, 2021