Estimate
Provides an overview of the configuration of the estimate service
Overview
The estimate service provides the functionality to create, update and search for estimates related to a Works project. An estimate is always linked to a project. For low-level technical design, please refer to this section.
Pre-requisites
The following services need to be running for the estimate service to function:
DIGIT backbone services (PostgreSQL, Elastic Search, Zuul)
Project
MDMS
Persister
Indexer
Workflow
User
Functionality
Please refer to the functional specifications for an overview of the functionality provided by this service.
Configuration
MDMS Configuration
Configure roles, actions and role-action mappings as per the table below by referring to this document:
ESTIMATE_CREATOR
/estimate-service/estimate/v1/_create
/estimate-service/estimate/v1/_search
/wms/estimate/_search
ESTIMATE_VERIFIER
/estimate-service/estimate/v1/_update
/estimate-service/estimate/v1/_search
/wms/estimate/_search
TECHNICAL_SANCTIONER
/estimate-service/estimate/v1/_update
/estimate-service/estimate/v1/_search
/wms/estimate/_search
ESTIMATE_APPROVER
/estimate-service/estimate/v1/_update
/estimate-service/estimate/v1/_search
/wms/estimate/_search
ESTIMATE_VIEWER
/estimate-service/estimate/v1/_search
/wms/estimate/_search
EMPLOYEE_COMMON
/inbox/v2/_search
Refer to the sample here.
Persister Configuration
The persister file for the service is called estimate-service.yml
.
https://github.com/egovernments/works-configs/blob/DEV/egov-persister/estimate-service.yml
Follow the steps here for configuring this.
Indexer configuration
Please ensure the below files are present in https://github.com/egovernments/works-configs/blob/DEV/egov-indexer/estimateservices-indexer.yml
If the above files are not present, add them in the given location and restart the ‘egov-indexer’ service in the respective environment. Before restarting the service please ensure, you have done the below configs
Note: Add this config in the respective environment YAML file in the DevOps repository and then deploy the service.
Idgen configuration
In the common-masters folder of MDMS, locate the IDFormat.json file. ID formats should be configured for the Estimate number as well as Estimate Detail objects. Make sure the following lines are added and the format modified per implementation:
Other masters for Estimate:
The following masters need to be configured for the Estimate service. Please make sure to use the same master name and module names:
Workflow Configuration
The workflow configuration for Estimate is as follows. This payload needs to be called against businessService _create API for workflow configuration:
Inbox Configuration
Inbox should be configured if Workflow is configured for the estimate service. If there is no workflow involved, this can be skipped.
Add the inbox-v2 configuration in a respective environment in MDMS as it has been done here. Below is the inbox configuration for the Estimate service:
to
Deployment
Below are the variables that should be configured well before the deployment of the estimate service build image. These are configured in the DevOps repository:
Add these ‘db-host’,’db-name’,’db-url’, ’domain’ and all the digit core platform services configurations (Idgen, workflow, user etc.) in respective environments YAML file.
Add estimate-service related environment variables’ value like the way it's done in ‘dev’ environment YAML file
Add the ‘egov-mdms-service’ related configuration to the respective environment YAML file. Make sure you change the gitsync.branch name.
Check the estimate-service persister file is added in the egov-persister.perister-yml-path variable. If not, follow the steps outlined here.
Make sure to add the DB(Postgres and flyway) username & password in the respective environment secret YAML file as per the steps given here.
Ensure that the DIGIT core services-related secrets are added to the respective environment secret file in a manner similar to how it is done here.
Integration
Postman scripts for Estimate are given below:
Last updated