> 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/detailed-mb/edit-mb.md).

# Edit MB

## Scope

Edit Detailed Measurement Book

Home > Measurement Book> MB Inbox > Edit MB

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

ULB: MB Creator

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

1. A measurement book can be edited during the workflow only.
2. Edit of measurement book should be configurable and can be enabled for any of workflow users.
3. As of now it is enabled for estimate creator only.
4. The attributes defining detailed measurement are given in below table.

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

1. Save - It is to save the details captured for detailed MB and keeping MB with editor.
2. Generate Utilization- Generate the utilization statement out of saved detailed MB details.
3. Submit - It is to allow the user to forward the MB for verification/ next action.
4. View Utilization Statements - It will take the user to view utilization statement HTML page.
5. View MB History - To display all the MBs created so far as per the detail provided in the table above.

#### On Save

1. Changes gets save successfully.
2. No change in workflow state.
3. Toast success message is displayed.
4. Page gets refreshed and opened in editable mode.

`Changes saved successfully.`

#### On Submit

1. Changes gets saved.
2. Utilization statements are revised.
3. MB is forwarded to next user in the workflow.
4. Toast message is displayed with success message based on the workflow state transition.

#### On Generate Utilization

1. Changes gets saved.
2. The utilization is generated and success toast message is displayed.

`Utilization statements are generated successfully.`

`Utilization statements generation failed.`

### 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>

<https://www.figma.com/file/M2P3O9WlKtxuLCjQKxLLDg/DIGIT-Works?type=design&node-id=9137-30903&mode=design&t=iYj7FtnLquFhW5r2-4>

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

1. MB can be edited during the workflow only.
2. Once approved it can not be edited.
3. Actions and messages are to be taken care.


---

# 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/detailed-mb/edit-mb.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.