1 of 1

FSM Service

Configuration Details

Make changes in config accordingly and restart the pdf-services.

1 . pdf-service/format-config/fsm-receipt.json

2 . pdf-service/data-config/fsm-receipt.json

egov-persister/fsm-persister.yaml

Fsm v 1.4 Persister Configuration

MDMS Configuration

Add master data in the MDMS service with module name as FSM and restart the egov-mdms-service. Following is a sample master data for Application Channel (Source):

{
    "tenantId": "pb",
    "moduleName": "FSM",
    "ApplicationChannel": [
        {
            "name": "Telephone",
            "code": "TELEPHONE",
            "active": true,
            "citizenOnly":false
        },
        {
            "name": "Counter",
            "code": "COUNTER",
            "active": true,
            "citizenOnly":false
        },
        {
            "name": "Online",
            "code": "ONLINE",
            "active": true,
            "citizenOnly":true
        }
    ]
}

Checklist (To be answered by a citizen while rating):

{
	"tenantId": "pb",
	"moduleName": "FSM",
	"CheckList": [{
			"code": "SPILAGE",
			"active": true,
			"required": true,
			"type": "SINGLE_SELECT",
			"options": [
				"YES",
				"NO",
				"NA"
			]
		},
		{
			"code": "SAFETY_GEARS_USED",
			"active": true,
			"type": "MULTI_SELECT",
			"required": true,
			"options": [
				"EYE_GEAR",
				"HAND_GLOVES",
				"NOSE_MASK"
			]
		},
		{
			"code": "NUMBER_OF_TRIPS",
			"active": true,
			"type": "DROP_DOWN",
			"required": false,
			"options": [
				"1",
				"2",
				"3",
				"4",
				"5",
				"6",
				"7",
				"8",
				"9",
				"10"
			]
		}
	]
}

Configuration (At the application level):

{
    "tenantId": "pb",
    "moduleName": "FSM",
    "Config": [
        {
            "code":"noOfTrips",
            "override":true,
            "default":1,
            "active":true,
            "description":"override:true indicates, noOfTrips poperty is allowed to override in FSM."
        },
        {
            "code":"additionalDetails.tripAmount",
            "override":false,
            "active":true,
            "description":"override:true indicates, tripAmount poperty is allowed to override in FSM."
        },
        {
            "code":"slumName",
            "override":true,
            "active":true,
            "description":"override:true indicates, tripAmount poperty is allowed to override in FSM."
        },
        {
            "code":"ALLOW_MODIFY",
            "WFState":"CREATED",
            "override":[
                "propertyUsage",
                "vehicleType",
                "sanitationtype",
                "address.pincode",
                "address.city",
                "address.locality",
                "address.street",
                "address.doorNo",
                "address.landmark",
                "pitDetail"
            ],
            "active":true,
            "description":"properties in override allowed to modify when FSM application moving from CREATED Status to next status."
        }
        
    ]
}

FSTP Plant Information (For each city):

{
    "tenantId": "pb",
    "moduleName": "FSM",
    "FSTPPlantInfo": [
        {
            "PlantCode": "AMR001",
            "PlantName": "Amritsar FSTP",
            "active": true,
            "PlantType":"FSTP",
            "PlantLocation":"Amritsar",
            "PlusCode":"JQ2R+7G Khapar Kheri, Punjab",
            "PlantOperationalTimings":"10.00am-08.00pm",
            "PlantOperationalCapacityKLD":"50",
            "ULBS":"pb.jalandhar,pb.amritsar,pb.nayagaon"
        },
        {
            "PlantCode": "MOH002",
            "PlantName": "Mohali SeTPP",
            "active": true,
            "PlantType":"SeTP",
            "PlantLocation":"Mohali",
            "PlusCode":"MPFQ+V2 Sahibzada Ajit Singh Nagar, Punjab",
            "PlantOperationalTimings":"10.00am-06.00pm",
            "PlantOperationalCapacityKLD":"100",
            "ULBS":"pb.mohali,pb.phagwara,pb.nawanshahr,pb.derabassi"
        }
    ]
}

Pit Type (Type of pit):

{
    "tenantId": "pb",
    "moduleName": "FSM",
    "PitType": [
        {
            "name": "Conventional septic tank",
            "code": "CONVENTIONAL_SPECTIC_TANK",
            "active": true,
            "dimension":"lbd"
        },
        {
            "name": "Septic tank with soak pit",
            "code": "SEPTIC_TANK_WITH_SOAK_PIT",
            "active": true,
            "dimension":"dd"
        }
    ]
}

Property Type:

Slums (Mapped to the locality of the city):

PaymentType (Payment preference type):

data/pg/FSM/ReceivedPaymentType.json

data/pg/FSM/CommonFieldsConfig.json

FSM Persister YML

data/pb/BillingService/BusinessService.json

data/pb/DIGIT-UI/RoleStatusMapping.json

data/pb/BillingService/BusinessService.json

data/pb/amritsar/FSM/ZeroPricing.json

data/pb/ACCESSCONTROL-ACTIONS-TEST/actions-test.json

Following are the changes that need to be integrated in dashboard-analytics, and restart the “dashboard-analytics” service

egov-dss-dashboards/dashboard-analytics/ChartApiConfig.json

egov-dss-dashboards/dashboard-analytics/MasterDashboardConfig.json

egov-indexer/egov-vehicle.yaml

Fsm v1.4 MDMS Configuration

inbox v2 mdms changes

Business Service/Workflow Configuration

Create businessService (workflow configuration) using the /businessservice/_create. Following is the product configuration for FSM:

For post-pay new business service, FSM_POST_PAY_SERVICE has been created. Create businessService (workflow configuration) using the /businessservice/_create. Following is the product configuration for FSM_POST_PAY_SERVICE:

In the system, the FSM_POST_PAY_SERVICE and FSM (that is, the above two business services) are removed and we have introduced a new business service for advance payment application and zero price application.

For advance new business service, FSM_ADVANCE_PAY_SERVICE has been created.

Create businessService (workflow configuration) using the /businessservice/_create. Following is the product configuration for FSM_ADVANCE_PAY_SERVICE:

For advance zero new business service PAY_LATER_SERVICE has been created.

Create businessService (workflow configuration) using the /businessservice/_create. Following is the product configuration for PAY_LATER_SERVICE:

For Zero Price Application new Business service FSM_ZERO_PAY_SERVICE has been created

Create businessService (workflow configuration) using the /businessservice/_create. Following is the product configuration for FSM_ZERO_PAY_SERVICE:

Localisation Setup

Using/localisation/messages/v1/_upsert, add localisation (templates) for notification messages to be sent. Following are the product notification templates:

Actions & Role-Action Mapping

Add role-action mapping for the API’s in MDMS. Following are the required entries. They should be mapped to both CITIZEN and the appropriate employee roles.

Action Configuration

data/pg/ACCESSCONTROL-ACTIONS-TEST/actions-test.json

data/pg/ACCESSCONTROL-ACTIONS-TEST/actions-test.json

Plant user mapping

data/pg/ACCESSCONTROL-ACTIONS-TEST/actions-test.json

Role-Action Mapping

data/pg/ACCESSCONTROL-ROLEACTIONS/roleactions.json

Plant user mapping

data/pg/ACCESSCONTROL-ROLEACTIONS/roleactions.json

Devops Changes

For a new environment these changes are required.

path:- deploy-as-code/helm/charts/sanitation/fsm/values.yaml