Property Tax - My Applications
My Applications
Users can review the list of applications and their status registered under their mobile number in My Applications tab. Initially only four application will load at once, if user want to look for more, “Load More” option needs to be clicked, Each Application for the initial view will display Application No, Service Category, Property Id, Application Type and status, with Track option, through which User can look up more details about the Application. If a user did not find the Application looking for, a new Application can be raised using the link provided at the end of the page.
Once the user clicks on Track Button, the Application Details Page will be displayed with all the necessary information about the application.
timeline component:
timeline component is present at the end of the application details which tells about the current status and history of the application being open to edit, approved, rejected, closed etc.
Technical Implementation Details:
The link for the My Applications and Application Details common Index is given below, it can be used to understand the working of the code, Below is the file link.
The template for My Application is present under pt/pages/citizen/PTMyApplications and Application Details page is present inside pt/pages/citizen named as PTApplicationDetails. All the Application list is being retrieved by calling the search API "/property-services/property/_search"
This API is called using the React hook present inside the index of PTMyapplication and PTApplicationDetails page, a single application is being loaded, by passing the unique Property Id in the search API.
Following is the hook used for the property search API.
const { isLoading, isError, error, data } = Digit.Hooks.pt.usePropertySearch(tenantId);Create and Update Util function:
The two main util function and the main objective of it are given below:
Create Util Function : while going through the create flow, all the inputs which user has entered are stored in a different structure, here as the units are not separated in the flow but incorporated according to each ground, the storing structure is different from the request body of create API, this function transformed the flow stored data into the request body format, code can be found using the link below:
https://github.com/egovernments/digit-ui-internals/tree/development/packages/modules/pt/src/utils
Update Util Function : Detailed information about it can be found in the below link:
https://digit-discuss.atlassian.net/wiki/spaces/DD/pages/1580793863
MDMS:
No MDMS data being used here, all the data is being loaded from Search API.
Localization :
For My Applications also the Localization keys are being added in the ‘rainmaker-pt’ locale module same as My properties and create. To change, update or of adding any new localization key will be done in the same locale module only.
Role Actions:
Url | Roles | Action Id |
|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|