> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/health/v1.5/introducing-health/release-notes/hcm-v1.4-release-notes.md).

# HCM v1.4 Release Notes

## Release Summary

HCM v1.4 is a tech release with only server upgrade to [DIGIT 2.9 LTS](https://core.digit.org/platform/releases/digit-2.9-lts) with some additional cleanup. 

### Features:

* Digit core LTS integration
  * MDMS v2 integration 
  * Boundary V2 integration
* HCM Admin Console
* DIGIT HCM app modules as package extractions

## Functional Changes

* Missing unique validation on client reference ID added in all offline supported services.
* Project types have been moved to project additional details from MDMS.

## Non-Functional Changes

* UI modules extracted as packages
  * Registration and delivery
  * Referral reconciliation
  * Inventory management
  * Attendance management
  * DIGIT scanner
  * DIGIT showcase
* All core services have been upgraded to core 2.9 LTS barring the services modified for offline use cases.
* All data models have been restructured with an **"is a relationship"** from base eGov model and the base eGov search model.
* All data models have been moved to the health common library and duplicates removed.
* Removed reflection until code in the health common library that is Incompatible with Java 9 and above.

## **Breaking Changes**

* All the master data for the DIGIT HCM app are separated by functionality from one single master.
* Flyway version upgrade to 9.22.3  for LTS upgrade.
* Boundary v2 Integration


---

# 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.digit.org/health/v1.5/introducing-health/release-notes/hcm-v1.4-release-notes.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.