> 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/health/ph-v1.7/deploy/configuration/ui-configuration/language-selection.md).

# Language Selection

### 1. Overview

The **Language Selection screen** in the DIGIT Health platform allows users to choose their preferred language before accessing application features. This ensures a personalised user experience, supporting multi-lingual interfaces as per the localisation configurations.

<div align="left"><figure><img src="https://3060978721-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FugLvZh3s3IGcc8JYqNN7%2Fuploads%2FARTuJUlf5E3eDVbUlBFK%2Fimage.png?alt=media&amp;token=e3957c87-f3de-4a35-8890-991199389cfd" alt="" width="206"><figcaption></figcaption></figure></div>

***

### 2. Workflow Details

1. **App Launch**: The language selection screen is presented immediately after launching the app.
2. **Display Available Languages**: The screen fetches and displays the list of available languages from the localisation MDMS configuration.
3. **User Selection**: The user selects their desired language.
4. **Set Locale**: The selected language is saved in the application’s state (usually in Redux or local storage).
5. **Localisation Load**: All subsequent UI screens are rendered in the selected language using the appropriate localisation files.
6. **Proceed**: User is navigated to the next screen (e.g., login or onboarding).

***

### 3. Technical Implementation

* **Configuration Source**:
  * Language options are configured in the MDMS under `common-masters` > `localization`.
  * The UI reads the available languages from this MDMS configuration.
* **UI Component**:
  * Typically implemented as a separate React component (e.g., `LanguageSelection`).
  * Uses a radio group or button group to display language choices.
  * On selection, it triggers a state update and persists the choice.
* **State Management**:
  * The selected language is stored in Redux or local storage.
  * The app uses this value to fetch and display localisation bundles.
* **Localisation Module Integration**:
  * On language change, the localisation module reloads the appropriate translation files.
* **Sample MDMS Language Config**:

  ```
  {
    "localization": [
      { "code": "en_IN", "label": "English" },
      { "code": "hi_IN", "label": "हिन्दी" }
    ]
  }
  ```

***

### 4. API Role Action Mapping

* **Relevant APIs**:
  * MDMS API to fetch localisation master data:\
    `/egov-mdms-service/v1/_search`
  * Localisation API to fetch translation bundles:\
    `/localization/messages/v1/_search`
* **Role Action Mapping**:

  * The language selection screen does not require user authentication or specific roles, as it is accessible before login.
  * However, the APIs used must be accessible to the `ANONYMOUS` role (i.e., no authentication required).
  * In the MDMS and localisation action configuration:
    * Ensure these endpoints are mapped to allow public/anonymous access.

  **Sample role-action mapping:**

  ```
  [
    {
      "rolecode": "ANONYMOUS",
      "actionid": 1010, // action ID for /egov-mdms-service/v1/_search
      "tenantId": "default"
    },
    {
      "rolecode": "ANONYMOUS",
      "actionid": 1020, // action ID for /localization/messages/v1/_search
      "tenantId": "default"
    }
  ]
  ```

Reference Links

* [Language selection screen](https://github.com/egovernments/health-campaign-field-worker-app/blob/master/apps/health_campaign_field_worker_app/lib/pages/language_selection.dart)
* [Language selection card widget](https://github.com/egovernments/health-campaign-field-worker-app/blob/master/packages/digit_components/lib/widgets/molecules/digit_language_card.dart)


---

# 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/health/ph-v1.7/deploy/configuration/ui-configuration/language-selection.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.