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:

{
      "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

PreviousHCM Console Web NextCreate New Campaign

Was this helpful?