Property - Transfer of Ownership
- jk
Â
Objective
Provide Citizen/Employee to Update Owner of an Existing Property. User can update Owner Information and Owner Documents. User has to upload supportive documents. Once the application registered successfully it goes through various phases such as Verification, Field Inspection, Approval and Pay Mutation Fee.
Route - https://egov-micro-qa.egovernments.org/employee/property-tax/property/PROPERTY_ID/TENANT_ID
Technical Implementation Details
User Search for the property and land in the property Information screen , if user wants to transfer of ownership
When user tries to click on Transfer Ownership, 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 Transfer Ownership , a MDMS call is made to get the required document information. This information is passed to the Popup.
A Transfer Ownership button is located at the footer of this popup. User can proceed to fill new Property Mutation application on clicking of this Transfer Ownership button. The code related to this popup is written in apply-document.js file.
https://github.com/egovernments/frontend/blob/a87e2ffdf7167e65206003f07301f4f66790c3c4/web/rainmaker/dev-packages/egov-pt-dev/src/ui-config/screens/specs/pt-mutation/apply-document.js and coversion of mdms to screenconfig is taken care in 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
Create New Property Mutation application divided into three forms. The configuration related to all these forms are written in apply.js file.
Â
Transfer Details
Transfer Details is the first step. It has a four card which gets Information about the New Owner Details, Mutation Details and Registration Details. Its first card shows about the Property Current Owner.
Â
Mutation Details
Mutation details is the second card where user has to fill all the required details related to property pending court cases.
Registration Details
Registration details is the third card where user has to fill all the required details related to property registration type and value etc.
Documents
Documents screen is the second step in the process. User can upload all the relevant documents asked while Property Mutation. 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.
MDMS configuration about Mutation Documents are Explained in
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.
All the Summary Cards are present in the folder.
Property Mutation
Once user clicks on Submit button, user navigates to acknowledgement screen stating that the application submitted successfully. Below is the acknowledgement configuration file.
Property Mutate Api
Once the data is fetched using /property-services/property/_update API, the returned data is formatted and dispatched to redux
While Updating Property
creationReason:Â "MUTATION"
and workflow information as follow
workflow = {
"businessService": "PT.MUTATION",
"tenantId" : tenantId,
"action": "OPEN",
"moduleName": "PT"
}Api call is made in
For More Information About Property ,
Once The Application is Successfully created for further actions are explained as below,
Search Property is explained in
About Property Information is explained in
About Property Application approval is explained in
API Call Role Action mapping:
S.No. | API | Action id | Roles |
|---|---|---|---|
1 |
|
|
|
2 |
|
|
|
3 |
|
|
|
4 |
|
|
|
Â