> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/health/v1.5/setup/configuration/configuring-hcm-to-campaign-and-country-needs.md). # Configuring HCM to Campaign and Country Needs ## Overview This document will cover the steps to configure HCM for a campaign. Every new campaign in a country or province will ideally require a few configurations to be done on the basic HCM application to cater to the exact needs of the campaign. ## Steps for configuring HCM to campaign and country needs First, the application must be installed using the procedure mentioned [here](https://health.digit.org/setup/installation/install-using-github-actions-in-aws). For easy installation, you may refer to [this](https://drive.google.com/drive/folders/1IiUipCq2pvQsd1A4s8r9ki5O_M9qAdPG?usp=sharing) video. Once the application is installed, you will have access to the admin console and workbench using which a campaign can be configured to the needs of the country and campaign. 1. Loading of new boundary hierarchy/boundary a. Each country will have its boundary hierarchy, which must be configured using the console/workbench feature. Refer to the [documentation](https://egov-digit.gitbook.io/0.1/technology/architecture/services/hcm-console-web/boundary-bulk-upload) for doing this. The login URL will be the \/workbench-ui/employee/user/language-selection b. After the hierarchy has been configured, the boundary master data will be uploaded. 2. Setting up a campaign and related master data using the HCM Console a. Refer to [this](https://egov-digit.gitbook.io/0.1/product-specification/setup-campaigns/user-manual) document for using the console for campaign setup b. Set up users for various roles c. Set up all other masters for HCM 3. Setting up the configuration parameters for the HCM app a. Using the workbench link, configure the parameters per the [instructions](https://egov-digit.gitbook.io/hcm-console/v/0.1/setup/configuration). 4. Changing the labels and messages as per the campaign needs a. Login to the workbench URL, select the localisation option and appropriately change the values for the keys. Refer to [this](https://workbench.digit.org/) document for instructions. b. These localisation changes will apply to both the web and the mobile application. 5. Making the APK as per the new configuration a. Once the master data and language configuration, including loading of values are done, you are ready to make an APK. b. Follow the steps mentioned [here](https://health.digit.org/setup/installation/setup-mobile-app) to make the APK which can then be installed on your Android device. 5. Installing the APK on a device and making it ready for use a. Once the APK is made, it can be downloaded and installed on the device. b. Enable the permissions to run background services. c. Enable the permission to access the camera. d. Enable location permissions. e. Check for the other recommended prerequisites mentioned below i. ​​RAM: Recommended is 6GB and minimum is 4GB. ii. Processor: Octa-core processors. iii. Battery: Minimum 5000 mAh. The higher the mAh, the better it is. Battery consumption is heavily dependent upon phone searching, network searching, and GPS usage. iv. Screen: Generally the bigger the better for the field teams, but a minimum 6.5-inch screen size is recommended. v. Storage: Minimum 32 GB. Typically 4 GB or 6GB RAM phones are available with more than 32 GB storage. 7. Login to the new application on the device a. Click on the icon with the name HCM to open the application. b. Login using the user credentials created using the console. 8. Login to the web application log in a. Using the domain URL configured while installing, you should be able to log in to the web application. b. Select the language of your choice. c. You can use the user credentials configured using the console. d. Once logged in you can see the menu options are per the roles assigned to this user. 9. Configuring Dashboard a. Kibana will be installed as part of the installation. Visualisations relevant to the campaign can be added to the dashboard by following the steps mentioned [here](https://health.digit.org/setup/installation/setup-kibana-dashboard). b. Follow the Kibana help documents for adding new charts and graphs. c. You should be able to log in to the web application using the dashboard role the user created as part of Step 1. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.digit.org/health/v1.5/setup/configuration/configuring-hcm-to-campaign-and-country-needs.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.