> 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/2018/5.23.0.md).

# 5.23.0

### June 26, 2018 - 5.23 - Publishing Apps to your Enterprise and Faster SAV Downloads

* Features
  * Added the ability for Enterprise users to publish apps to their domain. Apps published in a domain through the Developer Portal will only show up for users in the domain.
  * The performance of SAV download of run InterOp files has been improved by only downloading aggregated files when available. When aggregated files are not available, per cycle files will downloaded.
* Bugs Fixed
  * Fixed an issue where a user could be prompted with the window to accept an app's EULA after accepting it already.
  * Fixed an issue with workflow analyses getting stuck in "Pending Execution".

### Release 5.23.1 - June 28, 2018

* Bugs Fixed
  * Fixed an issue displaying reports for multi-node apps.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.connected.illumina.com/basespace/releases/previous-releases/2018/5.23.0.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.