> 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/emedgene/release-notes/change_log/change_log_workbench_30.md).

# Change log workbench 30

## **Features:**

* Feature | ACMG SNV | Add note
* Feature | Add report service activity in dashboard
* Feature | Add template name change activity in dashboard
* Feature | Add template upload activity in dashboard
* Feature | Import Gene Interpretation from Curate
* Feature | Enable kit management in organization settings
* Feature | New Phenomeld filter added
* Feature | Presets | Gene list | Search for gene list name
* Feature | Var page | Add Genomenon linkout to clinical significance
* Feature | Display varcaller in varpage
* Feature | Varpage | Enrich related cases
* Feature | Gene list | add NCBI ID to genes in gene list in database
* Feature | Validation of variant retrieval. When system is degraded this will alert users not to work on cases with incomplete variant data.

## **Enhancement:**

* Enhancement | Visualization - add tracks order
* Enhancement | Visualization | Change default locus zoom for BigWig
* Enhancement | Add more ethnicities

## **Bug fixes:**

* Bug Fix | Display chr number for finalized cases in finalize tab
* Bug Fix | Add new case | Reactivate batch mode using HPO IDs


---

# 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/emedgene/release-notes/change_log/change_log_workbench_30.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.