> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/complaints-management/cms-v2.11/deploy/customise/frontend.md).

# Frontend

## **Overview** <a href="#undefined" id="undefined"></a>

The **Complaint Management (CMS)** module in DIGIT’s frontend framework leverages two powerful, configuration-driven components from `@egovernments/digit-ui-components`:

* **FormComposerV2** – A dynamic, JSON-based React form builder that enables rapid creation of multi-step and single-page forms without hardcoding. Used for **citizen complaint submission, employee complaint creation, and workflow actions**.
* **InboxSearchComposer** – A modular search, filter, and results-view component designed for **complaint tracking, inbox management, and SLA monitoring**. Supports flexible configurations, custom UI components, and backend-driven filters.

## **Key Highlights**

* **Fully configuration-driven** – No need to hardcode UI; all fields, steps, and table columns are defined in JSON.
* **Highly reusable** – The same components are used across different screens and roles.
* **Customizable** – Supports custom React components, dynamic updates, conditional visibility, and API data transformations.
* **Mobile-responsive** – Adapts seamlessly for mobile and desktop views.
* **Integration-friendly** – Easy mapping of form inputs and search filters to backend APIs.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.digit.org/complaints-management/cms-v2.11/deploy/customise/frontend.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.