> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/clarity-lims/instruments-and-integrations/other-release-notes/ipp-v2.5.0-release-notes.md).

# IPP v2.5.0

Release Date: July 2023

These Release Notes describe the key changes to the Illumina Preset Protocols (IPP) from version 2.4.

## Compatibility

* Clarity LIMS v5.1 and later
* NGS Extensions Package v5.22 and later

## New Features

* Supports the new NovaSeq X Series v1.0 workflow.
* Updates the Validate Flowcell Barcode automation in the Load to Flowcell step of the NovaSeq Xp protocol. This update supports the future flow cell barcode format for the following workflows:
  * IGA v2.x
  * COVIDSeq
  * NovaSeq 6000
  * NovaSeq 6000Dx
* Updates the iLASS TruSight Whole Genome workflow to remove the Volume (µl) global custom field and the preset values of Target Queue Step Name and Target Queue Workflow Name.

## Defects Fixed

* Corrected the label groups in the TruSight Oncology 500 ctDNA workflow.

## Known Issues

* The Validate Flowcell Barcode automation (in the Load to Flowcell step of the NovaSeq Xp protocol in the COVIDSeq workflow) accepts lowercase alphanumeric characters in the first five positions of the barcode. The automation should only accept uppercase alphanumeric characters.


---

# 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://help.bioinsight.illumina.com/clarity-lims/instruments-and-integrations/other-release-notes/ipp-v2.5.0-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.