Vehicle Registry v1.3
- Kapil Gupta (Unlicensed)
- Aman Kumar (Unlicensed)
Overview
Vehicle Registry is a system that enables ULB Employees to create and search Vehicle Entities and schedule Vehicle Trip for FSM Application and track the VehicleTrip. This document contains the details about new enhancements made to the Vehicle service as part of FSM v1.2.1 release and how to setup the Vehicle 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 vehicle-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-perister
egov-mdms-service
egov-workflow-v2
egov-idgen
Key Functionalities
EXISTING
DSO or ULB can create multiple vehicle trips based on the number of trips entered while submitting the FSM application.
FSTPO can decline the vehicle trip with appropriate reason.
Owner attribute has been added to the vehicle.
FSTPO Vehicle Log Inbox Enhancements to include Application No search filter so that FSTPO can view all the vehicle trips associated with the application.
FSPTO vehicle log API upgraded to show trip numbers in case of multi-trip application.
ENHANCEMENT
Introduced Vehicle Tab.
Option to add/remove/update vehicle individually.
Admin can enable or disable the vehicle.
Functionality to add/remove vehicles to vendor.
Deployment Details
Deploy the latest version of vehicle
Add vehicle-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 restartegov-persister-service.Integrate the following below changes in vehicle-persister.ymlhttps://github.com/egovernments/configs/commit/2e536376408a0f09a2afe03c478201f5d81edfe4
Configuration Details
https://github.com/egovernments/configs/commit/32a7e1b606ac2b7466c83007e07d104d75153695
https://github.com/egovernments/configs/commit/23237c8f467684c452461c5d0bf88ff54157fb8b
https://github.com/egovernments/configs/commit/9b2f6043694a2f23e5a2bce83600e4b41a99b7f5
https://github.com/egovernments/configs/commit/482185f1a79ad094f716e480922374e40c6e217a
https://github.com/egovernments/configs/commit/56da639add16c412056aeac119517abd434a5ece
History for egov-persister/vehicle-persister.yaml - egovernments/configs
configs/vendor-persister.yaml at DEV · egovernments/configs
MDMS Configuration
Add master data in MDMS service with module name as Vehicle and restart egov-mdms-service. Following is some sample master data for
SuctionType
{
"tenantId": "pb",
"moduleName": "Vehicle",
"SuctionType": [
{
"code": "SEWER_SUCTION_MACHINE",
"name": "Sewer suction machine",
"active": true
},
{
"code": "SEWER_SUCTION_CUM_JETTING_MACHINE",
"name": "Sewer suction cum jetting machine",
"active": true
}
]
}
VehicleOwner
{
"tenantId": "pb",
"moduleName": "Vehicle",
"VehicleOwner": [{
"name": "ULB",
"code": "ULB",
"active": true
},
{
"name": "Private",
"code": "Private",
"active": true
}
]
}
VehicleMakeModel
{
"tenantId": "pb",
"moduleName": "Vehicle",
"VehicleMakeModel": [
{
"code": "MAHINDRA",
"name": "Mahindra",
"active": true
},
{
"code": "MAHINDRA.BOLERO_PICKUP",
"name": "Bolero Pickup",
"active": true,
"make": "MAHINDRA",
"capacity": "5000",
"amount": "500"
},
{
"code": "TATA",
"name": "TATA",
"active": true
},
{
"code": "TATA.LPT709/34",
"name": "TATA LPT709/34",
"active": true,
"make": "TATA",
"capacity": "2000",
"amount": "200"
},
{
"code": "TATA.407",
"name": "TATA 407",
"active": true,
"make": "TATA",
"capacity": "1000",
"amount": "100"
},
{
"code": "TAFE",
"name": "TAFE",
"active": true
},
{
"code": "TAFE.TRACTOR_45DI",
"name": "TAFE Tractor 45DI",
"active": true,
"make": "TAFE",
"capacity": "10000",
"amount": "1000"
},
{
"code": "SONALIKA",
"name": "Sonalika",
"active": true
},
{
"code": "SONALIKA.TRACTOR_35DI",
"name": "Sonalika Tractor 35DI",
"active": true,
"make": "SONALIKA",
"capacity": "8000",
"amount": "1000"
}
]
}
FSTPORejectionReason (Vehicle decline reason codes)
SAN-1049: Added role actions for Driver APIs. · egovernments/egov-mdms-data@fb8e530
SAN-1063: Added the permissiosn for Vehicle trip creation · egovernments/egov-mdms-data@632ee94
Business Service / Workflow Configuration
Search the FSM_VEHICLE_TRIP workflow by the given search api.
/egov-workflow-v2/egov-wf/businessservice/_search? tenantId=pb.amritsar&businessServices=FSM_VEHICLE_TRIP
2. Update this below given action at “null” state at line no. 20 for FSM_VEHICLE_TRIP in below workflow and restart the workflow service
Actions & Role Action Mapping
Actions
Role Action Mapping
Infra Ops Configuration
Configurations that we can manage through values.yml vehicle in infraops repo as follows
values.yml for vehicle can be found
Description | name in values.yml | Current Value |
|---|---|---|
id-gen host, to generate the application number |
|
|
mdms service host |
|
|
workflow v2 service host |
|
|
user service host, to get the locale data |
|
|
Kafka Consumer Group |
|
|
kafka topic to which service push data to save new vehicle application |
|
|
kafka topic to which service push data of the vehicleTrip to save |
|
|
kafka topic to which service push data of the vehicleTrip to update |
|
|
kafka topic to which service push data of the vehicleTrip to update the status |
|
|
VehicleTrip Appilcatiion Number format` |
|
|
Configurations sample in Values.yml
Data Setup
Create Vehicle
Create Vehicle with the one of the vehicleType available in the VehicleMakeModel MDMS
Sample Curl
Integration
Integration Scope
Integrated with Application through REST API to create, and search vehicles.
For any module where vehicle Trip is required, can integrate REST API trip/v1/create, update, search
Integration Benefits
Vehicle Managed would become easy
Trip Management would become easy
Steps to Integration
FSM Application can
vehicle/v1/_searchto validate the fsm vehicle assignmentFSM Application call
vehicle/trip/v1/_createon assigning vehicle to the ApplicationFSTP operator can mark the vehicleTrip as DISPOSED.
Interaction Diagram
Reference Docs
Doc Links
Title | Link |
Workflow Technical Document | |
User Technical Document | |
MDMS Technical Document | NEEDS TO BE UPDATED |
IDGen Technical Document | NEEDS TO BE UPDATED |
Localization 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 |
| |
| |
| |
/vehicle/trip/v1/_create | |
| |
| |
| |
|