Steps to Enable a New Campaign Type in Console
In the following steps, the creation of a new project type has been shown with code 'NTD' and a collection has been shared below in which {{projectTypeCode}} must be assigned with the new project type code:
Step 1: Configure products and variants
Create some products to be added for this campaign. The product-create and product-variant create curls do the same for a product named 'Praziquantel' under the type 'TABLET'. We have provided a sample object of 'product' and "productVariant" below. The "productId" will be obtained after creating the product.
"Product": [
{
"tenantId": "dev",
"type": "TABLET",
"name": "Praziquantel"
}
]"ProductVariant": [
{
"tenantId": "dev",
"productId": "P-2025-01-09-009569",
"variation": "600mg",
"sku": "Praziquantel - 600mg",
"additionalFields": {
"schema": "ProductVariant",
"version": 1,
"fields": [
{
"value": "NTD",
"key": "{{projectType}}"
}
]
}
}
]Step 2: Configure project-type template
Create a new project type. In the collection, we have used the project type 'NTD'. The projectType NTD creates a new project.
Add the 'group' and 'type' as needed. The examples we have used here are 'MALARIA' and "multiround" respectively.
Change the 'ID' in the 'data' object provided in the collection as it should be unique.
Assign the "beneficiaryType" as per your usage. Here we have used "INDIVIDUAL". You can use any one of these:
"INDIVIDUAL"
"HOUSEHOLD"The 'cycles' and 'deliveries' can be prefilled or kept empty according to your choice. Here we have populated it with one cycle and one delivery as shown below:
Add the resource details of the product created in the first step like this:
"resources": [
{
"name": "Praziquantel - 600mg",
"productVariantId": "PVAR-2025-01-09-000145",
"isBaseUnitVariant": true
}
]The final constructed project type will be:
Step 3: Configure delivery attributes
Update data in the schema named "allAttributes":
"moduleName": "HCM-ADMIN-CONSOLE"
"masterName": "allAttributes"Search for the attributes in MDMS. The collection has the curl named "Search allAttributes data". MDMS search is like this:
"MdmsCriteria": {
"tenantId": "dev",
"schemaCode": "HCM-ADMIN-CONSOLE.allAttributes"
}From this, select the attribute you want to link to your project type, and put it in the update curl. The collection has several attributes and the curls to update them. Sample update data is given below:
"Mdms": {
"id": "f0f1c893-3f93-43ac-a18d-6f52b757b29c",
"tenantId": "dev",
"schemaCode": "HCM-ADMIN-CONSOLE.allAttributes",
"uniqueIdentifier": "height",
"data": {
"key": 4,
"code": "height",
"i18nKey": "CAMPAIGN_ATTRIBUTE_HEIGHT",
"projectTypes": [
"CO-DEL",
"MR-DN",
"{{projectTypeCode}}"
]
},
"isActive": true,
}Ensure attributes are set correctly, as they will be used during delivery rule creation.
Step 4: Configure target template
Next, add data to the schema named "adminSchema": We have added two data with 'uniqueIdentifier' as "boundary.{{projectTypeCode}}" and "boundaryWithTarget.{{projectTypeCode}}" as follows:
After this, add localisations for the newly created project type. The collection has the localisation messages as per the 'NTD' project created. You can modify it according to your needs.
Step 5: Configure target mapping for the dashboard
Add the target configuration like the one provided below:
"data": {
"campaignType": "{{projectTypeCode}}",
"beneficiaries": [
{
"columns": [
"HCM_ADMIN_CONSOLE_TARGET_{{projectTypeCode}}_COLUUM_1",
"HCM_ADMIN_CONSOLE_TARGET_{{projectTypeCode}}_COLUUM_2"
],
"beneficiaryType": "HOUSEHOLD"
},
{
"columns": [
"HCM_ADMIN_CONSOLE_TARGET_{{projectTypeCode}}_COLUUM_3"
],
"beneficiaryType": "INDIVIDUAL"
}
]
}Step 6: Configure checklist templates
Refer to the default checklist added or refer to the documentation for how to add default checklist templates.
Step 7: Configure localisation messages
We have provided a collection where you can add localisation for the specified locale (language) in an environment. If your environment supports three languages, ensure you perform the upsert for all three languages by modifying the message and locale accordingly.
Example of Locale "en_MZ"
Finally, restart the "localization" and "project-factory" services to prevent data issues in templates.
We are not suggesting the creation of a new campaign type at this time. We already have a campaign type called 'codelivery', which covers all the different use cases. However, if a new campaign type is required and recommended by WHO when project types are created, you can proceed with its creation. A project type is essentially a known template used for creating and delivering campaigns.
Was this helpful?