> 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/complaints-management/digit-complaints-management/release-notes.md). # Release Notes {% hint style="info" %} **Release Date - April 17, 2026** {% endhint %} ## 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](/complaints-management/digit-complaints-management/release-notes/migration-guide.md) before upgrading. * Check exact image tags in [Service Build Updates](/complaints-management/digit-complaints-management/release-notes/mdms-configuration-and-service-build-updates.md). * Review the [WhatsApp Setup Guide](/complaints-management/deploy/configure/whatsapp-setup-guide.md) 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](/complaints-management/design/architecture/services/config-service.md). #### User Preferences Service * Stores per-user notification preferences. * Supports WhatsApp opt-in and opt-out flows. * Learn more in the [User Preferences Service](/complaints-management/design/architecture/services/user-preferences-service.md). #### Novu Bridge Service * Resolves templates across providers without code changes. * Adds bidirectional WhatsApp support with locale-aware templates. * Learn more in [Novu Bridge Service](/complaints-management/design/architecture/services/novu-bridge-service.md). ## 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_ADMIN` and `HRMS_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 {% hint style="warning" %} 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 (`_`). {% endhint %} ## Related Docs * [Migration Guide](/complaints-management/digit-complaints-management/release-notes/migration-guide.md) * [Service Build Updates](/complaints-management/digit-complaints-management/release-notes/mdms-configuration-and-service-build-updates.md) * [Configure Complaints Data Loader](/complaints-management/deploy/setup/production-setup/deploy-complaints-management/configure-cms-data-loader.md) * [WhatsApp Setup Guide](/complaints-management/deploy/configure/whatsapp-setup-guide.md) * [Local Setup CMS Service](/complaints-management/deploy/customise/backend/local-setup/local-setup-cms-service.md) * [Config Service](/complaints-management/design/architecture/services/config-service.md) * [Novu Bridge Service](/complaints-management/design/architecture/services/novu-bridge-service.md) --- # 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/complaints-management/digit-complaints-management/release-notes.md?ask=&goal= ``` `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.