> 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/local-governance/v2.8/platform/configure-digit/configuring-digit-services/water-services/water-and-sewerage-service-ui-docs/employee-modify-create-flow.md).

# Employee: Modify Create Flow

Water and Sewerage modify create application feature for employees - technical implementation doc

**Objective:** The Apply and Modify feature in the WS module allows counter employees to create or modify Water and Sewerage applications.

Every application is a part of the workflow.

## **Workflow Details** <a href="#validations" id="validations"></a>

Once a new application connection is activated, the system generates the consumer code. This code is used to route users to the connection details screen from the search/connection screen.\
\
Clicking on the Take Action button displays multiple options based on conditions. Clicking on the Modify Connection option routes users to the modify screen.

<figure><img src="https://1885278393-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUYtUmELy66UydIQtJOn5%2Fuploads%2FyXJhbmozagRPZu9vqjq7%2Fimage.png?alt=media&amp;token=890232f9-5fde-4e2a-9449-6d571ac08def" alt=""><figcaption></figcaption></figure>

![](https://1885278393-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUYtUmELy66UydIQtJOn5%2Fuploads%2FQZomnaG4iXrwcsHk8AYn%2Fimage.png?alt=media\&token=fdbe5647-4595-4064-ac9e-455592e12154)

#### **Validations** <a href="#validations" id="validations"></a>

* To disconnect, the connection should be in an **ACTIVE** state. Connections which are under **WORKFLOW** or **INACTIVE** are not eligible for Modify.

**Connection details**: [Employee: Water and Sewerage Connection Details](/local-governance/v2.8/platform/configure-digit/configuring-digit-services/water-services/water-and-sewerage-service-ui-docs/employee-connection-details.md)

#### **Acknowledgement screen**

<div align="left"><figure><img src="https://1885278393-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUYtUmELy66UydIQtJOn5%2Fuploads%2Fz3YbKSXjJAVb8rn3GB2I%2Fimage.png?alt=media&amp;token=5001a8da-d0a2-46b9-931e-07b37ff8bebb" alt=""><figcaption></figcaption></figure></div>

#### W\&S-Application <a href="#w-and-s-application" id="w-and-s-application"></a>

Creating an application on the water and sewerage module generates an acknowledgement form that can be downloaded by users. Processing the applications pending field inspection and user payment generates the Estimation Letter and Sanction Letter respectively. Find the configuration details for enabling the download of these documents.

**Acknowledgement Download**

Users can download the acknowledgement after submitting the W\&S Create application.

<figure><img src="https://1885278393-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUYtUmELy66UydIQtJOn5%2Fuploads%2F4xMFV4WGrJEDfdF9rGFG%2Fimage.png?alt=media&amp;token=05cf11cc-b077-4343-bd8e-ff2eba23c48c" alt=""><figcaption></figcaption></figure>

## Technical Implementation Details

File Path: <https://github.com/egovernments/DIGIT-Dev/blob/develop/frontend/micro-ui/web/micro-ui-internals/packages/modules/ws/src/pages/employee/ModifyApplication/index.js>

**Data fetch, load and render**:

`ws-services/wc/_create`

`sw-services/swc/_create`

**Case 1: In the case of Water connections:**

* Clicking on the Submit button calls the `ws-services/wc/_create` API and creates the application. The update API `ws-services/`is called after getting a successful response on creating the application.

**Case 2: In the case of Sewerage connections:**

* Clicking on Submit button calls the `sw-services/swc/_create` API and creates the application. The update API `sw-services/swc/_update`is called after getting a successful response on creating the application.

Successful create and update calls routes users to the acknowledgement screen.

File Path: <https://github.com/egovernments/DIGIT-Dev/blob/develop/frontend/micro-ui/web/micro-ui-internals/packages/modules/ws/src/pages/employee/WSResponse.js>

File Path: <https://github.com/egovernments/DIGIT-Dev/blob/develop/frontend/micro-ui/web/micro-ui-internals/packages/modules/ws/src/pages/employee/WSResponse.js>

For the application PDF, all related code is written to the W\&S folder in the below-mentioned file.

File Path: <https://github.com/egovernments/DIGIT-Dev/blob/develop/frontend/micro-ui/web/micro-ui-internals/packages/modules/ws/src/utils/getWSAcknowledgementData.js>

## **Role Action Mapping**

| API                             | Roles              | Action ID    |
| ------------------------------- | ------------------ | ------------ |
| `/egov-mdms-service/v1/_search` | `WS_CEMP, SW_CEMP` | `954`        |
| `/ws-services/wc/_create`       | `WS_CEMP, SW_CEMP` | `1899, 1917` |
| `/sw-services/swc/_create`      | `WS_CEMP, SW_CEMP` | `1899, 1917` |
| `/ws-services/wc/_update`       | `WS_CEMP, SW_CEMP` | `1899, 1917` |
| `/sw-services/swc/_update`      | `WS_CEMP, SW_CEMP` | `1899, 1917` |
| `/filestore/v1/files/url`       | `EMPLOYEE`         |              |


---

# 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/local-governance/v2.8/platform/configure-digit/configuring-digit-services/water-services/water-and-sewerage-service-ui-docs/employee-modify-create-flow.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.
