> For the complete documentation index, see [llms.txt](https://help.claritylims.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.claritylims.illumina.com/instruments-and-integrations/upa/clarity-lims-product-analytics-v1.3.1/upa-v1.3.1-release-notes.md).

# Release Notes

Release Date: July 2024

These release notes describe the key changes to software components for the Clarity LIMS Product Analytics Integration v1.3.1.

## Compatibility

Refer to [Compatibility](/instruments-and-integrations/compatibility.md#upa) under Instruments & Integrations.

## New Features

1. The `novaseqxseries_associate_seqrun.groovy` and `nextseq1k2k_associate_seqrun.groovy` scripts can now associate libraries to sequencing run when any sample in the pool(s) has been assigned QC flags prior to entering the AUTOMATED - Sequencing Run step in the workflow.

## Security Vulnerability & Bug Fixes

1. The `pooling.groovy` script no longer fails when any samples in the pool(s) has been assigned QC flags prior to entering pooling steps in the workflow.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.claritylims.illumina.com/instruments-and-integrations/upa/clarity-lims-product-analytics-v1.3.1/upa-v1.3.1-release-notes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.