# v1.2.2.0 DSL

**Release Name**: DSL Orchestrator & Packet Creator

**Release Version**: 1.2.2.0

**Release Type**: Minor Release

**Release Date**: 20th April, 2026

### Overview

We are pleased to announce **DSL Orchestrator & Packet Creator v1.2.2.0**, released to support environments running on **Java 11**.

This release contains functionality equivalent to [**v1.4.0 DSL**](/1.2.0/roadmap-and-releases/releases/v1.4.0-dsl.md), with the primary difference being **Java runtime compatibility**. While **v1.4.0 is built for Java 21**, **v1.2.2.0 is provided specifically for Java 11 environments** where upgrading Java versions is not yet feasible.

All DSL scenarios, reporting improvements, bug fixes, and enhancements available in [**v1.4.0 DSL**](/1.2.0/roadmap-and-releases/releases/v1.4.0-dsl.md) are also applicable to this release unless otherwise specified.

### Major Highlights

<table><thead><tr><th width="156.5859375">Key JIRA</th><th width="181.6015625">Feature</th><th>Summary</th></tr></thead><tbody><tr><td><a href="https://mosip.atlassian.net/browse/MOSIP-44268"><strong>MOSIP-44268</strong></a></td><td><strong>Biometric Update Scenario Stabilization</strong></td><td>Investigated and resolved failures occurring in <strong>Update Biometric scenarios within the DSL framework</strong>. Root causes were analysed and fixes were implemented to ensure stable and reliable execution of biometric update workflows.</td></tr></tbody></table>

{% hint style="info" %}
For detailed feature descriptions, enhancements, bug fixes, known issues, and scenario coverage, refer to the [**DSL v1.4.0 Release Notes**](https://mosip.atlassian.net/wiki/spaces/QT/pages/2507112467), As this release is aligned with DSL v1.4.0.
{% endhint %}

### **Known Issues**

<table><thead><tr><th width="194.82421875">Bug</th><th>Description</th></tr></thead><tbody><tr><td><a href="https://mosip.atlassian.net/browse/MOSIP-44548"><strong>MOSIP-44548</strong></a></td><td>In <strong>Scenario_229</strong>, a packet created with an <strong>invalid gender value</strong> should fail during <strong>VALIDATE_PACKET</strong>, but the system processes it successfully and RID status is shown as <strong>PROCESSED</strong>.</td></tr><tr><td><a href="https://mosip.atlassian.net/browse/MOSIP-41564"><strong>MOSIP-41564</strong></a></td><td>In <strong>Scenarios 145, 151, 156, 196, and 197</strong>, packets created with <strong>invalid or empty signatures</strong> fail at the <strong>UPLOAD_PACKET stage</strong> instead of the expected <strong>Packet Validation stage</strong>.</td></tr><tr><td><a href="https://mosip.atlassian.net/browse/MOSIP-44803"><strong>MOSIP-44803</strong></a></td><td>In <strong>Scenario_223</strong>, a packet created with an <strong>invalid packet type</strong> is expected to fail during the <strong>VALIDATE_PACKET stage</strong>, but in the <strong>QA11 environment</strong>, it fails earlier at the <strong>UPLOAD_PACKET stage</strong> instead.</td></tr><tr><td><a href="https://mosip.atlassian.net/browse/MOSIP-40705"><strong>MOSIP-40705</strong></a></td><td>In <strong>Scenarios 188 and 128</strong>, when a packet is created with <strong>both thumbs marked as exceptions</strong>, authentication using the <strong>little finger</strong> should succeed, but the authentication fails unexpectedly.</td></tr><tr><td><a href="https://mosip.atlassian.net/browse/MOSIP-39353"><strong>MOSIP-39353</strong></a></td><td>In <strong>Scenario_160</strong>, VID generation fails when <strong>phone</strong> is used as the <strong>OTP notification channel</strong>, causing the VID generation process to fail.</td></tr></tbody></table>

### **Compatibility**

| Modules                     | Version                                                                        |
| --------------------------- | ------------------------------------------------------------------------------ |
| id-authentication           | [v1.2.1.3](https://github.com/mosip/id-authentication/tree/v1.2.1.3)           |
| id-repository               | [v1.2.2.4](https://github.com/mosip/id-repository/tree/v1.2.2.4)               |
| admin-services              | [v1.2.1.4](https://github.com/mosip/admin-services/releases/tag/v1.2.1.4)      |
| resident-services           | [v1.2.1.3](https://github.com/mosip/resident-services/tree/v1.2.1.3)           |
| partner-management-services | [v1.2.2.2](https://github.com/mosip/partner-management-services/tree/v1.2.2.2) |
| pre-registration            | [v1.2.0.3](https://github.com/mosip/pre-registration/tree/v1.2.0.3)            |

### **Repositories Released**

| Repository                 | Version                                                                   |
| -------------------------- | ------------------------------------------------------------------------- |
| **mosip-automation-tests** | [v1.2.2.0](https://github.com/mosip/mosip-automation-tests/tree/v1.2.2.0) |

### **Documentation**

**Build & Setup:** [mosip-automation-tests/README.md at release-1.2.2.x · mosip/mosip-automation-tests](https://github.com/mosip/mosip-automation-tests/blob/release-1.2.2.x/README.md)


---

# 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.mosip.io/1.2.0/roadmap-and-releases/releases/v1.2.2.0-dsl.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.