> 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/implementation/training-resources/user-manual/web-application-user-manual/rates-revision.md).

# Rates Revision

This feature enables users to revise the rate of Works SORs upon updating either rate analysis or the rates of basic SORs. The rate revision is treated as a job and scheduled with a future effect

## Revise Rate

1. Click the Revise Rate action button on the View Rate Analysis page to revise the rate.

<figure><img src="https://lh7-us.googleusercontent.com/docsz/AD_4nXc4Dow-m__vIMen21-Ytq511EE3qnNrcQtzpAmNx89mp_q7VIY16M_rNDz8hMp72LRDnzr3rnzgdAnKP7sXXhKd-reRjJxKr17GaX_x69AqWBqjtR66KKUv6fnBZNSgcpYKO87tA-KB_H_0_TtLYOrVWKU?key=3EUJoyAOI7dmW2nyiqGGsA" alt=""><figcaption><p>View Rate Analysis</p></figcaption></figure>

2. Additionally from the Home Page, select the menu Revision of Rates.

<figure><img src="https://lh7-us.googleusercontent.com/docsz/AD_4nXe7Bu_OX4QFc79x2nVTYQWY41acWvmE_pEPThwKLPhx2XGVdV7VS_QwLwMEisjdM2iMEKOWobM8csH7w9Wb61EeZ7T9WuWUd-KugLj9u1AXTnCuZRqx1nGH23gd4HthyF-pjOGNPUbXogC5jvPuKc_c7A?key=3EUJoyAOI7dmW2nyiqGGsA" alt=""><figcaption><p>Home Page</p></figcaption></figure>

3. The Search SOR page displays the works SORs listing. Select the applicable SOR to revise the rate.

<figure><img src="https://lh7-us.googleusercontent.com/docsz/AD_4nXfytKp0zrWQY8s-aAPxQeUZsfqPA8Cwf6JpfX_n6QGW5SE5mMSsCynPPfJPDeoV0P9bRweKBLKx_yUOaWCiLWzy9k6hBXV55fHXLsQQw-va2Cvh7nqHwLSywqAd2EH1RaUmYnkpEA4XVULwcjm-BBPqbng?key=3EUJoyAOI7dmW2nyiqGGsA" alt=""><figcaption><p>Search SOR</p></figcaption></figure>

4. Schedule the rate vision for selected or for all the SORs without selecting SORs.
5. A JOB will get scheduled and the same can be seen from “Show JOB”.

## **View Scheduled Jobs**

This feature enables the user to see all the jobs scheduled for revising the rate with the details given below.

1. JOB ID - It is a system-generated ID to identify the job uniquely
2. Scheduled on date - It is the date on which the job is scheduled
3. Effective from - It is the effective date of rates from which new rates will become effective and the existing rates will get closed on the previous day of this date
4. Number of SORs scheduled - It is the number of SORs scheduled to revise the rate
5. Successful  - It is the count of SORs for which the rate is revised successfully
6. Failed - It is the count of SORs for which rate revision failed
7. Status - Status of job

<figure><img src="https://lh7-us.googleusercontent.com/docsz/AD_4nXcHzMTyRh5mO7vpR5GvQ8rIO6UjajedAoJqrh9xdy72NEVbi3aQ169WEKA-7ERmxvZq2rNKAUIfaRGSybVcJc3Us4WqPiVV7Q-f8sKnnHSzIpzkchZ56fVBf1fE20JhlSr83uA1O7acx7ct3s_ooRzpyrM?key=3EUJoyAOI7dmW2nyiqGGsA" alt=""><figcaption><p>View Scheduled Jobs</p></figcaption></figure>


---

# 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/implementation/training-resources/user-manual/web-application-user-manual/rates-revision.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.