Bill Amendment Apply

Owned by Vamshikrishna Kole (Unlicensed)
Last updated: Feb 24, 2021 by JaganKumar
3 min read

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 :

https://github.com/egovernments/frontend/blob/b54d63c5c6c49e7bacd30a9d0501ad2cab580f87/web/rainmaker/dev-packages/egov-wns-dev/src/ui-config/screens/specs/wns/connection-details.js

once all the conditions satisfies we procced to Apply for new Amendment application.

Reference:

https://github.com/egovernments/frontend/blob/7dbe930bb2a8af8f3544f48810b722b01f002c33/web/rainmaker/dev-packages/egov-billamend-dev/src/ui-config/screens/specs/utils/index.js

Route -https://egov-micro-dev.egovernments.org/employee/bill-amend/apply

Stepper 1 :

Source path : https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-billamend-dev/src/ui-config/screens/specs/bill-amend/apply.js

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 :

Source Path: https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-billamend-dev/src/ui-config/screens/specs/bill-amend/applyResource/amountDetails.js

Stepper 2 :

Source Path: https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-billamend-dev/src/ui-config/screens/specs/bill-amend/applyResource/documentDetails.js

 

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 :

Source path: https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-billamend-dev/src/ui-config/screens/specs/bill-amend/applyResource/summary.js

 

Apply Footer

Source path: https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-billamend-dev/src/ui-config/screens/specs/bill-amend/applyResource/footer.js

The Next, Previous and submit buttons are configured this json file.

 

Success Screen :

Souce path : https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-billamend-dev/src/ui-config/screens/specs/bill-amend/acknowledgement.js

Search-Preview :

Source Path : https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-billamend-dev/src/ui-config/screens/specs/bill-amend/search-preview.js

 

 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

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

S.No.

API

Action id

Roles

1

/egov-mdms-service/v1/_search

954

 

2

billing-service/amendment/_create

2059

WS_CEMP , SW_CEMP

3

/billing-service/amendment/_update

2061

WS_APPROVER, SW_APPROVER

4

/filestore/v1/files/url

1528

 

5

billing-service/demand/_search

706

WS_CEMP , SW_CEMP ,WS_APPROVER, SW_APPROVER

6

/billing-service/amendment/_search

2060

WS_CEMP , SW_CEMP ,WS_APPROVER, SW_APPROVER

Â