> 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/2016/4.12.0.md).

# 4.12.0

### October 4, 2016 - 4.12.0 - Usage Tracking

* Added application usage cost (iCredits/Node hour) in the application launch page.
* Added display of total current monthly storage, compute and application usage in iCredits per account, workgroup or domain.
* Professional and Enterprise Users now have the ability to specify under which Workgroup an application can be run.
* Display a banner warning when Basic Account users are within 90% of their limit and a Restriction Alert when a limit is met or exceeded.
* Provides Prep Tab support for TruSeq Methyl Capture EPIC kit.
* Added ability to copy data from the Runs and Projects table views.
* Upgraded FASTQ Generation for HIPAA compatibility. It still uses bcl2fastq v2.17 and produces the same results, but runs up to 25% faster. Some debug log files are no longer produced.
* Performance improvements.
* Bug 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 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/2016/4.12.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.