> For the complete documentation index, see [llms.txt](https://docs.mastersoftgroup.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mastersoftgroup.com/harmony-suite/release-notes/version-4.0.0/enhancements.md). # Enhancements ## G-NAF Enhanced Postcode Allocation Enhanced locality‑level postcode allocation in G‑NAF to ensure it more accurately reflects and respects the raw postcode values present in the source dataset. ## CNARGeocode GROUP Matching – Accented vs. De‑accented Input Matching logic has been updated to ensure **accent‑insensitive processing**, allowing GROUP matches to be returned regardless of whether the input is accented or de‑accented. ## Addition of `rdNumber` to CUSTOM Response The `rdNumber` field is now included in the CUSTOM response payload, ensuring attribute parity with CNAR and enabling consumers to access this value directly. ## CNAR PDPChangedItem Scope – Missing Postcode & Standardisation Changes The PDPChangedItem scope for CNAR has been updated to correctly capture and report **postcode updates** and **all relevant standardisation changes**, ensuring full visibility of field-level modifications. ## **Security Enhancements** A series of security vulnerabilities identified through assessments have been addressed in this release. These fixes improve system resilience, mitigate potential attack vectors, and ensure compliance with the latest security requirements. ## Decommissioned Modules As part of ongoing platform optimisation, several legacy modules have been **decommissioned** in this release. These components were phased in this version to streamline the product architecture and support a more modern, maintainable codebase. * HRA (Harmony Rapid Address) SOAP Web Service * HarmonyWS Old Style 1 Web Service * ODS Reporting * EnvinsaGeocode * ROAD browser * NADIS Post PDP * NZNRA PDP --- # 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.mastersoftgroup.com/harmony-suite/release-notes/version-4.0.0/enhancements.md?ask=&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.