> 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/2020/5.45.0.md).

# 5.45.0

### May 19, 2020 - 5.45 - Files & Kits Settings Pages

### Features

* Added Files & Kits menu to the Settings page, where the following run setup resources can be viewed or added:
  * Library prep kits
  * Index adapter kits
  * Reference genomes
* When running a NextSeq 2000 in Local Analysis mode, uploaded analysis results are stored in a project. If a project does not exist, a new project is created.
* Improvements to Run Setup:
  * Added support for large file upload.
  * Added confirmation prompt when switching Analysis Type or Analysis Location.
  * Added display of additional details when a reference genome is selected.

### Bug Fixes

* Fixed an issue that caused the My Data and Run Planning navbar links to briefly duplicate on page load.
* Fixed an issue with multi-node appsessions where the report did not display until the page refreshed.
* Fixed an issue with the dataset matcher that prevented tooltips from displaying.
* Fixed an issue that created duplicate planned runs if Submit was selected more than once in the Run Setup tool.
* Fixed an issue where editing a planned run with unspecified kits did not have the correct columns in sample data table.
* Fixed a bug where using an unacceptable character (".") was not prevented during run setup.
* Fixed an issue where a 'required field' error message could appear erroneously during run setup.
* Fixed a rare issue that could prevent app launches.
* Security fixes.

### Release 5.45.1 - May 28, 2020

* Features
  * None.
* Bug Fixes
  * Performance and stability fixes.


---

# 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/2020/5.45.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.
