Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Objective

To provide facility to search properties without logging into the application and making payment of pending due amount. This feature is developed only for citizen application.

Implementation Details

This feature has a separate search screen. Citizen can enter the search criteria into the search form and search the properties. The properties obtained by the search operation will be listed in the search table. Below is the details of search criteria.

Field

Input type

Validation rule

ULB

Dropdown

Mandatory

Locality

Dropdown

Mandatory

Owner Name

Input text

Optional

Owner mobile no

Input text

Optional

Property ID

Input text

Optional

  1. Atleast one optional field is required along with mandatory inputs to search the properties.

  2. Locality dropdown list depends on the ULB selected.

  3. After successful search, the search results will be displayed in the table as below

PAY option

User can have PAY button in the following scenarios

  1. Property should be ACTIVE

  2. Due amount should be more than 0

Technical Implementation Details

Open Search screen is developed as part of property tax module. Below is the search screen configuration file link.

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

Search screen table, api calls and other utility functions are written in the files under publicSearchResource folder. Below are the file description.

https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-pt-dev/src/ui-config/screens/specs/pt-mutation/publicSearchResource/search-resources.js - It has the screen configuration like input text, dropdowns, buttons etc.

https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-pt-dev/src/ui-config/screens/specs/pt-mutation/publicSearchResource/search-methods.js - It has the functions related to search api calls, reset forms etc.

https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-pt-dev/src/ui-config/screens/specs/pt-mutation/publicSearchResource/publicSearchUtils.js - This file has utility methods supporting api calls, form validation etc.

https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-pt-dev/src/ui-config/screens/specs/pt-mutation/publicSearchResource/search-table.js - This file has functions that is responsible for making table definitions.

MDMS Call details

We have to make few MDMS calls to get the required configuration related data. Below is the description of MDMS calls used in open search implementation.

  1. MDMS call to get the Tenants data. Tenants data was supplied to ULB dropdown after screen initialization.

API Whitelisting

Since this is open search and citizen can search the properties without logging in the application, certain apis were required to be whitelisted. These apis can return the result without authenticating the user. Below is the list of apis that were whitelisted

  1. "/property-services/property/_search"

  2. "/billing-service/bill/v2/_search"

  3. "/egov-location/location/v11/boundarys/_search?hierarchyTypeCode=REVENUE&boundaryType=Locality"

  4. "pg-service/transaction/v1/_create"

  5. "pg-service/transaction/v1/_update" + txnQuery

API call details

  1. Boundary calls to get the Locality data

  2. Search API Call

URL: "/property-services/property/_search"

method: “post“

QueryParams: [{key:”tenantId”, value:”pb.amritsar”}, {key:”locality”, value:”SUN02”}, {key:”name”, value:”test”}]

3. Search Bill Call

URL: "/billing-service/bill/v2/_search"

method: “post“

QueryParams: [{key:”tenantId”, value:”pb.amritsar”}, {key:”service”, value:”PT”}, {key:“consumerCode“, value:”PT-107-001920,PT-107-000519”}]

Localization Implementation

Search screen locale keys are pushed under rainmaker-pt locale module. Table header locale keys are in rainmaker-common locale module. Localization calls are made before screen initialization and all the locale keys are stored in localStorage.

While selecting the ULB, again a locale call is made for locality dropdown. This call returns the locale keys of every locality dropdown options.

URL: /localization/messages/v1/_search

method: “post“

queryParams: [{key:”module”, value:”rainmaker-common,rainmaker-pt,rainmaker-pgr”}, {key:”locale”, value:”en_IN”}, {key:”tenantId”, value:”pb”}]

  • No labels