The vendor registry is a system that enables urban local body (ULB) employees to create and search a vendor, that is, the desludging operator (DSO) and driver entities with appropriate vehicle entities for the FSM application. This document contains the details about how to set up the vendor and describe the functionalities provided.
Pre-requisites
Before you proceed with the configuration, make sure the following pre-requisites are met:
Java 8
Kafka server is up and running.
egov-persister service is running and has a 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
Added payment payment preference and agency attributes for DSO
Added gender attribute in the create and update APIs for Vendor
Updated the Vendor search API to add vehicleCapacity in the search parameter to search all vendors matching the vehicle capacity specified in the search parameter.
Introduced Vendor Tab.
Option to add/remove/update Vendor individually.
Users can add vehicles and drivers.
search for the list of all vehicles not associated with any vendors.
Users can enable or disable the vendor.
Introduced Driver Tab.
Option to add/remove/update driver individually.
Users should be able to create/update/enable/disable a driver from the driver screen.
Functionality to add/remove directly from driver to vendor.
Deployment Details
Deploy the latest version of the vendor.
Add vendor-persister.yml file in the config folder in git and add that path in persister . (The file path is to be added in the environment yaml file in param called persist-yml-path ) and restart egov-persister-service.
Configuration Details
MDMS Configuration
Business Service / Workflow Configuration
NA
Actions & Role Action Mapping
After adding actions and role-action mappings, restart the egov-mdms-service
The DSO for FSM system is a vendor. For every city/ULB, a DSO should be created with the representative details as owner, associated vehicles and drivers.
Any system or DIGIT module can be integrated with the vendor service. It helps to manage the vendor with the vehicles, drivers and owner for representatives, and login for the representative/owner to login into the system to carry our role-specific operations.
Integration Benefits
Validation of DSO/vendor availability.
Fetch the vehicle assigned to the DSO.
Fetch the drivers assigned to the DSO.
Steps to Integration
FSM to call vendor/v1/_search to fetch the DSOs.
FSM can call vendor/v1/_search to fetch the DSO’s and the respective vehicles and drivers.
Interaction Diagrams
Reference Docs
Doc Links
Workflow Technical Document
User technical document
MDMS technical document
NEEDS TO BE UPDATED
IDGen technical document
NEEDS TO BE UPDATED
Localisation technical document
NEEDS TO BE UPDATED
Persister technical document
NEEDS TO BE UPDATED
SMS notification technical document
NEEDS TO BE UPDATED
API contract
Postman scripts
API List
Title
Link
/vendor/v1/_create
/vendor/v1/_search
/vendor/v1/_plainsearch
/vendor/v1/_update
/vendor/driver/v1/_create
/vendor/driver/v1/_update
/vendor/driver/v1/_search
Last updated
Was this helpful?
Integrate the following below changes in vendor-persister.yml .