> 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/miseq/miseq-v8.2.0/miseq-v8.2.0-manual-upgrade.md).

# Manual Upgrade

MiSeq Integration v8.2.0 includes the MiSeq v3.2 workflow upgrade. This upgrade is typically done through the API. To upgrade the workflow manually, create the Validate Single Input automation and update its trigger information as follows.

{% hint style="info" %}
Before updating the script, make sure the MiSeq v3.1 workflow is installed.
{% endhint %}

## Create Validate Single Input Automation

1. In Clarity LIMS, under Configuration, select the Automation tab.
2. Select **New Automation**.
3. Create an automation called Validate Single Input.
4. In the Command Line field, add the following string:

   <pre class="language-markup" data-overflow="wrap"><code class="lang-markup">bash -l -c "/opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/ngs-common/v5/EPP/ngs-extensions.jar -i {stepURI:v2} -u {username} -p {password} script:validateSampleCount -min 1 -max 1"
   </code></pre>
5. Under Automation Use, enable this automation on the Denature and Dilute master step.

## Change Trigger Point for the Validate Single Input Automation

1. In Clarity LIMS, under Configuration, select the Lab Work tab.
2. Find the Denature and Dilute step.
3. In the Automation section, update the Trigger Location and Trigger Style for the Validate Single Input automation as follows.
   * **Trigger Location** — Step
   * **Trigger Style** — Automatic upon entry


---

# 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/miseq/miseq-v8.2.0/miseq-v8.2.0-manual-upgrade.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.