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

# Reject Work Order

## Context

Reject the work order.

## Actors

Employees

## Actions

1. To reject the work order, action is provided to capture the below-given detail and reject the work order.
   * **Comments** - Text area - Mandatory
   * **Attach Supporting Document** - Document upload
   * **Reject** - Action Button
   * **Cancel** - Action Button
2. On Reject,
   * The pop-up window is closed, toast reject message is displayed.
   * The work order page is refreshed. No actions are enabled for the rejected work order.
   * The work order creator is informed about the rejection of the work order through SMS notification.
   * Workflow state changes as given below.

| Role                                       | From State       | To State | Status   |
| ------------------------------------------ | ---------------- | -------- | -------- |
| \<the role having access of reject action> | \<Current State> | Rejected | Rejected |

3\. On cancel, a toast cancel message is displayed on the view work order page.

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

Work order has been rejected successfully.

**Failure Message:**

Rejection of work order is failed.

**Toast Cancel Message:**

Action has been cancelled.
{% endhint %}

## Notifications

*SMS to the creator’s mobile*

Work order \<work order no.> for the project \<project name> of the location \<location> has been rejected by \<username+designation>. For more detail please login to MUKTASoft to view the work order details.

## **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%3A33715\&t=ewVSJBLAMoyry76D-4)

## **Acceptance Criteria**

<table><thead><tr><th width="212">Acceptance Criteria</th><th>Description</th></tr></thead><tbody><tr><td>1</td><td>On reject, the work order is rejected and the workflow state/status changes accordingly.</td></tr><tr><td>2</td><td>No further actions can be performed on a rejected work order.</td></tr><tr><td>3</td><td>Notification is sent to the work order creator.</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/reject-work-order.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.