User Interface Design

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

MDMS Configuration

• citymodule needed to run campaign module in an environment:

  Link: https://github.com/egovernments/egov-mdms-data/blob/UNIFIED-QA/data/mz/tenant/citymodule.json

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

• roleactions config needed for the user for all campaign access

  Link: https://github.com/egovernments/egov-mdms-data/blob/UNIFIED-QA/data/mz/ACCESSCONTROL-ROLEACTIONS/roleactions.json

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

  LINK: https://github.com/egovernments/egov-mdms-data/blob/UNIFIED-QA/data/mz/ACCESSCONTROL-ACTIONS-TEST/actions-test.json

  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:

• 1528

• 1763

• 1764

• 1765

• 1766

• 1767

• 1768

• 1769

• 1770

• 1771

• 1772

• 1773

• 1774

• 1775

• 1776

• 1777

• roles need to be added in roles

  Link: https://github.com/egovernments/egov-mdms-data/blob/UNIFIED-QA/data/mz/ACCESSCONTROL-ROLES/roles.json

{
      "code": "CAMPAIGN_MANAGER",
      "name": "Campaign Manager",
      "description": "Campaign Manager"
    }

• Boundary Schema config needs to be added for boundary sheet validation:

  Link: https://github.com/egovernments/egov-mdms-data/blob/UNIFIED-QA/data/mz/health/hcm-admin-console/boundarySchema.json

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

  Link:https://github.com/egovernments/egov-mdms-data/blob/UNIFIED-QA/data/mz/health/hcm-admin-console/facilitySchema.json

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

  Link: https://github.com/egovernments/egov-mdms-data/blob/UNIFIED-QA/data/mz/health/hcm-admin-console/userSchema.json

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

  Link: https://github.com/egovernments/egov-mdms-data/blob/UNIFIED-QA/data/mz/health/hcm-admin-console/hierarchyConfig.json

DevOps Configuration

• Global configuration needs to be added to environments.

  Link: https://github.com/egovernments/DIGIT-DevOps/blob/unified-env/deploy-as-code/helm/environments/unified-uat.yaml

• Helm chart needs to be added in DevOps.

  Link: https://github.com/egovernments/DIGIT-DevOps/blob/unified-env/deploy-as-code/helm/charts/frontend/workbench-ui/Chart.yaml

• Refer here to learn more about the setup environment.

Localisation

Module	Use
rainmaker-common	For all common screen localisation messages like login, homepage, sidebar
rainmaker-campaignmanager	For all 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 get this BOUNDARY_HIERARCHY_TYPE from the MDMS