Release Notes
Release notes for Complaints Management v2.11
Release Date - April 17, 2026
Release Summary
Complaints Management v2.11 introduces a new way to send notifications, including full two-way communication via WhatsApp. It also makes it easier to set up and get started. This version adds new system features, improves platform deployment, and fixes important issues in the interface, language support, and workflows.
At a glance
Upgrade path: v2.10 to v2.11
New services: Config Service, User Preferences Service, Novu Bridge Service
Major feature: provider-agnostic notifications with WhatsApp support
What you need to do
Read the Migration Guide before upgrading.
Check exact image tags in Service Build Updates.
Review the WhatsApp Setup Guide if you plan to enable messaging.
Highlights
Provider-agnostic notification engine
Full bidirectional WhatsApp integration
New configuration and user preference services
Faster local setup with Docker Compose, Kind, and Tilt
Broad UI, workflow, localisation, and deployment improvements
New Services
Config Service
Stores notification provider configuration and template bindings.
Supports MDMS v2 schema validation and secure credential handling.
Learn more in Config Service.
User Preferences Service
Stores per-user notification preferences.
Supports WhatsApp opt-in and opt-out flows.
Learn more in the User Preferences Service.
Novu Bridge Service
Resolves templates across providers without code changes.
Adds bidirectional WhatsApp support with locale-aware templates.
Learn more in Novu Bridge Service.
New Features
For platform teams
Added provider priority support for Twilio, ValueFirst, and Novu.
Added separate SMS and WhatsApp config resolution flows.
Enriched complaint domain events with assignee and reference metadata.
For implementers
Added one-command local setup with Docker Compose.
Added Kind and Tilt support for live-reload development.
Improved onboarding with a unified DataLoader workflow.
For product and UI teams
Added OpenStreetMap support with switchable map provider configuration.
Added configurable boundary hierarchy rendering in the UI.
Improved complaint search, validation, photo upload, and citizen detail rendering.
Changed
Platform and configuration
Service requests now use the department name instead of the department code.
MDMS v2 endpoints are now the default across the stack.
Boundary role actions were updated for
MDMS_ADMINandHRMS_ADMIN.Added mobile prefix handling and cleaner endpoint whitelists.
Localisation and onboarding
Localisation upserts are now idempotent.
Boundary and complaint-type loads now generate localisation data automatically.
Employee templates now pull dynamic values from MDMS.
Loaders now fail fast on authentication errors.
CI and delivery
Added Postman collection tests to CI.
Added telemetry verification across compose files.
Added readiness checks before smoke tests.
Added multi-arch Docker build support.
Fixed
HRMS template syntax and RequestInfo model compatibility issues.
Tenant bootstrap and tenant ID configuration issues.
Localisation memory issues during boundary template generation.
Inbox, workflow, and complaint creation bugs in Complaints.
Boundary validation and citizen detail rendering issues in the UI.
Preferred language resolution issues.
Known issues
Hindi localisations are not available on some Citizen and Employee page labels. If a localisation key still contains a dot (.), replace it with an underscore (_).
Related Docs
Last updated
Was this helpful?