> 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/nextseq1k2k-v2.0.0-release-notes.md).

# NextSeq 1000/2000 v2.0.0

The following release notes detail the key changes to software components for the Clarity LIMS NextSeq 1000/2000 Integration package v2.0.

## Compatibility

* Clarity LIMS Hosted v5.3 through 5.4
* NGS Extensions Package v5.20 or later
* Illumina Preset Protocol (IPP) v2.1.0 or later
* NextSeq 1000/2000 Instrument Control Software v1.1
* DRAGEN v3.5.8

## New Features

This release of the Clarity LIMS integration package:

* Supports the security improvements made to the management of passwords in Clarity LIMS v5.4.
* Decouples the SIS CORE from the integration package extension. Each is available for download independently.
* References ICA instead of IAP.
* Supports AWS SDK 2.6.15 to mitigate the risk of its dependency to Jackson-databind.jar.

## Known Issues

* None

## Limitations

For the demultiplexing information in the Sample Details table to display correctly, the following conditions must be met:

* The DRAGEN version must be earlier than v3.9.3.
* The samples in the run must not repeat.
* The run must be for the single lane flow cell (P1 or P2).


---

# 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/nextseq1k2k-v2.0.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.