> 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/works/reference-implementations/muktasoft-v2.2/specifications/functional-requirements/user-stories/estimate-template/modify-template.md).

# Modify Template

## Scope

Modify Estimate Template

Home > Search Template> Template Code (Hyperlink) > View Template> Modify (action)

## Actors <a href="#actors" id="actors"></a>

State: STATE\_MUKTA\_ADMIN

## Details <a href="#details" id="details"></a>

1. Modify template is provided to enable the users to make the correction in the existing template details.
2. The attributes which are allowed to modify are as given below table.

<table data-header-hidden><thead><tr><th width="73"></th><th width="128"></th><th width="119"></th><th width="127"></th><th></th></tr></thead><tbody><tr><td>Sr. No.</td><td>Field</td><td>Data Type</td><td>Is Mandatory ?</td><td>Description</td></tr><tr><td>1</td><td>Code</td><td>Display</td><td>Yes</td><td>A unique code generated for template.</td></tr><tr><td>2</td><td>Project Type</td><td>Drop-down</td><td>Yes</td><td>Project types values from master data.</td></tr><tr><td>3</td><td>Name</td><td>Text</td><td>Yes</td><td>Name given to template.</td></tr><tr><td>4</td><td>Description</td><td>Text</td><td>Yes</td><td>The description, describing the template in detail.</td></tr><tr><td>5</td><td>Status</td><td>Drop-down</td><td>Yes</td><td>Status of the template Active/ Inactive</td></tr><tr><td>5</td><td>Search SOR</td><td>Search</td><td>Yes</td><td>To search an SOR and add to the template.</td></tr><tr><td>6</td><td>SORs</td><td> </td><td> </td><td> </td></tr><tr><td>6.1</td><td>Sr. No.</td><td>Display</td><td>Yes</td><td>Serial number.</td></tr><tr><td>6.2</td><td>Sub Type</td><td>Display</td><td>Yes</td><td>SOR Sub Type</td></tr><tr><td>6.3</td><td>SOR Code</td><td>Display</td><td>Yes</td><td>SOR Code</td></tr><tr><td>6.4</td><td>Description</td><td>Display</td><td>Yes</td><td>SOR description</td></tr><tr><td>6.5</td><td>Unit</td><td>Display</td><td>Yes</td><td>Unit of measurement</td></tr><tr><td>7</td><td>Non SORs</td><td> </td><td> </td><td> </td></tr><tr><td>7.1</td><td>Sr. No.</td><td>Display</td><td>Yes</td><td>Serial number.</td></tr><tr><td>7.2</td><td>Description</td><td>Text</td><td>Yes</td><td>Non SOR description</td></tr><tr><td>7.3</td><td>Unit</td><td>Drop-down</td><td>Yes</td><td>Unit of measurement</td></tr></tbody></table>

### Actions <a href="#actions" id="actions"></a>

Submit - On Submit,

1. Changes are saved and success toast message is displayed.
2. The existing estimates which has already used the template remains unaffected.

Changes to template are saved successfully.

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

Not applicable.

### Configuration <a href="#configuration" id="configuration"></a>

Not applicable.

### Notifications <a href="#notifications" id="notifications"></a>

Not applicable.

### User Interface <a href="#userinterface" id="userinterface"></a>

<figure><img src="https://content.gitbook.com/content/Oahp3xBKoPsr1r1NAaNj/blobs/zEhdKhejxirCOIC4Jegl/View%20Template.png" alt=""><figcaption></figcaption></figure>

## Acceptance Criteria <a href="#acceptancecriteria" id="acceptancecriteria"></a>

1. Estimate template is modified.
2. Estimates created remains unchanged.


---

# 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/works/reference-implementations/muktasoft-v2.2/specifications/functional-requirements/user-stories/estimate-template/modify-template.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.