Boundary Details

In this step, the user will encounter 2 screens:

• Boundary Details

• Boundary Details Summary

Boundary Details

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

Boundary details

The working of this screen is as follows:

We will fetch 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

HCM-ADMIN-CONSOLE.HierarchySchema

For more information on the master data can be referred here

This screen will be shown using the component

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

https://github.com/egovernments/DIGIT-Frontend/blob/console/health/micro-ui/web/micro-ui-internals/packages/modules/campaign-manager/src/components/SelectingBoundaryComponent.jsgithub.com

Validation: The user must select boundaries till the lowest level. If the parent boundary is selected, then the user should select at least one of its child.

Boundary Details Summary

Summary

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 this format.

API Details

EndPoint	Role
boundary-service/boundary-relationships/_search	CAMPAIGN_MANAGER
/boundary-service/boundary-hierarchy-definition/_search	CAMPAIGN_MANAGER