> For the complete documentation index, see [llms.txt](https://help.connected.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.connected.illumina.com/basespace/releases/previous-releases/2022/7.4.0.md).

# 7.4.0 - Run Planning Enhancements

#### September 21, 2022

#### Features

* Run Planning:
  * Renamed "Instrument Run Setup" to "Run Planning" in the New Run dropdown menu.
  * Run planning now consists of three stages: run settings, analysis configurations, and run review.
  * Added a "Save as Draft" option when planning a run. Draft runs are available through Sequence Hub but not on instruments. Once a draft is saved as Planned, it is available on supported instruments.
  * Improved the ability to import samples from a CSV file. A template CSV is provided for download, and v2 Sample Sheets can still be used to import samples.
  * Added multi-selection support for the Lane column in the Sample table.
  * Added new optional fields under run settings: Run Description and Library Tube ID.
  * Note that there is no change to saved data. Planned runs created using the previous version can still be viewed in Run Planning.
* Removed product filter from Beadchip selection table in the Microarray Analysis Setup tool

#### Bugs Fixed

* Improved error messages when launching an app with the API or CLI and no valid FASTQ files are found.
* Improved performance when retrieving biosamples in preptab.
* Fixed an issue that could cause the email notification checkboxes in Settings to be unchecked even when turned on.


---

# 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.connected.illumina.com/basespace/releases/previous-releases/2022/7.4.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.