> 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/local-governance/v2.8/products/modules/hrms/hrms-ui-configuration/auto-escalation-ui-flow.md).

# Auto Escalation UI Flow

## **Objective**

Refer to the employee inbox technical documentation below before reading the auto-escalation flow details.

{% content-ref url="/pages/xxsJfCPUMVSQNzutiH0n" %}
[Employee Inbox (Old UI)](/local-governance/v2.8/platform/configure-digit/configuring-digit-services/property-tax-service/pt-create-property-ui-details/employee-inbox-old-ui.md)
{% endcontent-ref %}

The auto-escalation option provides employees with the option to view all escalated applications that have not been acted on.

Route - <https://egov-micro-uat.egovernments.org/employee/inbox>

![](/files/-MgiGgr82NJUmMDLVOAS)

## **Technical Implementation Details**

{% hint style="info" %}
**Note**

1. The tab **ASSIGNED TO ME** is inter-changed to **ALL** vice versa and the **Escalated** tab is added in the 3rd position.
2. **Nearing Escalation and Escalated**: The localisation message of **Escalated** is changed to **SLA Breached.**
   {% endhint %}

Escalated API file path:[ <img src="https://github.com/fluidicon.png" alt="" data-size="line">frontend/actions.js at master · egovernments/frontend](https://github.com/egovernments/frontend/blob/master/web/rainmaker/dev-packages/egov-ui-kit-dev/src/redux/app/actions.js). The escalated API is called based on given conditions.

![](/files/-MgiGgrB6ZZ7wHJgmcFP)

![](/files/-MgiGgrEhAiLY1tXM49K)

1. get all applications in `payload.ProcessInstances` using `egov-workflow-v2/egov-wf/process/_search`
2. get the escalated applications in `escalatedPayload.ProcessInstances` using `egov-workflow-v2/egov-wf/escalate/_search`
3. pushing escalated applications into all applications with `isEscalatedApplication` flag with true value, for finding the escalated application in all applications.
4. This works the same as [Employee Inbox](https://digit-discuss.atlassian.net/wiki/spaces/EGR/pages/1004437517).

### **Escalated Tab**

The Escalated tab shows all Escalated applications.

The process instance response fetches all records from which the records are filtered based on the following condition:

```
if (get(item, "isEscalatedApplication", false)) {
      escalatedToMe.push([...dataRows])
  }
```

The `isEscalatedApplication` is the flag added initially for separating the escalated applications to show in the escalated tab.

### On-Click History

The functionality works as it is but the only change is showing the symbol to identify the state from which it has escalated.

Functionality file path:[ <img src="https://github.com/fluidicon.png" alt="" data-size="line">frontend/index.js at master · egovernments/frontend](https://github.com/egovernments/frontend/blob/master/web/rainmaker/packages/employee/src/modules/employee/Inbox/components/Table/index.js)

![](/files/-MgiGgrHxBz3quZnBuu9)

{% hint style="info" %}
**Note:** Inbox functionality works the same as before as outlined in the Employee Inbox document attached here.
{% endhint %}

{% content-ref url="/pages/xxsJfCPUMVSQNzutiH0n" %}
[Employee Inbox (Old UI)](/local-governance/v2.8/platform/configure-digit/configuring-digit-services/property-tax-service/pt-create-property-ui-details/employee-inbox-old-ui.md)
{% endcontent-ref %}

## **Role Action Mapping**

| API                                          | Roles      | Action ID |
| -------------------------------------------- | ---------- | --------- |
| `/egov-workflow-v2/egov-wf/escalate/_search` | `EMPLOYEE` | `2150`    |


---

# 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/local-governance/v2.8/products/modules/hrms/hrms-ui-configuration/auto-escalation-ui-flow.md?ask=<question>&goal=<endgoal>
```

`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.