> 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/v2.0/deploy/configuration/hcm-console-configuration/console-ui-configuration/hcm-console-web-ui/campaign-setup/campaign-details.md).

# Campaign Details

## Overview

The Campaign Details feature has 4 screens:

* Campaign Type
* Campaign Name
* Campaign Dates
* Campaign Details Summary

## Steps

### 1.  Campaign Type

This is the first screen that appears when the user clicks "set up campaign". In this screen, the user can select the campaign type, and the beneficiary will be prepopulated from the MDMS. This field is mandatory to set up a campaign.

<figure><img src="https://content.gitbook.com/content/mb5VUHEnO0msarLMPz6q/blobs/Kkeh7xwG5CSFOz7KWpNu/image.png" alt=""><figcaption><p>Campaign Type</p></figcaption></figure>

Here, the dropdown will show the list of campaign types in the MDMS. We will fetch the MDMS data from. For more information, check the configurations from the link [here](https://docs.digit.org/health/v2.0/deploy/configuration/hcm-console-configuration/console-ui-configuration/hcm-console-web-ui/campaign-setup/pages/HOE2bIXaoPn6bibfTTpA#id-1.-project-type-configuration)

File Path: <https://github.com/egovernments/DIGIT-Frontend/blob/campaign/micro-ui/web/micro-ui-internals/packages/modules/campaign-manager/src/components/CampaignType.js>

### 2. Campaign Name&#x20;

This screen comes after the campaign type. This step is crucial for saving your campaign as a draft, as the name serves as a unique identifier. After clicking on 'Next', the name will be saved, and the user can check the draft.

<figure><img src="https://content.gitbook.com/content/mb5VUHEnO0msarLMPz6q/blobs/4I7tOU0G8UDGCqMGB2Oe/image.png" alt=""><figcaption><p>Camapign Name</p></figcaption></figure>

File Path: <https://github.com/egovernments/DIGIT-Frontend/blob/campaign/micro-ui/web/micro-ui-internals/packages/modules/campaign-manager/src/components/CampaignName.js>

### 3. Campaign Dates

This screen asks a user to fill in the start and end dates of the campaign.&#x20;

<figure><img src="https://content.gitbook.com/content/mb5VUHEnO0msarLMPz6q/blobs/qztf7AT4DVOVF4bMrVwp/image.png" alt=""><figcaption><p>Campaign Dates</p></figcaption></figure>

FilePath: <https://github.com/egovernments/DIGIT-Frontend/blob/campaign/micro-ui/web/micro-ui-internals/packages/modules/campaign-manager/src/components/CampaignDates.js>

### 4. Summary

This screen will show the summary of the campaign details screen

<figure><img src="https://content.gitbook.com/content/mb5VUHEnO0msarLMPz6q/blobs/8KLr3aAV4Jg45IB8nM14/image.png" alt=""><figcaption><p>Campaign details summary</p></figcaption></figure>

## API Details

<table><thead><tr><th width="396.69140625">Action</th><th>Role</th></tr></thead><tbody><tr><td>project-factory/v1/project-type/create</td><td>CAMPAIGN_MANAGER</td></tr><tr><td>project-factory/v1/project-type/search</td><td>CAMPAIGN_MANAGER</td></tr><tr><td>/project-factory/v1/project-type/search</td><td>CAMPAIGN_MANAGER</td></tr><tr><td>/project-factory/v1/project-type/update</td><td>CAMPAIGN_MANAGER</td></tr></tbody></table>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.digit.org/health/v2.0/deploy/configuration/hcm-console-configuration/console-ui-configuration/hcm-console-web-ui/campaign-setup/campaign-details.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.