Search/Create -Property

Search Property

To provide users facility to search properties in the application by providing various search criteria to Create a Water Application.

While creating a New Water Application , it will be created based on the property so to select property we Navigate to this Search / Create property and search for a property and select the required property so that we can create a New Water/Sewerage Application.

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

Technical Implementation Details:

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

It follows egov-ui framework principles. All the screens have their configuration in the egov-pt dev package folder. Property search configuration listed in the below file.
https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-pt-dev/src/ui-config/screens/specs/pt-common-screens/propertySearch.js
Property Search Table

Objective:

Property search table is created to display the search results in a tabular format. Property search table contains various columns as per product requirements. Table Columns can be configured from the Table component configuration written in source file.

Table has few features like sorting, pagination, table search, rows limit. All these features are configurable. Default no of rows in the table configured as 10.

Here we can select the property which are Active / Approved. once we select

If none of the search criteria matches we can create a new property by Register property Option.

Table body initializes with the Property search page initialization. By default tables are hidden. Once the search operation completed successfully then all the search records formatted into to expected tabular format and supplied to the table by making Table as visible.

Below is the file link.

https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-pt-dev/src/ui-config/screens/specs/pt-common-screens/searchResource/searchFunctions.js

Create / Register Property,

Provide Citizen/Employee to Create a New Property. User has to provide various information regarding Property Location , Property Built up Information and Owner Information. Once the application registered successfully it goes through various phases based on configuration.
https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-pt-dev/src/ui-config/screens/specs/pt-common-screens/register-property.js

MDMS Requests

            { name: "PropertyType" },
            { name: "UsageCategory" },
            { name: "PTWorkflow" }

Based on the PTWorkflow https://github.com/egovernments/egov-mdms-data/blob/DEV/data/pb/PropertyTax/PTWorkflow.json

 {
         "businessService":"PT.CREATEWITHWNS",
         "initialAction":"OPEN",
         "inWorkflowStatusAllowed":false,
         "enable":false
     },

Here in the businessService = PT.CREATEWITHWNS and enable =false then we don't have workflow for Property created through WNS , if we update it to enable =true then we have the workflow for the Property
created .

If Response Property Created through WNS module will behave in following way if enable =false

Register New Property states

1	Current State	Action	Next State	Actors
2		Initiate	Initiated	CEMP, Citizen
3	Initiated	Next	Inworkflow	CEMP, Citizen
4	Inworkflow	Back	Initiated	CEMP, Citizen
5	Inworkflow	Submit	Approved	CEMP, Citizen

Once property is created it is approved in the further screens if PTWorkflow is satisfying this condition

get(payload, "MdmsRes.PropertyTax.PTWorkflow", []).filter(data=> data.enable&&data.businessService).includes("WNS"))

and property object will have same business service from that mdms businessService : data.businessService,

Summary screen

Summary of register property is configured in

https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-pt-dev/src/ui-config/screens/specs/pt-common-screens/summary.js file.

Property Create Api

Property is created using /property-services/property/_create API, the returned data is formatted and dispatched to redux

API Call Role Action mapping:

S.No.	API	Action id	Roles

S.No.	API	Action id	Roles
1	`/access/v1/actions/mdms/_get`	`870`	`CSR`, `GRO`,`DGRO`,`EMPLOYEE`,`CITIZEN`,`PGR-ADMIN`,`EMPLOYEE_FINANCE`,`TL_APPROVER`,`TL_CEMP`,`SUPERUSER`,`COLL_OPERATOR`,`BANK_COLL_OPERATOR`,`CSC_COLL_OPERATOR`,`DMA OFFICE OFFICER`,`ULB OFFICER`,`COMMISSIONER`,
2	`/egov-mdms-service/v1/_search`	`954`	`LOA_CREATOR`,`SUPERUSER`,`WO_CREATOR`,`AE_CREATOR`,`WORKS_MASTER_CREATOR`,
3	`/user/_search`	`604`	`SUPERUSER`,`SYS_INTEGRATOR_FINANCE`,`SYS_INTEGRATOR_WATER_SEW`,`EGF_BILL_CREATOR`,`EMPLOYEE`,`EMPLOYEE_FINANCE`,
4	`/localization/messages/v1/_search`	`1531`	`SUPERUSER`,`EMPLOYEE`,`CITIZEN`,`GRO`,`DGRO`,
5	`/property-services/property/_search`	`1897`	`CITIZEN`, `PT_CEMP`,`PT_DOC_VERIFIER`,`PT_FIELD_INSPECTOR`,`PT_APPROVER`
6	`/property-services/property/_create`	`1895`	`CITIZEN`, `PT_CEMP`,