[ASTPPCOM-628] According to decimal point origination rate, termination rate, refill etc., is not created. Created: 14/Aug/20  Updated: 27/Apr/21  Resolved: 26/Apr/21

Status: Closed
Project: ASTPP Community
Component/s: None
Affects Version/s: v4.0.1
Fix Version/s: None

Type: Bug Priority: Medium
Reporter: Sameer Patel (Inactive) Assignee: Ashish Gohil
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: 3h
Original Estimate: Not Specified

Attachments: File decimal point.mp4     PNG File image_2020_11_27T06_17_28_830Z.png    
Issue Links:
Relates
Reproducibility: always
Category: Functional
Sprint: 2021-COM-DEV-W15
Edition: Community

 Description   

Steps to reproduce :

 1. Login as admin

 2. Go to configuration menu

 3. Click on settings

 4. Set decimal point

 5. Go to origination rate and try to create for e.g., 2.1234567

Expected result :

 > According to decimal point anything should be created.

 Comments   
Comment by Ashish Gohil [ 27/Nov/20 ]

when you create origination and termination you should create only 5 decimal value due to reason below example.

for ex :-  if you have set 50 decimals in globally so you want to add 50 decimal at create time so what is logic behind this.

we have limitation in database and its value is 5 decimal point. please check below image.

 

Comment by Ashish Gohil [ 26/Apr/21 ]

This issue is resolve, changes done regarding according to set decimal points all rates and amount will be shown as per decimal pint configuration.

MR W15

https://gitlab.com/inextrix/ITPLATP/ASTPPCOM/-/merge_requests/633

verification pending on container.

Comment by Prashant Kumar [ 26/Apr/21 ]

As per discussed with Ashish Gohil, issue doesn't resolve due to code missing.

Comment by Prashant Kumar [ 27/Apr/21 ]

This concern is resolved and will be added in upcoming version release.

Generated at Sat Feb 10 07:18:51 CET 2024 using Jira 8.13.3#813003-sha1:22ebedbb75c99b147c66f14e031dd8a2d214753a.