# Configure

## Objective

To ensure the **Complaints Management** functions smoothly across all interfaces—**citizen portal, mobile app, dashboards, and employee interfaces**—a set of core configurations must be completed **before deploying the service**.

***

## Configurations Needed 

Before deploying the `ccrs-services` application image, the following configurations and data must be **preloaded**:

1. **Workflow Configuration**\
   Define workflows for each stage of the complaint lifecycle (e.g., registration, assignment, resolution, closure).
2. **Master Data (MDMS)**\
   Load necessary master data, including service definitions, complaint types, departments, roles, and ULB information.
3. **Localisation Messages**\
   Add translations for all UI labels, error messages, and service names across supported languages.
4. **Persister Configuration**\
   Configure how and where data will be stored (PostgreSQL DB mappings for CMS-related actions).
5. **SLA Configuration**\
   Establish service-level agreements for each complaint type and department to monitor and track resolution timelines.
6. **IDGen Configuration**\
   Define ID formats for generating unique complaint IDs using the ID generation service.
7. **Inbox & Indexer Configuration**\
   Configure inbox filters for employees and indexing settings for search and reporting.
8. **Boundary Configuration**\
   Load geospatial boundaries (e.g., wards, zones) to map complaints accurately to locations.