> 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.

## Deprecated Modules

As part of ongoing platform optimisation, several legacy modules have been **deprecated** in this release. These components were phased in this version to streamline the product architecture and support a more modern, maintainable codebase.


---

# 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.mastersoftgroup.com/harmony-suite/release-notes/version-4.0.0/enhancements.md?ask=<question>&goal=<endgoal>
```

`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.