> 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/aadhar-integration/wage-seeker-modification.md).

# Wage Seeker Modification

## Context

Wage seeker’s modification to be changed to validate the individual’s AADHAAR through AADHAAR integration.

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

1. There is change in modification screens to accommodate the AADHAAR validation.
2. User is given an option to select the identity document and enter the document number.
3. In case, identity document selected is AADHAAR validate button is displayed.
4. In case of other document selected, validation button is not displayed.

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

#### Validate <a href="#validate" id="validate"></a>

On validate, API is called and AADHAAR is validated.

1. On valid AADHAAR, a inline success message is displayed and “Next” button is enabled to move to next page.

```
AADHAAR provide is valid!
```

2. On invalid AADHAAR, a inline invalid message is displayed and “Next” button is kept disabled.

```
 AADHAR provided is invalid, enter a valid AADHAAR or choose any other idetity document!
```

3. On failure, a inline invalid message is displayed and “Next” button is kept disabled.

```
Validation process failed, try again or choose any other idetity document!
```

4. On selection of any other identity document, other than AADHAAR, “Validate” action is not displayed and user is allowed to move to next scree if case all the required detail is entered.

#### Save <a href="#save" id="save"></a>

Save the record in system.

#### Validations <a href="#validations" id="validations"></a>

1. All existing validation
2. Validation button is displayed only when identity document selected as AADHAAR.

### Configurations <a href="#configurations" id="configurations"></a>

None

## User Interface <a href="#userinterface" id="userinterface"></a>

<figure><img src="https://content.gitbook.com/content/Oahp3xBKoPsr1r1NAaNj/blobs/G5qnWq1wyJ8SxhnRqiYg/Desktop%20-%2041.png" alt=""><figcaption></figcaption></figure>

<figure><img src="https://content.gitbook.com/content/Oahp3xBKoPsr1r1NAaNj/blobs/PWJmptc7mbiqKr38YtX1/Desktop%20-%2043.png" alt=""><figcaption></figcaption></figure>

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

1. Change in Individual Details Page to accommodate AADHAAR validation.
2. AADHAAR validation is implementation only when identity document selected AADHAAR.


---

# 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/aadhar-integration/wage-seeker-modification.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.