DIGIT Docs
v0.3
  • DIGIT Knowledge Base
  • Local Governance
v0.3
  • Introducing HCM Console
  • Release Notes
    • v0.3: Release Notes
      • v0.3 Technical Release Summary
      • Service Build Updates
      • Master Data Management Service (MDMS) & Configuration Updates
      • HCM Console Test Cases V0.3
      • Gate 2 Release Checklist
        • Release Showcase
    • v0.2: Release Notes
      • v0.2 Technical Release Summary
      • Service Build Updates
      • Master Data Management Service (MDMS) & Configuration Updates
    • v0.1: Release Notes
      • v0.1 Technical Release Summary
      • Service Build Updates
      • Master Data Management Service (MDMS) & Configuration Updates
      • Gate 2 Release Checklist
  • PRODUCT SPECIFICATION
    • User Manual
    • Product Requirement Document (PRD)
    • Functional Specifications
  • TECHNOLOGY
    • Architecture
      • High Level Design
        • Project Factory
      • Low Level Design
        • Project Factory (Campaign Manager)
          • Create Campaign
          • Update Campaign
          • Manage Resources
        • Admin Console
          • Campaign Creation Flow
          • Campaign Updation Flow
          • Checklist Management
      • Services
        • Project Factory
          • Manage Campaign APIs
            • Microplan Integration
            • Update an Ongoing Campaign
          • Manage Data APIs
            • Target Upload
          • Manage Boundary APIs
            • Boundary Generation
            • Boundary Management
            • Boundary Management Through GeoJson
        • HCM Console Web
          • User Interface Design
          • Manage Campaign
            • Setup Campaign (New Campaign)
              • Campaign Details
              • Boundary Details
              • Delivery Details
              • Resource Upload Details
              • Summary Screen
              • Setup Campaign from Microplan
              • Setup and Implementation of Campaign
              • IRS Console Support
            • My Campaign
              • My Campaign Actions
              • Campaign Timeline
              • Update Campaign (Boundary/ Resources)
              • Update Campaign Dates
          • Boundary Data Management
          • Manage Checklist
            • Default Templates
  • SETUP
    • Installation
    • Configuration
      • UI Configurations
      • Steps to Enable a New Campaign Type in Console
      • Advanced Configurations
    • Quality Assurance Testing
      • Automation - Run HCM Console Script
        • User
        • Target
        • Facility
      • Performance Testing
  • GENERAL
    • Product Roadmap
Powered by GitBook

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

On this page
  • Boundary Details
  • Boundary Details Summary
  • Localisation Details
  • API Details

Was this helpful?

Export as PDF
  1. TECHNOLOGY
  2. Architecture
  3. Services
  4. HCM Console Web
  5. Manage Campaign
  6. Setup Campaign (New Campaign)

Boundary Details

PreviousCampaign DetailsNextDelivery Details

Last updated 5 months ago

Was this helpful?

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.

The working of this screen is as follows:

We will fetch the boundary data according to the hierarchy saved in the MDMS.

The hierarchy structure and the lowest boundary will be fetched from the MDMS 

HCM-ADMIN-CONSOLE.HierarchySchema

This screen will be shown using the component

Which internally calls the - Selecting boundary component

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

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

The file where data is fetched -

For more information on the master data can be referred

File Path -

https://github.com/egovernments/DIGIT-Frontend/blob/console/health/micro-ui/web/micro-ui-internals/packages/modules/campaign-manager/src/Module.js
https://github.com/egovernments/DIGIT-Frontend/blob/console/health/micro-ui/web/micro-ui-internals/packages/modules/campaign-manager/src/components/SelectingBoundariesDuplicate.js
DIGIT-Frontend/health/micro-ui/web/micro-ui-internals/packages/modules/campaign-manager/src/components/SelectingBoundaryComponent.js at console · egovernments/DIGIT-FrontendGitHub
Logo
Boundary details
Summary
here