eFMAS (GramNidhi) Web App
- “Registration : Updated put vendor API to allow edit of vendor details only
- Expenditure : Expenditure approval get all data updated”
- “Sparsh : updated error log and error message while budgetdetails not match while adding or updating the details
- Fund-request: DSC amount validation at Recommend proposal
- Expenditure : update vendor response added gst number”
- “Registration : – Updated patch api and resolved cbo approval receiver logic and queries
- Dsc : – Added validatations at the time of dsc registration to block users for multiple requests
- for same payment type and level .
- Frontend : bugfix for DSC history for district level -> verified by Avanti on stage
- expenditure : Null check added for vendor address
- total and net payble get calculation updated”
- “Sparsh : Added disburseed fto flag status from sparsh to fund-request
- Fund-request: Changed grouping of block level, added district name in fto number, flag updated in GNS001 in fundrequest.
- Expenditure- fetching all beneficiary and tax beneficiary for a expenditure in generatexml”
- “Frontend : components load in CreateExpenditure based on ExpType, CostType and Clone feature for Expenditures
- Expenditure – Added missing compoents, filtering based on expenditure type and cost type
- Updated find all expenditure method
- Expenditure – Updated draft case flow , resolved partial delete and update issues
- Registration :- Updated vendor reject PFMS flow in case of duplicate registration “
- “fund request – added api for getting shg count on the basis of clf
- Frontend : bugfix for Clone, binding PTax and cascading fixes
- Expenditure : component code fix”
- “Frontend : bugfix to patch form value in FE
- Registration : – Optimized get Vendor List API and duplicate vendor case in PFMS acceptance”
- “Frontend : bugfix to patch form value in FE
- Fund-request: Removed shg_count, vo_count max limit from proposal
- Sparsh : Added validation of DSC sign fto’s
- Registration : – Optimized get Vendor List API and duplicate vendor case in PFMS acceptance”
- Expenditure : tax beneficiary delete fix