> 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/work-order/send-back.md).

# Send Back

## Context

Send the work order back to the previous user in the workflow.

## Actors

Employees

## Actions

1. **Send Back** action is provided with the below details to be captured.
   * **Comments** - Text area - Non-mandatory - *It is provided to add any remarks/instructions to be passed on to the previous user in the workflow.*
   * **Attach Supporting Document** - Document upload - Non-mandatory - *In case any documents are to be attached.*
   * **Send Back** - Action Button
   * **Cancel** - Action Button
2. On Send Back,
   * The pop-up window is closed, and a toast success message is displayed.
   * The view work order page is refreshed and the action menu is loaded according to the role of the logged-in user.
   * The work order is sent back to the previous user’s inbox.
   * Workflow states change as per the flow.

| Role                | From State               | To State                 | Status    |
| ------------------- | ------------------------ | ------------------------ | --------- |
| Work Order Verifier | Pending for verification | Pending for correction   | Sent Back |
| Work Order Approver | Pending for approval     | Pending for verification | Sent Back |

3. On cancel, the toast cancel message is displayed on top of the view work order page.

{% hint style="info" %}
**Toast Success Message:**

Work order has been sent back successfully.

**Failure Message:**

Sending back of work order is failed.

**Toast Cancel Message:**

Action has been cancelled.
{% endhint %}

## **Notifications**

Not applicable.

## **User Interface**

[<img src="https://static.figma.com/uploads/b6df2735e4cb368306acf5480b50f96e69f96099" alt="" data-size="line">DIGIT-Works](https://www.figma.com/file/M2P3O9WlKtxuLCjQKxLLDg/DIGIT-Works?node-id=2325%3A33359\&t=ewVSJBLAMoyry76D-4)

## **Acceptance Criteria**

<table><thead><tr><th width="200">Acceptance Criteria</th><th>Description</th></tr></thead><tbody><tr><td>1</td><td>On send back, the pop-up window is closed and a toast success message is displayed. The view work order page is refreshed.</td></tr><tr><td>2</td><td>The work order is sent back to the previous user in the workflow and the workflow timeline gets updated.</td></tr><tr><td>3</td><td>Workflow state changes based on the role as mentioned in the story above.</td></tr><tr><td>4</td><td>On cancel, the pop-up window is closed and a toast cancel message is displayed.</td></tr></tbody></table>


---

# 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/work-order/send-back.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.