To add new ulb/tenant for FSM,following steps should be followed:

• Add data in MDMS

• After this,restart the mdms service and check the status in ui.The tenant will be added in ui.

• Create Employee and FSTP login credientials.

• Plant Mapping of tenant

• Push the localisation of all the slums and Gram Panchayat in tenant.

• Push the billing-slab of new tenant

• Push the vendor-vehicle data of new tenant

• Import this curl :

  Copy

  curl --location --request POST 'https://sujog-dev.odisha.gov.in/fsm/plantmap/v1/_create' \
  --header 'Content-Type: application/json' \
  --data-raw '{
      "RequestInfo": {
          "apiInfo": {
              "id": "string",
              "version": "string",
              "path": "string"
          },
          "deviceDetail": {
              "id": "string",
              "signature": "string"
          },
          "ts": 0,
          "action": "string",
          "key": "string",
          "msgId": "string",
          "requesterId": "string",
          "authToken": "45092a19-3dab-43b0-a9e1-19e8a6c94923",
          "userInfo": {"id":3186071,"userName":"FSM_ADMINDEV","salutation":null,"name":"Taresh","gender":"MALE","mobileNumber":"7721827042","emailId":"vddvd@gmail.com","altContactNumber":null,"pan":null,"aadhaarNumber":null,"permanentAddress":null,"permanentCity":null,"permanentPinCode":null,"correspondenceAddress":null,"correspondenceCity":null,"correspondencePinCode":null,"active":true,"locale":null,"type":"EMPLOYEE","accountLocked":false,"accountLockedDate":0,"fatherOrHusbandName":"Dilip","relationship":"FATHER","signature":null,"bloodGroup":null,"photo":null,"identificationMark":null,"createdBy":575,"lastModifiedBy":1,"tenantId":"od.cuttack","roles":[{"code":"EMPLOYEE","name":"Employee","tenantId":"od"},{"code":"FSM_ADMIN","name":"FSM Administrator","tenantId":"od.cuttack"},{"code":"HRMS_ADMIN","name":"HRMS ADMIN","tenantId":"od.cuttack"},{"code":"SUPERUSER","name":"Super User","tenantId":"od.cuttack"},{"code":"FSM_COLLECTOR","name":"FSM Payment Collector","tenantId":"od"},{"code":"FSM_CREATOR_EMP","name":"FSM Employee Application Creator","tenantId":"od"},{"code":"FSM_EMP_FSTPO","name":"FSM FSTP Opperator","tenantId":"od"},{"code":"SUPERUSER","name":"Super User","tenantId":"od"},{"code":"FSM_EDITOR_EMP","name":"FSM Employee Application Editor","tenantId":"od"},{"code":"FSM_ADMIN","name":"FSM Administrator","tenantId":"od"}],"uuid":"2f3851cd-864e-42d7-869c-d5a05abb8f39","createdDate":"01-09-2022 17:04:45","lastModifiedDate":"17-01-2023 13:49:59","dob":"21/11/1995","pwdExpiryDate":"30-11-2022 17:04:44"}
      },
      "plantMapping": {
          "employeeUuid": "c3249480-b45c-43b6-bfe1-cb78330d258c",
           "plantCode": "ODAG_064",
          "tenantId": "od.odagaon",
          "status":"ACTIVE"
      }
  }'

• Login from FSTP credientials and copy the uuid of FSTP user.

• Take FSTP plantCode from MDMS PlantInfo.json file for specific ulb.

• The status should be always ACTIVE.

• Login from FSM_ADMINDEV credentials(for sujog-dev) which is having FSM Admin role for all the ulb’s.

• Copy the auth token and user-info. Paste the auth token in the req. Body “authToken” field.

• Hit the url.

1. Import the curl :

   Copy

   curl --location --request POST 'https://fsm-2.3.digit.org/localization/messages/v1/_upsert?tenantId=pg' \
   --header 'Content-Type: application/json' \
   --data-raw '{
       "RequestInfo": {
           "apiId": "Rainmaker",
           "ver": ".01",
           "ts": "",
           "action": "_create",
           "did": "1",
           "key": "",
           "msgId": "20170310130900|hi_IN",
           "authToken": "94a4a1dd-5691-4534-88ce-d3440c2e1b85",
           "userInfo": {
               "id": 118,
               "userName": "TLCreator",
               "salutation": null,
               "name": "TLCreator",
               "gender": "MALE",
               "mobileNumber": "6666666666",
               "emailId": null,
               "altContactNumber": null,
               "pan": null,
               "aadhaarNumber": null,
               "permanentAddress": null,
               "permanentCity": null,
               "permanentPinCode": null,
               "correspondenceAddress": "Bang",
               "correspondenceCity": null,
               "correspondencePinCode": null,
               "addresses": [
                   {
                       "pinCode": null,
                       "city": null,
                       "address": "Bang",
                       "type": "CORRESPONDENCE",
                       "id": 235,
                       "tenantId": "uk.haldwani",
                       "userId": 118,
                       "addressType": "CORRESPONDENCE",
                       "lastModifiedDate": null,
                       "lastModifiedBy": null
                   }
               ],
               "active": true,
               "locale": null,
               "type": "EMPLOYEE",
               "accountLocked": false,
               "accountLockedDate": 1571224291053,
               "fatherOrHusbandName": "Test",
               "signature": null,
               "bloodGroup": null,
               "photo": null,
               "identificationMark": null,
               "createdBy": 4,
               "lastModifiedBy": 1,
               "tenantId": "uk.haldwani",
               "roles": [
                   {
                       "code": "PTCEMP",
                       "name": "PT Counter Employee",
                       "tenantId": "uk.haldwani"
                   },
                   {
                       "code": "TL_CEMP",
                       "name": "TL Counter Employee",
                       "tenantId": "uk.haldwani"
                   }
               ],
               "uuid": "573dd472-ebbc-4bbd-b093-897d33f95980",
               "createdDate": "07-10-2019 17:51:18",
               "lastModifiedDate": "13-11-2019 12:19:55",
               "dob": "1/10/2019",
               "pwdExpiryDate": "05-01-2020 17:51:18"
           }
       },
       "tenantId": "pg",
       "messages": [
           {
               "code": "FROM_OTHER_ULB",
               "message": "Other",
               "module": "rainmaker-fsm",
               "locale": "en_IN"
           }
       ]
   }'

2. Login to Super_user and copy the auth token

3. Change the req. Url to env you want to push also the auth token

4. Add the localisation message in the request body.

5. Hit the url.

Reference Localisation Doc :

All localisations of FSM : https://docs.google.com/spreadsheets/d/1RWqP-h_s0lJZnQ9RvFOIePdy7Hxle-RN/edit?usp=sharing&ouid=109809705320882389789&rtpof=true&sd=true

https://docs.google.com/document/d/1z-V8U8BvT1Ict1gRyf4b4aOCjr_snJ-Psk6A_5oKzWs/edit?usp=sharing

https://drive.google.com/drive/folders/1bIv4txLjOSt2L4DsNWkShSgmZFzo73yU?usp=drive_link

Important points :

1. Related modules for FSM : rainmaker-fsm,rainmaker-common,rainmaker-dss

2. Push the localisation for all the modules separately

3. After pushing the localisation,make a file to store all the localisations according to modules.

After adding all the data for ulb in MDMS,next step is to create user for Employee and FSTP.

From HRMS, Create Employee user and FSTP user of new tenant and add roles to it.

EMPLOYEE USER Example

FSTP USER Example

• Set the password of EmployeeId by checking the logs of sms service.

For adding the rate slabs(pricing) of vehicles,consider different combination of propertyType , slum and tank capacity.

• Required combination of property types and Sub-property types added in MDMS :

1. RESIDENTIAL and RESIDENTIAL.SUB-PROPERTY_TYPE

2. INSTITUTIONAL and INSTITUTIONAL.SUB-PROPERTY_TYPE

3. COMMERCIAL and COMMERCIAL.SUB-PROPERTY_TYPE

• Consider billing slab property types and Sub-property types for both slum and non-slum areas.Take slum='YES' for slum areas and take slum='NO' for non-slum areas.

• Sample Data for pricing : - The pricing is provided according to Vehicle capacity,property-types and slum areas.

Within the tenant,For two Vehicles having the same capacity,the pricing should be same. Example : In Vehicle-1 and Vehicle-3,for capacity 1000,pricing for Residential properties with Slum='NO' = 1000 Commercial properties with Slum='NO' = 1000 Institutional properties with Slum='NO' = 1000 Residential properties with Slum='YES' = 800 Commercial properties with Slum='YES' = 800 Institutional properties with Slum='YES' = 800

• Loading Rate Slabs Steps:

1. Import this collection - https://www.getpostman.com/collections/d039948bfdf20f7286ad

2. Change the request url specific to environment.

For search billing-slab(url) - https://sujog-dev.odisha.gov.in/fsm-calculator/v1/billingSlab/_search? tenantId=od.rourkela&limit=-1

For create billing-slab(url) - https://sujog-dev.odisha.gov.in/fsm-calculator/v1/billingSlab/_create

For update billing-slab(url) - https://sujog-dev.odisha.gov.in/fsm-calculator/v1/billingSlab/_update

1. Login from FSM_ADMINDEV credentials(for sujog-dev) which is having FSM Admin role for all the ulb’s.

2. Copy the auth token. Paste the auth token in the req. Body “authToken” field.

3. Download these files - https://drive.google.com/drive/folders/1cmEcpnvOHiGeq0pKpuznzWKoIYXL4VEI?usp=sharing and update the file by changing the different combination of propertyType , slum and tank capacity with respect to tenant/ulb.

4. Open the runner tab (ctrl+shift+R) and import the file which is shared in the step 5. (For example: billing-athagarh.json for pushing athagarh billing slab).

5. Drag the api which is provided in Step 1 collection.

6. Hit the postman collection.

IMPORTANT POINTS:

1.The format of billing slab data is:

{
    "tenantId": "{{tenantId}}",
    "capacityFrom": "{{capacityFrom}}",
    "capacityTo": "{{capacityTo}}",
    "propertyType": "{{propertyType}}",
    "slum": "{{slum}}",
    "price": "{{price}}",
    "status": "{{status}}"
}

Eg.

{
    "tenantId": "pg.rourkela",
    "capacityFrom": 0,
    "capacityTo": 1000,
    "propertyType": "RESIDENTIAL",
    "slum": "YES",
    "price": 800,
    "status": "ACTIVE"
}

2.The capacity always starts from 0.

3.Example. If the given capacity is 1000 and 3000 then the range should be:

"capacityFrom": 0,

"capacityTo": 1000,

"capacityFrom": 1001,

"capacityTo": 3000,

4.Consider billing-slab for both slum and non-slum areas.

5.The status is always ACTIVE.

6.If the price of all the slums is given as 0,then mark zeroPricingStatus as true otherwise mark it as false in MDMS.

How to update billing slab data:

1. The format of updating billing slab data is:

{
    "id": "{{id}}",
    "tenantId": "{{tenantId}}",
    "capacityFrom": "{{capacityFrom}}",
    "capacityTo": "{{capacityTo}}",
    "propertyType": "{{propertyType}}",
    "slum": "{{slum}}",
    "price": "{{price}}",
    "status": "{{status}}",
    "auditDetails": {
        "createdBy": "0ea42eb0-4406-4acf-91b0-52eca31403ab",
        "lastModifiedBy": "0ea42eb0-4406-4acf-91b0-52eca31403ab",
        "createdTime": 1685258218048,
        "lastModifiedTime": 1685258218048
    }
}

2.If the need is to update the price for all the slums from 800 to 500,for this Take the response from search api for slum “YES”,make a json file with updated price and push it using runner with the syntax mentioned in point 1.

Eg. https://drive.google.com/file/d/11GqEB3mtDO2A9g5P6ilbBOUSuN0kPGgx/view?usp=sharing

Zero Pricing property in billing-slab :

For some combination of property types and sub-property types,the zero pricing property is given.For that,the price will be considered as 0(zero) for all the capacities and slum areas.

Ways to load Vendor details :

• From Api

• By FSM Registry

Loading from API :

Steps:

1. Import this collection -

2. Change the request url specific to environment.

For Create DSO(URL) :

For Search DSO(URL) :

For Update DSO(URL) :

1. Login from FSM_ADMINDEV credentials(for sujog-dev) which is having FSM Admin role for all the ulb’s.

2. Copy the auth token. Paste the auth token in the req. Body “authToken” field.

3. Request Info (eg. anandapur ulb) for Create DSO :-

Note:

2. No special characters allowed in Vendor name.

3. Vehicle Registration number should be unique for every vehicle.

4. Scenerios for Vendor and Vehicle users: - One Vendor can be linked with two or more vehicles. - One Vehicle is linked with One Vendor. - Two Vendors can’t have same mobile number because vendor is a user and user is stored uniquely in database. - Vendor owner, Vehicle owner and Driver owner can be same or different for One Vehicle.

5. Hit the url it’ll push the data of vendor.

From FSM Registry :

Add details of Cesspool Operator,Vehicle and Driver from FSM Registry and link Vehicle with Cesspool operator and Driver with Cesspool Operator.