Update Campaign Dates

Overview

The Update Campaign Dates feature allows users to modify:

  • Campaign start date

  • Campaign end date

  • Cycle start and end dates

This feature is available only for Ongoing and Upcoming campaigns and is accessed from the Actions column on the My Campaign screen.

The behaviour of the update screen depends on an MDMS configuration flag, which determines whether dates are updated:

  • At the root (campaign) level, or

  • At the boundary level

Steps

Step 1: Enable the “Update Dates” Action

User Flow

  1. Navigate to My Campaign.

  2. Click the Actions button for an ongoing or upcoming campaign.

  3. Select Update Dates.

Outcome

  • The user is redirected to the Update Dates flow.

  • The system evaluates the MDMS flag to decide which screen to render.

MDMS linkarrow-up-right

Step 2: Configure MDMS Flag for Date Updates

MDMS Configuration

This flag controls whether date updates are boundary-specific or campaign-wide.

MDMS File

  • dateWithBoundary.json

Behaviour

  • true → Dates can be updated per boundary

  • false → Dates are updated at the root campaign level

Step 3: Update Dates With Boundary (MDMS = true)

When dateWithBoundary = true, boundary-specific date updates are enabled.

3.1 Select Boundary

Screen Behaviour

  • User selects:

    • Hierarchy level

    • Specific boundary

  • Clicks Confirm to proceed

Key Files

  • DateWithBoundary.js

  • BoundaryWithDate.js

3.2 Modify Dates for Selected Boundary

Displayed Data

  • Start date

  • End date

  • Cycle start and end dates for the selected boundary

Edit Rules

  • Dates before the current date are read-only

  • Only valid future dates can be edited

User Action

  • Modify applicable dates

  • Click Confirm

3.3 Save and Redirect

Outcome

  • Dates are updated successfully

  • A success screen is shown

  • User is redirected back to My Campaign

File Patharrow-up-right

Step 4: Update Dates Without Boundary (MDMS = false)

When dateWithBoundary = false, date updates apply to the entire campaign.

Screen Behaviour

  • Campaign start date and end date are pre-filled

  • Cycle dates are shown at the root level

Key File

Edit Rules

  • Dates that have already passed are non-editable

  • Only future dates can be modified

User Action

  • Update required dates

  • Click Confirm

Outcome

  • Dates are saved

  • The success screen is displayed

  • User is redirected to My Campaign

File Patharrow-up-right

MDMS configurationarrow-up-right to check whether the update date is at the root level or boundary level

Hooks

Project Searcharrow-up-right

Project Updatearrow-up-right

MDMS Linkarrow-up-right

API Details

End Point
Action

/health-project/v1/_search?tenantId=mz&limit=10&offset=0

CAMPAIGN_MANAGER

/health-project/v1/_update

CAMPAIGN_MANAGER

/health-project/v1/_search?tenantId=mz&limit=10&offset=0

CAMPAIGN_MANAGER

/health-project/v1/_update

CAMPAIGN_MANAGER

boundary-service/boundary-hierarchy-definition/_search

CAMPAIGN_MANAGER

Sample Payload

Last updated

Was this helpful?