> 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.5.0/upa-v1.5.0-release-notes.md).

# Release Notes

Release Date: November 2025

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

## Compatibility

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

## New Features

1. `step_start.groovy` now includes the name of technician that started the step.
2. `step_completed.groovy` now sends these additional information:
   * Name of technician completing the step
   * Reagent lot associated with the step (if any)
   * Instrument associated with the step (if any)
   * Step custom field (if configured)
   * Input artifact custom field (if configured)
   * Output artifact custom field (if configured)
3. Added new optional properties to support the sending of custom field data:
   * `integration.upa.v1.includeStepFields`
   * `integration.upa.v1.excludeStepFields`
   * `integration.upa.v1.includeArtifactFields`
   * `integration.upa.v1.excludeArtifactFields`

## Updates

1. Improved handling of empty UDF values.
2. Updated `configure_upa.sh` script.

## Security Vulnerability & Bug Fixes

1. Fixed payload generation issue for NextSeq 1000/2000 Sequencing workflow due to automation triggered before step fields are populated.
2. Fixed configuration issue when switching CLPA from workgroup to personal account.


---

# 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.5.0/upa-v1.5.0-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.