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
  • MDMS Configuration
  • Devops Configuration
  • Localisation

Was this helpful?

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

User Interface Design

PreviousHCM Console WebNextCreate New Campaign

Was this helpful?

Below are the configurations needed for successfully setting up the campaign module:

MDMS Configuration

  • citymodule needed to run campaign module in an environment:

    Link:

{
      "module": "Campaign",
      "code": "Campaign",
      "active": true,
      "order": 10,
      "tenants": [
        {
          "code": "mz"
        }
      ]
    },

  • roleactions config needed for the user for all campaign access

    Link:

  • actionTest config needed for sidebar action and user access for services

    LINK:

    To enable action in the sidebar, add navigationUrl and path to the object

{
      ```
      "path": "1Campaign.Mycampaign",
      "navigationURL": "/workbench-ui/employee/campaign/my-campaign",
      "leftIcon": "dynamic:EstimateIcon",
      "rightIcon": ""
    },

Refer to the below id's link in QA:

  • roles need to be added in roles

{
      "code": "CAMPAIGN_MANAGER",
      "name": "Campaign Manager",
      "description": "Campaign Manager"
    }
  • Boundary Schema config needs to be added for boundary sheet validation:

  • Facility Schema config needs to be added for facility sheet validation:

  • User schema config needs to be added for user sheet validation:

  • Hierarchy config needs to be added to define lowset hierarchy in boundary selection:

Devops Configuration

  • Global configuratio needs to be added to environments.

  • Helm chart needs to be added in devops.

Localisation

Module
Use

rainmaker-common

For all common screen localisation messages like login, homepage, sidebar

rainmaker-campaignmanager

For all admin console related screens localisation messages

rainmaker-hcm-admin-schemas

For all upload schemas like target, facility, user

boundary-${BOUNDARY_HIERARCHY_TYPE}

For boundary type localisations, we are getting this BOUNDARY_HIERARCHY_TYPE from the mdms

Link:

Link:

Link:

Link:

Link:

Link:

Link:

Refer to learn more about the setup environment.

https://github.com/egovernments/egov-mdms-data/blob/UNIFIED-QA/data/mz/tenant/citymodule.json
https://github.com/egovernments/egov-mdms-data/blob/UNIFIED-QA/data/mz/ACCESSCONTROL-ROLEACTIONS/roleactions.json
https://github.com/egovernments/egov-mdms-data/blob/UNIFIED-QA/data/mz/ACCESSCONTROL-ACTIONS-TEST/actions-test.json
1528
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
https://github.com/egovernments/egov-mdms-data/blob/UNIFIED-QA/data/mz/ACCESSCONTROL-ROLES/roles.json
https://github.com/egovernments/egov-mdms-data/blob/UNIFIED-QA/data/mz/health/hcm-admin-console/boundarySchema.json
https://github.com/egovernments/egov-mdms-data/blob/UNIFIED-QA/data/mz/health/hcm-admin-console/facilitySchema.json
https://github.com/egovernments/egov-mdms-data/blob/UNIFIED-QA/data/mz/health/hcm-admin-console/userSchema.json
https://github.com/egovernments/egov-mdms-data/blob/UNIFIED-QA/data/mz/health/hcm-admin-console/hierarchyConfig.json
https://github.com/egovernments/DIGIT-DevOps/blob/unified-env/deploy-as-code/helm/environments/unified-uat.yaml
https://github.com/egovernments/DIGIT-DevOps/blob/unified-env/deploy-as-code/helm/charts/frontend/workbench-ui/Chart.yaml
here