Page Comparison

Overview

Vendor Registry is a system that enables ULBEmployees to create and search Vendor i.e Desluding Operator (DSO) and driver entities with appropriate vehicle Entities for FSM Application. This document contains the details about how to setup the Vendor and describe the functionalities provided.

...

• Java 8

• Kafka server is up and running

• egov-persister service is running and has vendor-persister config path added in it

• PSQL server is running and database is created to store FSM Application data

• Following services should be up and running:

  • egov-mdms-service

  • egov-user-service

  • boundary-service

  • vehicle-service

Key Functionalities

EXISTING

1. Added payment payment preference and agency attributes for DSO

2. Added gender attribute in the create and update APIs for Vendor

3. Updated the Vendor search API to added vehicleCapacity in the search parameter to search all vendors matching the vehicle capacity specified in the search parameter.

ENHANCEMENT

1. Introduced Vendor Tab.

2. Option to add/remove/update Vendor individually.

3. User can add vehicle and driver.

4. search for the list of all vehicles not associated with any vendors. 

5. User can enable or disable the vendor.

6. Introduced Driver Tab.

7. Option to add/remove/update driver individually.

8. User should be able to create/update/enable/disable a driver from driver screen.

9. Functionality to add/remove directly driver to vendor.

Deployment Details

1. Deploy the latest version of vendor

2. Add vendor-persister.yml file in config folder in git and add that path in persister . (The file path is to be added in environment yaml file in param called persist-yml-path ) and restart egov-persister-service.

3. Integrate the following below changes in vendor-persister.yml

   https://github.com/egovernments/configs/commit/95dd26f926ec44d07448926ee4b6b7e031847a57

4. https://github.com/egovernments/configs/pull/2237/files

...

...