> For the complete documentation index, see [llms.txt](https://docs.mosip.io/1.2.0/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mosip.io/1.2.0/roadmap-and-releases/releases/1.2.0.2-reg-processor-and-id-repo.md).

# 1.2.0.2 - Reg Processor & ID Repo

**Release Version:** 1.2.0.2(Reg Processor & ID Repo)

**Release Date:** 8th January, 2025

### **Overview**

This release launches an enhancement in the Registration Processor to support the [Custom Handle](https://docs.mosip.io/1.2.0/modules/id-repository/custom-handle) feature to be enabled during the new registration process using the Android Registration Client. As part of this release, changes were made in the packet manager, ID repo & registration processor to process packets that contain demographic fields with datatype as an array.

### **Major Highlights**

* Registration
* Packet Manager
* ID Repository

### **New Features**

* **Supporting Array DataType in packet processing** :\
  With the custom handle feature enabled, the handle attribute is passed as an array datatype in the packet during packet creation. This change has modified the registration processor and packet manager to handle both string and array values.

### **Bug Fixes**

* **Unable to authenticate using handles:**\
  Fix was provided through this release by introducing a new endpoint in ID Repository which will retrieve the identity based on handle and idtype.

### **Repository Released**

| Repositories            | Tag version                                                       |
| ----------------------- | ----------------------------------------------------------------- |
| mosip-config            | [v1.2.3.0](https://github.com/mosip/mosip-config/tree/v1.2.3.0)   |
| id-repository           | [v1.2.2.0](https://github.com/mosip/id-repository/tree/v1.2.2.0)  |
| packet-manager          | [v1.2.0.2](https://github.com/mosip/packet-manager/tree/v1.2.0.2) |
| registration            | [v1.2.0.2](https://github.com/mosip/registration/tree/v1.2.0.2)   |
| bio-utils/biometric-api | [v1.2.0.3](https://github.com/mosip/bio-utils/tree/v1.2.0.3)      |

### **Compatible Modules**

The following table outlines the tested and certified compatibility of [1.2.0.1](https://github.com/mosip/documentation/blob/1.2.0/docs/roadmap-and-releases/releases/release-notes-1.2.0.1) with other modules.

| Module   | Version     |
| -------- | ----------- |
| Platform | v1.2.0.1 B3 |

### Documentation

* [Functional test report](https://docs.mosip.io/1.2.0/releases/1.2.0.2-reg-processor-and-id-repo/test-report)
* [Known Issues](https://mosip.atlassian.net/issues/?jql=labels%20%3D%20%22known-issue-1.2.0.2%22)


---

# 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.mosip.io/1.2.0/roadmap-and-releases/releases/1.2.0.2-reg-processor-and-id-repo.md?ask=<question>&goal=<user_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.