> 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/sandbox/platform/architecture/sandbox-ui/low-level-design/modules/boundary-data-management.md).

# Boundary Data Management

## **Overview**

The Boundary Management Module is designed to manage Boundary data within the system. This includes components, setting up master data, creating new entries,&#x20;

<figure><img src="https://383170073-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLTNzsJMDGVoewNjC1V95%2Fuploads%2Fn0cG3oLHNKjwsaZdPbpu%2FUI%20Tech%20Designs%20-%20Boundary%20Module.jpg?alt=media&amp;token=3579c1b2-3b08-4d2b-a2c1-29e2368e5814" alt=""><figcaption><p>Boundary Management</p></figcaption></figure>

## **Components**

**1. Boundary Home**

* **Purpose:** The main landing page for the Boundary Management module.
* **Components:**
  * Navigation to other submodules.
  * Display of tenant information retrieved from the host app.

**2. Boundary Hierarchy Type Selection/Creation**

* **Purpose:** Allows users to select or create a boundary hierarchy type.
* **Components:**
  * Dropdown or list for selecting existing hierarchy types.
  * Button or form to create a new hierarchy type.

**3. Create Hierarchy**

* **Purpose:** Interface for creating a new boundary hierarchy.
* **Components:**
  * Form fields to input hierarchy details.
  * Validation and submission controls.

**4. Create Boundary Data**

* **Purpose:** Interface for creating boundary data within the selected hierarchy.
* **Components:**
  * Form fields to input boundary data.
  * Dropdowns or selectors for hierarchy levels.
  * Validation and submission controls.

**5. View Boundary Upload Status**

* **Purpose:** Displays the status of boundary data uploads.
* **Components:**
  * Table or list view to display upload statuses.
  * Filters and search functionality for easier navigation.

## **Navigation and Flow**

* Users start at the **Boundary Home**.
* From **Boundary Home**, they can navigate to **Boundary Hierarchy Type Selection/Creation**.
* In **Boundary Hierarchy Type Selection/Creation**, they can either select an existing hierarchy or navigate to **Create Hierarchy** to create a new one.
* After selecting or creating a hierarchy, users move to **Create Boundary Data** to input boundary details.
* Finally, users can navigate to **View Boundary Upload Status** to check the status of their uploads.

### Web API sequence Diagrams

{% tabs %}
{% tab title="Boundary Management" %}

<figure><img src="https://383170073-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLTNzsJMDGVoewNjC1V95%2Fuploads%2FhUYEbGBesz9TXC1B7vSA%2FScreenshot%202024-08-08%20at%207.34.56%20PM.png?alt=media&amp;token=157e5458-36d1-4635-8b71-b0c13c5df544" alt=""><figcaption><p>Boundary Management</p></figcaption></figure>
{% endtab %}

{% tab title="Second Tab" %}

{% endtab %}
{% endtabs %}


---

# 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/sandbox/platform/architecture/sandbox-ui/low-level-design/modules/boundary-data-management.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.
