Citizen-Search(W&S)

Citizen Search Connection

Objective

Citizen can search Connection by providing all mandatory information along with any one of the parameter. When user has entered connection number then only one record will be displayed if the record associated with the connection number exist. All the fields have pattern validation rule. Consumer No is nothing but connection number.

Reset operation clears all the data entered in the screen.

Technical Implementation Details:

All the screens are developed under the egov-wns-dev package. 

https://github.com/egovernments/frontend/tree/master/web/rainmaker/dev-packages/egov-wns-dev

It follows egov-ui framework principles. All the screens have their configuration in the egov-wns-dev package folder. Citizen search configuration listed in the below file.

https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-wns-dev/src/ui-config/screens/specs/wns-citizen/search.js

MDMS data:

Only one MDMS call is made to get the tenantID data to fill the City dropdown. Below is the snippet from search.js file

 

Localization and search connection table is similar to the employee search water & sewerage. for finding those details refer Search Water & Sewerage .

API Call Role Action mapping:

API

Action id

Roles

API

Action id

Roles

1

/egov-mdms-service/v1/_search

954

LOA_CREATOR,SUPERUSER,WO_CREATOR,AE_CREATOR,WORKS_MASTER_CREATOR

2

/localization/messages/v1/_search

1531

SUPERUSER,EMPLOYEE,CITIZEN,GRO,DGRO

3

/billing-service/bill/v2/_fetchbill

1862

CITIZEN,EMPLOYEE

4

/ws-services/wc/_search

1900

CITIZEN,EMPLOYEE,WS_CEMP,WS_DOC_VERIFIER,WS_FIELD_INSPECTOR,WS_APPROVER,WS_CLERK

5

/sw-services/swc/_search

1919

CITIZEN,EMPLOYEE,SW_CEMP,SW_DOC_VERIFIER,SW_FIELD_INSPECTOR,SW_CLERK

6

/property-services/property/_search

1897

CITIZEN,EMPLOYEE

Â