The update feature in property services provides a facility to update the owner’s primary mobile number (referred to as ‘mobile number’ hereafter). The already existing update API is used with some enhancements to implement this feature. Also, a facility has been provided to add an alternate mobile number for every owner of the property. This can be done using the newly created addAlternateNumber API. The alternate number can also be updated using this API.
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
Enables user to update property owner’s mobile number and to add/update the alternate mobile number.
All the property information (except the owner’s mobile number/ alternate number) should be the same as the information from the search result. The owner’s primary mobile number has to be necessarily different from the existing one.
The Creation Reason in the property should be sent as UPDATE for the request to be considered as an update request. Also, the property has to be in ACTIVE status. For adding/updating alternate numbers, modify the alternateMobileNumber field in the Property.
Sample request for updating primary mobile number or adding/updating alternate number.
Configs:
The update service belongs to the property service itself and provides the same ease of access for the functionality.
Pick a property id that is already created in the system.
call the property/update API by changing the owner’s mobile number.
Steps to Integration (updating alternate number):
Pick a property id that is already created in the system.
call the property/addAlternateNumber API by adding/changing the owner’s alternate number.
Reference Docs: - For additional details please refer to the property document
All content on this page by is licensed under a .
Prior knowledge of the demand-based systems.
Following services should be up and running:
user MDMS
Persister
Location
Localization
Id-Gen
Billing-service
URL-shortener
name
value
description
kafka update topic
update-property-registry
{
"RequestInfo": {
"apiId": "Rainmaker",
"authToken": "08876469-a3e7-41c7-8031-218405fee62e",
"access_token":"dee3f319-5593-4cf9-b74b-4771860445f9",
"userInfo": {
"id": 12085,
"uuid": "abfe724b-a93e-4edd-b084-82ecbe22a192",
"userName": "qaroo",
"name": "QARoo",
"mobileNumber": "6939358368",
"emailId": null,
"locale": null,
"type": "EMPLOYEE",
"roles": [
{
"name": "PT Counter Employee",
"code": "PT_CEMP",
"tenantId": "pb.amritsar"
},
{
"name": "PT Field Inspector",
"code": "PT_FIELD_INSPECTOR",
"tenantId": "pb.amritsar"
},
{
"name": "PT Doc Verifier",
"code": "PT_DOC_VERIFIER",
"tenantId": "pb.amritsar"
},
{
"name": "Employee",
"code": "EMPLOYEE",
"tenantId": "pb.amritsar"
},
{
"name": "PT Counter Approver",
"code": "PT_APPROVER",
"tenantId": "pb.amritsar"
},
{
"name": "Super User",
"code": "SUPERUSER",
"tenantId": "pb.amritsar"
}
],
"active": true,
"tenantId": "pb.amritsar",
"permanentCity": null
}
},
"Property": {
"id": "b9e8fecd-5527-4283-b0fd-9019da696c25",
"propertyId": "PB-PT-2021-09-01-020993",
"surveyId": null,
"linkedProperties": null,
"tenantId": "pb.amritsar",
"accountId": "11b0e02b-0145-4de2-bc42-c97b96264807",
"oldPropertyId": null,
"status": "ACTIVE",
"address": {
"tenantId": "pb.amritsar",
"doorNo": null,
"plotNo": null,
"id": "8c567955-a6d6-4e97-8ba2-9e0675229893",
"landmark": null,
"city": "Amritsar",
"district": null,
"region": null,
"state": null,
"country": null,
"pincode": null,
"buildingName": null,
"street": null,
"locality": {
"code": "SUN04",
"name": "Ajit Nagar - Area1",
"label": "Locality",
"latitude": "31.63089",
"longitude": "74.871552",
"area": "Area1",
"children": [],
"materializedPath": null
},
"geoLocation": {
"latitude": 0.0,
"longitude": 0.0
},
"additionalDetails": null
},
"acknowldgementNumber": "PB-AC-2021-09-01-020523",
"propertyType": "BUILTUP.INDEPENDENTPROPERTY",
"ownershipCategory": "INDIVIDUAL.SINGLEOWNER",
"owners": [
{
"id": null,
"uuid": "188fe338-5116-4ba7-96f5-d8b3c86466d0",
"userName": "3dc9ed9b-a72f-41c8-a30e-618964ccd2dd",
"password": null,
"salutation": null,
"name": "Rohit",
"gender": null,
"mobileNumber": "7391904467",
"emailId": null,
"altContactNumber": null,
"pan": null,
"aadhaarNumber": null,
"permanentAddress": null,
"permanentCity": null,
"permanentPinCode": null,
"correspondenceCity": null,
"correspondencePinCode": null,
"correspondenceAddress": null,
"active": true,
"dob": null,
"pwdExpiryDate": 1626617402000,
"locale": null,
"type": "CITIZEN",
"signature": null,
"accountLocked": false,
"roles": [
{
"id": null,
"name": "Citizen",
"code": "CITIZEN",
"tenantId": "pb"
}
],
"fatherOrHusbandName": null,
"bloodGroup": null,
"identificationMark": null,
"photo": null,
"createdBy": "24226",
"createdDate": 1630534079000,
"lastModifiedBy": "1",
"lastModifiedDate": 1634086148000,
"tenantId": "pb",
"alternatemobilenumber": "9619367055",
"ownerInfoUuid": "f375b888-e400-4007-8e0a-5338a6aa2794",
"isPrimaryOwner": null,
"ownerShipPercentage": null,
"ownerType": "NONE",
"institutionId": null,
"status": "ACTIVE",
"documents": null,
"relationship": "FATHER"
}
],
"alternateMobileNumberDetails": null,
"institution": null,
"creationReason": "UPDATE",
"usageCategory": "NONRESIDENTIAL.COMMERCIAL",
"noOfFloors": 1,
"landArea": 1234.0,
"superBuiltUpArea": null,
"source": "MUNICIPAL_RECORDS",
"channel": "CFC_COUNTER",
"documents": null,
"units": [
{
"id": "c82b31b4-5761-41c2-b472-782f34670520",
"tenantId": null,
"floorNo": 0,
"unitType": "ACRESTAURANT",
"usageCategory": "NONRESIDENTIAL.COMMERCIAL.FOODJOINTS.ACRESTAURANT",
"occupancyType": "SELFOCCUPIED",
"active": true,
"occupancyDate": 0,
"constructionDetail": {
"carpetArea": null,
"builtUpArea": 136.67,
"plinthArea": null,
"superBuiltUpArea": null,
"constructionType": null,
"constructionDate": null,
"dimensions": null
},
"additionalDetails": null,
"auditDetails": null,
"arv": null
}
],
"additionalDetails": null,
"auditDetails": {
"createdBy": "11b0e02b-0145-4de2-bc42-c97b96264807",
"lastModifiedBy": "11b0e02b-0145-4de2-bc42-c97b96264807",
"createdTime": 1630514279281,
"lastModifiedTime": 1630514279281
},
"workflow": null,
"AlternateUpdated": false
}
} {
"code": "PT_UPDATE_ALTERNATE_NUMBER",
"message": "Dear {ownername}, Your request to register an alternate mobile number in property record has been processed and the mobile number {alternatenumber} has been registered as alternate mobile no.",
"module": "rainmaker-pt",
"locale": "en_IN"
},
{
"code": "PT_UPDATE_OWNER_NUMBER",
"message": "Dear {ownername}, Your request to update of mobile number in property record has been processed and the mobile number has been changed from {oldmobilenumber} to {newmobilenumber}.",
"module": "rainmaker-pt",
"locale": "en_IN"
}The Update Mobile Number feature in PT
Reminds ULB users about any invalid mobile numbers that exist in the owner records and enables them to update these.
Enables ULB users to update the mobile numbers as per requests from the property owner(s).
Enables property owner(s) to update the mobile number in their record to log in to the system.
If the mobile number is invalid it throws a warning in the property info screen whenever the user tries to pay the dues.
Mobile Number is invalid if it doesn't match the pattern defined in the MDMS config and if the number equals to the invalid number.
The Update number popup for employees requires a few documents to be uploaded. Citizens must provide the OTP received on the new number to update details.
Citizens must provide the OTP received on the new number to update details.
Update number component related files are present in the egov-ui-kit packages available in the link below.
Update API is used to update the property mobile number
property-services/property/_update
To update the number, just update the owner.mobileNumber
To update alternate number the API used is
property-services/property/_addAlternateNumber
Update owner.alternatemobilenumber
Click on the Edit Existing Number. A popup appears to update the number.
Enter the new number that needs to be added. Click on Send OTP.
UI makes an API call to user-otp/v1/_send with type as login to send the otp if it is registered.
PT Alternate Number feature enables owners to add an alternate number for the property.
We can add an alternate number while creating the property. The system also provides the option to add an alternate number after making a payment.
Alternate Number component details link
Steps To Add Alternate Number
Click on Add Alternate Number. A popup opens to add the alternate number.
The system sends an OTP to the registered number.
Once the user enters the OTP, the system validates it.
Enter the new number that needs to be added. Click on the Send OTP button.
Once the OTP is entered, it verifies and validates the user in both cases (in case of register the citizen gets registered).
Once the OTP is validated, the Property Update call is triggered to update the number in the property object.
UI makes an API call to user-otp/v1/_send with type as login to send the OTP if it is registered.
If it fails then type register in the same API to create a new user.
Once the OTP is entered, it verifies and validates the user in both cases (in case of register the citizen gets registered).
Once the OTP is validated, the Property Update call is triggered to add the alternate number in the property object.
1531
CITIZEN
4
/property-services/property/_search
1897
CITIZEN ,PT_CEMP
API
Action Id
Roles
1
property-services/property/_addAlternateNumber
870
CITIZEN,PT_CEMP
2
property-services/property/_update
954
CITIZEN,PT_CEMP
3
user-otp/v1/_send
"MdmsCriteria": {
"tenantId": "pb",
"moduleDetails": [
{
"moduleName": "PropertyTax",
"masterDetails": [
{
"name": "UpdateNumber"
}
]
}
]
}invalidNumber: "9999999999"
invalidPattern: "^[6789][0-9]{9}$"
skipEnabled: true
warningEnabled: true
documents:[]
