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
  • Overview
  • 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)

Setup Campaign from Microplan

Overview

The "Setup Campaign" feature facilitates the creation of a campaign using an approved microplan. It ensures that only authorized users can initiate the setup process, generates required campaign data, and integrates with external APIs to fetch user, facility, and target data.

. User Role Validation

  • Role Required: MICROPLAN_CAMPAIGN_INTEGRATOR

  • Validation Logic:

    • Only users with the above role can select an approved microplan to initiate the campaign setup.

    • If the user lacks the role, access to the feature is denied with a proper error message.

Campaign Object Creation

  • Input: Approved microplan object.

  • Steps:

    1. Extract the base campaign object from the selected microplan.

    2. Create a new campaign object by cloning the base campaign object with the following updates:

      • Add unique identifiers (campaignId, createdBy).

      • Set the campaign status to draft.

    3. Save the new campaign object to the backend.

Generate Empty Templates

  • Trigger: After updating the campaign object with selected boundaries, it gets auto-generated from Backend

  • Steps:

    1. Automatically generate empty templates for the campaign, including:

      • User assignments.

      • Facility data placeholders.

      • Target data placeholders.

Fetch Data from Microplan API

  • API Endpoint: project-factory/v1/project-type/fetch-from-microplan

  • Steps:

    1. Call the Microplan API to fetch:

      • User data.

      • Facility data.

      • Target data.

    2. Populate the empty templates with the fetched data.

    3. Save the updated templates back to the backend.

Campaign Search Polling

  • Purpose: Monitor the progress of data population and transition to the next step once completed.

  • Steps:

    1. The UI triggers a periodic call to the campaignSearch endpoint:

      • API Endpoint: /campaign-search

      • Parameters: campaignId.

    2. Check the status of the campaign:

      • If Completed:

        • Navigate the user to the Setup Campaign page.

      • If In Progress:

        • Re-trigger the data fetch from Microplan API to ensure completion.

        • Continue polling.

Navigation to "Setup Campaign" Page.

  • Steps:

    1. Transition the user to the Setup Campaign page.

    2. Pass the necessary campaign data as route parameters or via state management.

API Details:

Action (Api details)
Role

project-factory/v1/project-type/fetch-from-microplan

MICROPLAN_CAMPAIGN_INTEGRATOR

project-factory/v1/project-type/search

CAMPAIGN_MANAGER

project-factory/v1/project-type/create

CAMPAIGN_MANAGER

project-factory/v1/project-type/update

CAMPAIGN_MANAGER

project-factory/v1/data/_download

CAMPAIGN_MANAGER

PreviousSummary ScreenNextSetup and Implementation of Campaign

Last updated 5 months ago

Was this helpful?

fetch from microplan