FEATURE/HCMPRE-1625 last modified date added in campaign search and checklist search screens

[suryansh-egov]

Choose the appropriate template for your PR:

Feature PR

Feature Request

JIRA ID

Module

Description

Related Issues

---

Bugfix PR

Bugfix Request

JIRA ID

Module

Description

Root Cause

Related Issues

---

Release PR

Summary by CodeRabbit

• New Features

  • Added "CHECKLIST_LAST_UPDATE" column to search results, enhancing visibility of checklist updates.
  • Introduced "CAMPAIGN_LAST_UPDATE" field across various campaign configurations, improving tracking of campaign updates.
  • Updated search result configurations for campaign types to reflect last update times instead of beneficiary types.

• Bug Fixes

  • Improved error handling in campaign retry functionality.

• Chores

  • Minor adjustments made to search parameters and state management for better responsiveness.

[coderabbitai]

📝 Walkthrough

📝 Walkthrough

Walkthrough

The pull request introduces enhancements to the campaign management system's user interface configurations. The changes primarily focus on adding new columns for tracking last update times in various campaign and checklist configurations. Specifically, new cases are added to handle "CHECKLIST_LAST_UPDATE" and "CAMPAIGN_LAST_UPDATE" across different configuration files. These modifications improve the visibility of modification timestamps for campaigns and checklists, utilizing the Digit.DateUtils.ConvertEpochToDate function to transform epoch timestamps into readable date formats.

Changes

File	Change Summary
health/micro-ui/web/micro-ui-internals/packages/modules/campaign-manager/src/configs/UICustomizations.js	Added new cases for "CHECKLIST_LAST_UPDATE" and "CAMPAIGN_LAST_UPDATE" in additionalCustomizations methods for multiple configurations.
health/micro-ui/web/micro-ui-internals/packages/modules/campaign-manager/src/configs/checklistSearchConfig.js	Added new column for "CHECKLIST_LAST_UPDATE" with additionalCustomization: true in the search result configuration.
health/micro-ui/web/micro-ui-internals/packages/modules/campaign-manager/src/configs/myCampaignConfig.js	Replaced "CAMPAIGN_BENEFICIARY_TYPE" with "CAMPAIGN_LAST_UPDATE" across various campaign configurations and added LAST_MODIFIED_TIME in drafts.

Possibly related PRs

• Facility data fix #1829: Modifies the UICustomizations object, enhancing the handling of additional customizations.
• Hcmpre 1290 #1834: Updates the myCampaignConfig object, specifically adding a new field for CAMPAIGN_LAST_UPDATE.
• added back button, redirected checklist success and fixed null issue … #1894: Introduces changes to the CreateChecklist component, related to campaign management.
• added campaign name in update #1973: Updates the SetupCampaign component to include the campaignName in the URL for navigation.

Suggested reviewers

• nipunarora-eGov

Poem

🐰 Hop, hop, through configs we go,
Timestamps dancing, row by row!
Last updates shine so bright and clear,
Campaign magic spreading cheer!
A rabbit's tale of UI delight 🕒✨

Tip

CodeRabbit's docstrings feature is now available as part of our Early Access Program! Simply use the command @coderabbitai generate docstrings to have CodeRabbit automatically generate docstrings for your pull request. We would love to hear your feedback on Discord.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 3

📜 Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ce3222f and cb279a7.

📒 Files selected for processing (1)

• health/micro-ui/web/micro-ui-internals/packages/modules/campaign-manager/src/configs/UICustomizations.js (6 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

health/micro-ui/web/micro-ui-internals/packages/modules/campaign-manager/src/configs/UICustomizations.js (1)

Pattern **/*.js: check

🪛 Biome (1.9.4)

health/micro-ui/web/micro-ui-internals/packages/modules/campaign-manager/src/configs/UICustomizations.js

[error] 122-122: Other switch clauses can erroneously access this declaration.
Wrap the declaration in a block to restrict its access to the switch clause.

The declaration is defined in this switch clause:

Unsafe fix: Wrap the declaration in a block.

(lint/correctness/noSwitchDeclarations)