Property Tax - Add New Property

Objective

Provide Citizen/Employee to Create a New Property. User has to provide various information regarding Property Location , Property Built up Information and Owner Information. User has to upload supportive documents. Once the application registered successfully it goes through various phases such as Verification, Field Inspection, Approval .

Route - https://egov-micro-qa.egovernments.org/employee/property-tax/assessment-form

Technical Implementation Details

When user tries to add new Property application, a popup comes upfront before navigating to the creation form. This popup tells about documents required to upload in the process so that user can collect those in advance.

This popup data is configurable in MDMS. On clicking Add New Property a MDMS call is made to get the required document information. This information is passed to the Popup.

An Apply button is located at the footer of this popup. User can proceed to fill new Property application on clicking of this apply button. The code related to this popup is written in reqDocs.js file.

https://github.com/egovernments/frontend/blob/d97c0c2cd92fb0dfbe68a048be49193c1e988232/web/rainmaker/dev-packages/egov-pt-dev/src/ui-config/screens/specs/pt-mutation/requiredDocuments/reqDocs.js

here only mdms data is converted to screen config with print and apply functionalities.

All the Config and its functionality are in https://github.com/egovernments/frontend/blob/d97c0c2cd92fb0dfbe68a048be49193c1e988232/web/rainmaker/dev-packages/egov-pt-dev/src/ui-config/screens/specs/pt-mutation/requiredDocuments path.

For more information about mdms document is available in this link ADDLINK-> MDMS doc

Create New Property

Create New Property application divided into five forms. Parent Component of all these forms are Formwizard.

Employee FormWizard https://github.com/egovernments/frontend/blob/5360ed2606d0ea597022eda3050a583f0fb8a4aa/web/rainmaker/dev-packages/pt-employee-dev/src/Screens/FormWizard/index.js

Citizen FormWizard https://github.com/egovernments/frontend/blob/5360ed2606d0ea597022eda3050a583f0fb8a4aa/web/rainmaker/dev-packages/pt-citizen-dev/src/Screens/FormWizard/index.js

All the config for the Forms are present in https://github.com/egovernments/frontend/blob/1c4086b504b1fffc7388952c100e72b5a98fae75/web/rainmaker/dev-packages/egov-ui-kit-dev/src/config/forms/specs/PropertyTaxPay path.

MDMS Configs and other actions are Explained in Property Actions.

Location Details

Property Address is the first step. It has a card which gets Information about the Property Location in Detail.

https://github.com/egovernments/frontend/blob/80c5bff5b0869ba44f1626fabe4a5a6133afa558/web/rainmaker/dev-packages/egov-ui-kit-dev/src/config/forms/specs/PropertyTaxPay/propertyAddress.js

Property Details

Property details is the second step where user has to fill all the required details related to property This step has two cards i.e. Property Type and Property Unit Details.

Property Details card has requires information to fill like

Property Type

Property Usage Type

Unit Usage Type

The configuration for this card is written in below file.

https://github.com/egovernments/frontend/blob/1c4086b504b1fffc7388952c100e72b5a98fae75/web/rainmaker/dev-packages/egov-ui-kit-dev/src/config/forms/specs/PropertyTaxPay/basicInformation.js

Owner Details

This is the third step in the process of Creating a Property. Owner details basically asks information about the owner of the property. Below is the file for configuration of this step.

https://github.com/egovernments/frontend/blob/80c5bff5b0869ba44f1626fabe4a5a6133afa558/web/rainmaker/dev-packages/egov-ui-kit-dev/src/config/forms/specs/PropertyTaxPay/ownerInfo.js

Documents

Documents screen is the fourth step in the process. User can upload all the relevant documents asked while Creating Proeprty. All the documents are mandatory and its configurable so that it can be made mandatory or optional as per requirement. Below file holds all the required configuration for this screen.

https://github.com/egovernments/frontend/blob/1ad9a9e63a4fdeff20d2939c071e4126928c6542/web/rainmaker/dev-packages/egov-ui-kit-dev/src/common/common/DocumentListContainer/index.js

Summary Screen

After successfully uploading the documents, the next step is summary page. User can see all the information entered . User has options to edit the information of each section. Upon clicking of edit icon user will navigate to respective section with all the data pre-filled. Below is the file contains all the required configuration of this screen.

https://github.com/egovernments/frontend/blob/6e7683214ab124237000a39869f2b0a3b99ea974/web/rainmaker/dev-packages/pt-employee-dev/src/Screens/FormWizard/components/ReviewForm/index.js

Add Property

Once user clicks on Add Property button, user navigates to acknowledgement screen stating that the application submitted successfully. Below is the acknowledgement configuration file.

https://github.com/egovernments/frontend/blob/b912e02cb6bbb4a137e49d7755d89b80cbf4254e/web/rainmaker/dev-packages/egov-ui-kit-dev/src/common/propertyTax/PTAcknowledgement/index.js

Acknowledgement screen and acknowledgement is Explained in Property Tax - Download Acknowledgement , Receipt and Mutation Certificate.

Property Create Api

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

https://github.com/egovernments/frontend/blob/5360ed2606d0ea597022eda3050a583f0fb8a4aa/web/rainmaker/dev-packages/egov-ui-kit-dev/src/utils/PTCommon/FormWizardUtils/formActionUtils.js

While Creating Property

creationReason: "CREATE"

For More Information About Property ,

Once The Application is Successfully created for further actions are explained as below,

Search Property is explained in Search Property Tax

About Property Information is explained in https://digit-discuss.atlassian.net/wiki/spaces/EGR/pages/408945038

About Property Application approval is explained inhttps://digit-discuss.atlassian.net/wiki/spaces/EGR/pages/408945299

About Property Assessment after approval is explained in https://digit-discuss.atlassian.net/wiki/spaces/EGR/pages/443678843

API Call Role Action mapping:

S.No.	API	Action id	Roles

S.No.	API	Action id	Roles
1	`/egov-mdms-service/v1/_search`	`954`	`LOA_CREATOR`,`SUPERUSER`,`WO_CREATOR`,`AE_CREATOR`,`WORKS_MASTER_CREATOR`,
2	`/user/_search`	`604`	`SUPERUSER`,`SYS_INTEGRATOR_FINANCE`,`SYS_INTEGRATOR_WATER_SEW`,`EGF_BILL_CREATOR`,`EMPLOYEE`,`EMPLOYEE_FINANCE`,
3	`/localization/messages/v1/_search`	`1531`	`SUPERUSER`,`EMPLOYEE`,`CITIZEN`,`GRO`,`DGRO`,
4	`/egov-location/location/v11/boundarys/_search`	`1429`	`EMPLOYEE`,`CITIZEN`,`GRO`,`PGR-ADMIN`,`CSR`,`TL_APPROVER`,`TL_CEMP`,`SUPERUSER`,`DE_CREATOR`,
5	`/filestore/v1/files/url`	`1528`	`SUPERUSER`,`EMPLOYEE`,`CITIZEN`,`GRO`,`DGRO`,
7	`/property-services/property/_create`	`1895`	`PT_CEMP`,`CITIZEN`
8	`/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`,