DIGIT Docs
v0.2
  • DIGIT Knowledge Base
  • Local Governance
v0.2
  • Introducing HCM Console
  • Release Notes
    • 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
      • Low Level Design
        • Project Factory (Campaign Manager)
      • Services
        • Project Factory
          • Campaign Manage APIs
          • Data Manage APIs
            • Target Upload
          • Boundary Campaign Setup
            • Boundary Generation
        • HCM Console Web
          • User Interface Design
          • Create New Campaign
            • Campaign Details
            • Delivery Details
            • Boundary Details
            • Resource Upload Details
            • Setup and Implementation of Campaign
            • Summary Screen
          • Change Campaign Dates
          • My Campaign
            • Action Column Integration
          • Boundary Bulk Upload
          • Campaign Timeline
  • SETUP
    • Installation
    • Configuration
    • 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

Was this helpful?

Export as PDF
  1. TECHNOLOGY
  2. Architecture
  3. Services
  4. HCM Console Web

Boundary Bulk Upload

PreviousAction Column IntegrationNextCampaign Timeline

Was this helpful?

This screen allows the user to create a new hierarchy and then upload the boundary data in bulk.

  1. Upload Boundary Screen

This screen allows the user to select the hierarchy. According to that, a template is downloaded in which the user needs to fill in the boundary data. If the hierarchy type is not present, then the user can make a new hierarchy using this screen.

  1. Create Boundary Hierarchy

The user needs to give a hierarchy name, and levels according to the hierarchy.

UI Validation: Headers should be according to the template downloaded.

API Details

EndPoint
MDMS Roles
Method
Payload

/boundary-service/boundary-hierarchy-definition/_create

1759 - CAMPAIGN_MANAGER

POST

{ "tenantId": "mz", "hierarchyType": "test", "boundaryHierarchy": [ { "boundaryType": "country", "parentBoundaryType": null, "active": true }, { "boundaryType": "state", "parentBoundaryType": "country", "active": true } ] }

/project-factory/v1/data/_create

1772- CAMPAIGN_MANAGER

POST

{ "tenantId": "mz", "type": "boundary", "fileStoreId": "1f984e91-2ed2-4d5c-8788-37b3a4c8fcbc", "action": "create", "hierarchyType": "test", "additionalDetails": {} }

/boundary-service/boundary-hierarchy-definition/_search

1760-CAMPAIGN_MANAGER

POST

{ "tenantId": "mz" }

Upload Boundary
create boundary hierarchy