> 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.1/design/architecture/field-app-architecture/ui-packages/registration-and-delivery-package/multi-campaign-suppot.md).

# Multi Campaign Suppot

#### What's new for users

**New campaign types supported out of the box:**

* **SMC (Seasonal Malaria Chemoprevention)** — full MR-DN flow including cycle tracking, target/delivered counts, redose handling, and "unable to deliver" guards. Householders, members, and delivery actions are config-driven, so campaign teams can tune target ages, dose counts, and cycle length from the console.
* **Polio** — including inside-household monitoring, LQA (Lot Quality Assurance) data collection, and a configurable daily return cap for vials. Polio-specific stock details and unable-to-deliver behavior are included.
* **Bednet** — including child-count validation on the Add Member action so a bednet allocation can't be created against a household with no eligible recipients.

The default registration\_delivery package now ships with these flows alongside the standard HCM flow, and a project is bound to its campaign type at runtime via per-project config.

**Registration / Delivery UX improvements:**

* **Smarter member display in householdOverview** — after adding a new member during SMC/Polio flows, the member appears immediately without requiring a re-entry.
* **Accurate computed values** — currentRunningCycle, deliveryLength, targetCycle, and currentDelivery are now resolved correctly across cycles.
* **Cleaner button & icon set** — Edit Household, Edit Individual, and Add Member icons unified across Polio and SMC; redose / unable-to-deliver guards added on ADMINISTERED\_SUCCESS, NOT\_VISITED tags and the Delivery button so users can't act on a state that has already been resolved.
* **Hidden-condition support in forms** — fields and groups can be hidden purely by config, simplifying campaign-specific tailoring.
* **Improved beneficiary search** — a new "no result" card guides the field worker when a search returns nothing, and search performance is materially better (see platform notes).
* **Localizations loaded on startup for every supported locale** — no more missing-key blanks when switching languages mid-flow.

&#x20;**Registration & Delivery (multi-campaign, config-driven)**

<figure><img src="https://2077406040-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FI0KFbSBTySIQ7TCOKnJF%2Fuploads%2FEARCQx5C3b8Idok3vOKx%2Fimage.png?alt=media&amp;token=6520647c-ab94-46f6-8ee5-d1960f2a1440" alt=""><figcaption></figcaption></figure>


---

# 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/v2.1/design/architecture/field-app-architecture/ui-packages/registration-and-delivery-package/multi-campaign-suppot.md?ask=<question>&goal=<user_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.
