Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Yadav Abhishek Kumar (ABHISHEK-2)
Capgemini

Capgemini
IN
ABHISHEK-2 Member since 2011 4 posts
Capgemini
Posted: Jan 8, 2018
Last activity: Jan 9, 2018
Posted: 8 Jan 2018 1:33 EST
Last activity: 9 Jan 2018 3:36 EST
Closed

Decimal places truncating is not required

We have a requirement where after divide operation we require the exact value to be stored on the clipboard without rounding and truncating. As per current behavior if we don't give any precision then 2 decimal places is being considered.
we cannot give precision because we have no control on the input values.
Is there any fix/hot fix available which can help us in achieving the same?

To see attachments, please log in.

  • Sapana Mishra
Posted: 6 years ago
Posted: 8 Jan 2018 2:07 EST
Arun Kumar Mahanty (Arun_Mahanty)
Pegasystems Inc.
Principal Technical Solutions Engineer
Pegasystems Inc.
IN

Hello Abhishek,

Currently which method your using it .

You can have a look into below article

https://collaborate.pega.com/question/truncating-decimal-places-without-doing-rounding

Show More

Hello Abhishek,

Currently which method your using it .

You can have a look into below article

https://collaborate.pega.com/question/truncating-decimal-places-without-doing-rounding

Thanks,

Arun


Show Less
To see attachments, please log in.
Posted: 6 years ago
Posted: 8 Jan 2018 2:40 EST
Yadav Abhishek Kumar (ABHISHEK-2)
Capgemini

Capgemini
IN

Thanks for your response. The solution requires precision to be given which is not the requirement in our case. The Scenario for which I am seeking solution is below.

Here Prop1 and Prop2 are user inputs without any limitations.

Show More

Thanks for your response. The solution requires precision to be given which is not the requirement in our case. The Scenario for which I am seeking solution is below.

Here Prop1 and Prop2 are user inputs without any limitations.

Prop1=499 
Prop2=50000 
@(Pega-RULES:Math).divide(.Prop1,.Prop2) gives 0.01 but desired output is 0.00998 
Similarly 
Prop1=499 
Prop2=500000 
@(Pega-RULES:Math).divide(.Prop1,.Prop2) gives 0.00 but desired output is 0.000998

 


Show Less
To see attachments, please log in.
Posted: 6 years ago
Posted: 8 Jan 2018 15:58 EST
Mohammad Asif Hasan (Mohammad_Asif_Hasan)
EPAM Systems, Inc.
Mohammad Asif Hasan
EPAM Systems, Inc.
ES
You can create your own custom utility function. Open "divide" function and save as it in your application ruleset and modify the return code and remove trucating function used. And refer the above created function in your application. Hope it gives you an idea for your business requirement.
To see attachments, please log in.
Posted: 6 years ago
Posted: 9 Jan 2018 3:36 EST
Rachit Agarwal (Rachit_Agarwal)
PEGA
Principal Technical Support Engineer
Pegasystems Inc.
US

Hi,

You can also write a java step and pass the parameters there. In the java step you can use BigDecimal where you can use setScale() method. Please refer below. 

You can modify the code as per your requirement. This should resolve your issue. 

Regards,

Rachit

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice