Property Tax System Service Configuration
Service configuration details
Overview
The Property Tax System is one of the major applications of the eGov stack, which helps municipalities and citizens to handle property tax payments and other related functions on the property, such as assessments, mutation, and so on.
Pre-requisites
Prior knowledge of Java/J2EE.
Prior knowledge of Spring Boot.
Prior knowledge of REST APIs and related concepts like path parameters, headers, JSON etc.
Prior knowledge of Git
Prior knowledge of the demand-based systems.
The following services should be up and running:
user
MDMS
Persister
Location
Localization
Id-Gen
Billing-service
URL-shortener
These services must be up so the Property Tax System can interact with identity, master data, persistence, billing, and UI resolution.
Key Functionality
The Property Service provides multiple functionalities, starting from serving as a central repository where property information is registered for the reference of citizens and other municipality-provided services such as water connection and sewerage management.
An assessment can be done so as to calculate and pay tax on the property. The different services provided by the property services include -
Property Registry
Assessment
Mutation
Bifurcation
Consolidation
Registry Explanation
The registry flow helps the Citizen/Employee to create a property in the system with the minimal information required.
Other workflows, such as assessment or mutation, can be triggered on the existing ACTIVE Property in the registry.
The property can be created, updated, cancelled, searched, followed by the process of Mutation and Assessment.
The same entry in the registry can be referred to by other modules for their business purposes(Water charges).
Configuration Steps
Add Persister Configuration
The Persister service needs to know how to store Property Tax records.
Open your
persisterservice config repo.Add the property-services-registry.yml file to the Persister configs.
This config informs Persister how to persist property registry flows and objects.
Add Workflow Configuration
Configure workflows for different Property Tax operations.
Sample configurations
Fields in the above MDMS file
businessService
Name of workflow config
initialAction
Indicate the start(initial) action of the particular workflow mention in businessService.
inWorkflowStatusAllowed
This field indicate whether the property with application status as “inWorkflow” can be use with water and sewerage connection creation. If this field is true then for that particular use case, the property with “inWorkflow” status can be use with water and sewerage connection creation and vice versa
enable
If this filed is set as true, then the other fields associate with the particular object is use for property creation.
Below is another sample workflow config where a property is created from the Water and Sewerage module -
Sample workflow config for update property
Sample property tax legacy workflow config
Configure Integrations
Integration Scope
Property service can be integrated with any organisation or system that wants to maintain a record of the property and collect taxes with ease.
Integration Benefits
Easy to create and a simple process of self-assessment to avoid the hassle.
Helps maintain property data which can be used in the integration of other essential services like asset management, water connection and so on.
provides additional functionalities like mutation, assessment of properties.
Steps to Integration
To let external systems use the PT service:
Reference Docs
USER Service
url-shortening
Billing-service
Location
Workflow
Persister
****
Localization
Id-Gen service
API LIST:
/Property/_create
/Property/_update
/property/_search
Last updated
Was this helpful?