> 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/reference-implementations/odisha-sujog/implementation-checklist.md).
# Implementation Checklist
This document calls out the various tasks the teams need to perform before the FSM application is released to production.
| **Sl No.** | **Checklist** | **Reference** | **Owner** | **Completed(Yes/No/Partially/WIP)** | **Remarks** |
| ---------- | ------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------- | ---------- | ----------------------------------- | ----------------------------------------------------------------------------------- |
| 1 | Product Release Gate Checklist FSM 1.3 | [Checklist](/sanitation/water-sanitation/release-notes/service-build-update.md) | Riddhi | Yes | |
| 2 | Get the list of common services that need to be upgraded mandatory for FSMv1.3 to function | | Riddhi | NA | There is no changes to common services |
| 3 | Get the list of SMS template changes and new templates to be loaded as part of v1.3 | | Riddhi | Yes | 4 new templates have to be added |
| 4 | Upgrade the eGov Test environment with the changes listed in FSMv1.3 release | | Taresh | Yes | |
| 5 | Sanity testing of FSM on eGov test server | | Venu | Yes | |
| 6 | Make pull requests for Code, Configs, MDMS on to PwC repo | | Aman | Yes | |
| 7 | Merging the pull request after verification | | PWC team | Yes | |
| 8 | Share FSM related service Builds to PwC team | | Riddhi | Yes | |
| 9 | Loading the incremental localisation codes on UAT | | Taresh | Yes | |
| 10 | Sharing the changes and additional SMS templates that need to be applied for UAT and production with PwC team | | Riddhi | NA | |
| 11 | Getting the SMS templates approved | | PWC team | In Progress | |
| 12 | Deploy Builds to UAT environment | | Taresh/PwC | Yes | All FSM builds will be deployed by eGov team. Only MDMS restart will be done by PwC |
| 13 | Sanity in PwC UAT(Sujog Dev) for FSM | | Venu | Yes | |
| 14 | QA in Sujog UAT for FSM | | Venu | Yes
| |
| 15 | All tasks and issues that are part of the v1.3 release are updated as UAT completed | | Riddhi | Yes | |
| 16 | All Sujog modules are tested with the lasted changes on UAT | | PwC team | Yes | |
| 17 | Functional Sign off on UAT | | Shrija | In Progress | |
| 18 | Deployment on Sujog Production | | PwC team | Yes | |
| 19 | Testing on Sujog production using the testing tenant | | Venu | Yes | |
| 20 | Marking all FSMV1.3 upgrade tasks as DONE | | Riddhi | In Progress | |
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.digit.org/sanitation/reference-implementations/odisha-sujog/implementation-checklist.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.