> 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/sanitation/water-sanitation-product-suite/waste-management-system/faecal-sludge-management-fsm/fsm-functional-specification/fsm-ui-docs/fsm-employee-ui.md).
# FSM Employee UI
There are three main updates in FSM v1.2.1 for employee UI:
1. Application timeline
2. Photo viewed by employee/DSO
3. Payment mode while completing request
### 1. Application Timeline:
An employee can see the application status in application timeline with provider details.
#### Technical Implementation Details:
The path for the code:
**frontend/micro-ui/web/micro-ui-internals/packages/modules/fsm/src/pages/employee/ApplicationDetails/index.js**
The code snippet to render application timeline:
The code snippet for extracting the provider info for each status:
### 2. Photo viewed by employee/DSO
An employee/DSO can view the photo uploaded by the employee/DSO in complete request action.
#### Technical Implementation Details:
The path for the code:
**frontend/micro-ui/web/micro-ui-internals/packages/modules/fsm/src/pages/employee/ApplicationDetails/index.js**
The code snippets to render the field:
ViewImages.js are the common component used to fetch and render the Image file id. The path is shown below:
**frontend/micro-ui/web/micro-ui-internals/packages/modules/fsm/src/components/ViewImages.js**
### 3. Payment mode while completing request
An employee has to select the payment mode while completing the request.
#### Technical Implementation Details:
File path:
**frontend/micro-ui/web/micro-ui-internals/packages/modules/fsm/src/pages/employee/ApplicationDetails/config/CompleteApplication.js**
The code snippet to render the field.
MDMS file fetch for payment mode:
[egov-mdms-data/ReceivedPaymentType.json at UAT ยท egovernments/egov-mdms-data](https://github.com/egovernments/egov-mdms-data/blob/UAT/data/pg/FSM/ReceivedPaymentType.json)
```
{
"tenantId": "pg",
"moduleName": "FSM",
"ReceivedPaymentType": [
{
"name": "Payed in Cash",
"code": "PAYED_IN_CASH",
"active": true
},
{
"name": "Payed in Counter",
"code": "PAYED_IN_COUNTER",
"active": true
},
{
"name": "Netbanking",
"code": "NETBANKING",
"active": true
}
]
}
```
---
# 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/sanitation/water-sanitation-product-suite/waste-management-system/faecal-sludge-management-fsm/fsm-functional-specification/fsm-ui-docs/fsm-employee-ui.md?ask=&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.