> 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/v2.1/deploy/configuration/hcm-console-configuration/console-ui-configuration/campaign-setup/boundary-details-selection.md).

# Boundary Details - Selection

## Overview

In this step, the user encounters 2 screens:

* Boundary Details
* Boundary Details Summary

## Steps

### Boundary Details

This screen allows users to select the boundaries according to their requirements.

<figure><img src="https://content.gitbook.com/content/I0KFbSBTySIQ7TCOKnJF/blobs/Hmh1ILZ3WrwsiZyQ54cB/image.png" alt=""><figcaption><p>Boundary details</p></figcaption></figure>

The working of this screen is given below.

The system fetches the boundary data according to the hierarchy saved in the MDMS.

The file where data is fetched - <https://github.com/egovernments/DIGIT-Frontend/blob/console/health/micro-ui/web/micro-ui-internals/packages/modules/campaign-manager/src/Module.js>

The hierarchy structure and the lowest boundary will be fetched from the MDMS&#x20;

```
HCM-ADMIN-CONSOLE.HierarchySchema
```

For more information on the master data, refer [here](https://docs.digit.org/health/v2.1/access/public-health-product-suite/health-campaign-management-hcm/hcm-console.md).&#x20;

File Path - <https://github.com/egovernments/DIGIT-Frontend/blob/console/health/micro-ui/web/micro-ui-internals/packages/modules/campaign-manager/src/components/SelectingBoundariesDuplicate.js>

Which internally calls the - Selecting boundary component&#x20;

{% embed url="<https://github.com/egovernments/DIGIT-Frontend/blob/console/health/micro-ui/web/micro-ui-internals/packages/modules/campaign-manager/src/components/SelectingBoundaryComponent.js>" %}

**Validation:** \
The user must select boundaries down to the lowest level. If the parent boundary is selected, then the user should select at least one of the child options.

### Summary

<figure><img src="https://content.gitbook.com/content/I0KFbSBTySIQ7TCOKnJF/blobs/3tPu0VbWgaAgbGYfk1W1/image.png" alt=""><figcaption><p>Summary</p></figcaption></figure>

This screen displays all the boundaries selected in the previous step.

### Localisation Details

Boundary localisation for this screen happens by using the combination of hierarchy type and boundary type

```
 {t((hierarchyType + "_" +boundaryType).toUpperCase())}
```

**It should be in the above-given format.**

## **API Details**

<table><thead><tr><th width="433.5390625">EndPoint</th><th>Role </th></tr></thead><tbody><tr><td>boundary-service/boundary-relationships/_search</td><td>CAMPAIGN_MANAGER</td></tr><tr><td>/boundary-service/boundary-hierarchy-definition/_search</td><td>CAMPAIGN_MANAGER</td></tr><tr><td></td><td></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/health/v2.1/deploy/configuration/hcm-console-configuration/console-ui-configuration/campaign-setup/boundary-details-selection.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.
