> 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/basespace/releases/previous-releases/2024/7.21.0.md).

# 7.21.0 - Improved Look and Feel

#### April 16, 2024

#### Features

* Improved look and feel on the dashboard, runs spotlight section, navbar, and toolbar menus.
* Updated the toolbar icons.
* Added the option to switch to the correct Workgroup when following a Project or Analysis link.
* Added the application category "Infectious Disease + Microbiology".
* Added an analysis description in Microarray Analysis Setup that displays after selecting an analysis.
* Updated the dropdown lists in Microarray Analysis Setup to sort alphabetically.

#### Bugs Fixed

* Fixed an issue that could prevent Run size from updating during upload.
* Fixed an incorrect validation for the Override Cycles field in Run Planning that prevents user from setting up a run with Index1 as UMI and Index2 for demultiplexing.
* Fixed an issue in Run Planning that occurred when importing a NextSeq1000/2000 planned run from a sample sheet that does not contain an OverrideCycles value.
* Fixed an issue in Microarray Analysis Setup where a "Failed to import idats" message remained after re-importing valid files.
* Fixed an issue in Microarray Analysis Setup where uploading an invalid Product Descriptor file would cause the Add Custom Configuration modal to hang.


---

# 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/basespace/releases/previous-releases/2024/7.21.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.
