# New Features

## Address Linkage Component for Unified Reference Data (NZ Locale)

This release introduces a new [component ](/harmony-suite/user-guides/version-3.2.0/address-link-table-integration-guide.md)designed to unify address reference data across multiple sources by establishing a single source of truth. A batch tool is provided to build a link table that consolidates address records, which is then used by the HRA address lookup to return unified results.
\
If a match is not found in the link table during lookup, the system performs an online linkage and updates the link table accordingly. This feature is initially rolled out for the New Zealand (NZ) locale, with potential expansion to other regions in future releases.

## **Character Transliteration Support for Address Cleansing and Lookup**

This release adds support for character transliteration, enabling normalization of accented and special characters—such as macron characters (e.g. Āā, Ēē, Īī, Ōō, Ūū)—into their base ASCII equivalents. This functionality enhances consistency and improves match accuracy across address data.

Transliteration is available in two key areas:

* **Address Cleansing** via the `AddressTransliteration` PDP (requires appropriate licensing and configuration in the pdp chain for cleanse).
* **Address Lookup** in HRA, when the [`transliteration`](/harmony-suite/user-guides/version-3.2.0/address-link-table-integration-guide/address-lookup-using-link-table.md) option is set to `1`.

This feature ensures broader character compatibility and improved integration with systems that do not support extended character sets.


---

# Agent Instructions: 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:

```
GET https://docs.mastersoftgroup.com/harmony-suite/release-notes/version-3.2.0/new-features.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.