# 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: 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:

```
GET https://help.claritylims.illumina.com/instruments-and-integrations/miseq/miseq-v8.2.0/miseq-v8.2.0-manual-upgrade.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.