> 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/novaseq-x-series/novaseqx/novaseqx-v1.2.0.md).

# NovaSeq X Series v1.2.0

The integration includes the following features:

* Preconfigured NovaSeq X Series Sequencing v1.1 workflow that maps to lab protocols and instrument runs.
* The following steps in the NovaSeq X Series Sequencing v1.1 preconfigured protocol:
  * Assign Analysis Configuration Template (NovaSeq X Series Sequencing v1.1)
  * Make Bulk Pool (NovaSeq X Series Sequencing v1.1)
  * Dilute and Denature (NovaSeq X Series Sequencing v1.1)
  * Load to Library Tube Strip (NovaSeq X Series Sequencing v1.1)
  * AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.1)
  * AUTOMATED - Analysis Run (NovaSeq X Series Sequencing v1.1)
* Automatic validation of run setup information before sample sheet generation or planned run creation.
* Automated generation of the sample sheet. This sample sheet is used to start the sequencing run on the NovaSeq X Series Control Software through Local run mode.
* Automated creation of a planned run on Illumina Connected Analytics (ICA). The NovaSeq X Series Control Software retrieves the planned run for use with the Cloud run mode.
* Automated tracking of the NovaSeq X Series sequencing run and parsing of run statistics from BaseSpace Sequence Hub to Clarity LIMS.
* Automated tracking of the NovaSeq X Series analysis run and high level analysis summary from BaseSpace Sequence Hub to Clarity LIMS.
* Support for configuration of multiple secondary analyses with multiple library prep kits (LPKs) and index adapter kits (IAKs) for the planned run. The analysis is either performed by ICA in Cloud mode or by DRAGEN on-board the instrument in Local mode.
* \[Optional] Preconfigured Library Prep Validation v2.3.2 workflow used for validation purposes only. The workflow contains a single-step protocol that models the library prep required to produce libraries that are ready for the NovaSeq X Series Sequencing v1.1 workflow. For more information, refer to [NovaSeq X Series Integration v1.2.0 User Interaction, Validation and Troubleshooting](/clarity-lims/instruments-and-integrations/novaseq-x-series/novaseqx/novaseqx-v1.2.0/novaseqx-v1.2.0-user-interaction-validation-and-troubleshooting.md).
* \[Optional] Clarity LIMS Product Analytics (CLPA) integration that can be used with ICA. The CLPA integration installation and configuration is required. For more information, refer to [Clarity LIMS Product Analytics Integration v1.2.0 Configuration](/clarity-lims/instruments-and-integrations/upa/clarity-lims-product-analytics-v1.2.0/upa-v1.2.0-configuration.md).


---

# 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/novaseq-x-series/novaseqx/novaseqx-v1.2.0.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.