Bill Amendment Apply
Apply for Bill Amendment:
Bill Amendment Gets initiated from the Individual modules , currently we have enabled for Water and Sewerage screens .
The option for the Billamend is shown based on the 3 Criteria's,
1. Based on the MDMS Service wise enabled using is isBillAmendmentEnabled
Flag in the the MDMS moduleName:Â "BillingService"
, masterDetails:Â name: "BusinessService
".
2. Based on The demand , if there is demand from the demand search for that consumer code then again the option wont be shown
3. Based on the Amendment search , if a Amendment Application was created already on the same consumer and it is not approved then we don't get option to create a new Bill amend from the connection details screen in individual Service.
Reference :
once all the conditions satisfies we procced to Apply for new Amendment application.
Reference:
Route -https://egov-micro-dev.egovernments.org/employee/bill-amend/apply
Stepper 1 :
All the drop down data are mapped through mdms response.
For to display MDMS data we have common container in UI Framework ( “getSelectField
“ ).
In Bill Amendment: We used common container for Demand Revison Basis
.
Sample JSON for Structure Type and Sub Structure Type :
Â
jsonPath is used to store the data in specified path when clicking event triggers or on handleFieldChange.
sourceJsonPath is the path where the data is fetched to populate in the dropdown.
Mdms data :
Demand Revision Type data is fetched from https://github.com/egovernments/egov-mdms-data/blob/DEV/data/pb/BillAmendment/DemandRevisionBasis.json
Amount details is the first stepper :
Stepper 2 :
Â
Mdms data : https://github.com/egovernments/egov-mdms-data/blob/DEV/data/pb/BillAmendment/documentObj.json
The data formatting logic is as shown below. prepareDocumentsUploadData(state, dispatch);
in https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-billamend-dev/src/ui-config/screens/specs/bill-amend/utils/index.js
Stepper 3 :
Â
Apply Footer
The Next, Previous and submit buttons are configured this json file.
Â
Success Screen :
Search-Preview :
Â
 Download PDF:
1 . Acknowledgement PDF
It is Generated from the Client side itself and configuration is present in https://github.com/egovernments/frontend/blob/4beb20bfbd359b9aea52de0ddf06377a07173207/web/rainmaker/dev-packages/egov-ui-kit-dev/src/utils/pdfUtils/generateBillAmendAcknowledgement.js
Â
2. Credit/ Debit Note PDF:
It is been generated from the API , refer the function generateBillAmendPdf
for the Instance inhttps://github.com/egovernments/frontend/blob/cd6b6beaddcb759ddcbacce6d79a9ce3b9197dc0/web/rainmaker/dev-packages/egov-billamend-dev/src/ui-config/screens/specs/bill-amend/utils/index.js
Â
Workflow :
Role | Action | Next State | Status |
---|---|---|---|
EMPLOYEE, CITIZEN | null | APPROVALPENDING | INWORKFLOW |
EMPLOYEE | APPROVALPENDING | APPROVED/REJECTED | ACTIVE/INACTIVE |
Â
API Call Role Action mapping:
S.No. | API | Action id | Roles |
---|---|---|---|
1 |
|
| Â |
2 |
|
|
|
3 |
|
|
|
4 |
|
| Â |
5 |
|
|
|
6 |
|
|
|
Â