> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/whats-new/december-2024/simplified-tga-report-creation.md).

# Simplified TGA Report Creation

<figure><img src="https://3871776571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTqMveDrJ1pB6OErwHvF0%2Fuploads%2FYqHT8rbue8vDXATUMFUr%2FScreenshot%202024-12-16%20at%2014.32.10.png?alt=media&amp;token=e5c5a36c-2f02-4b49-a6e4-7c0ca7cbf945" alt="" width="563"><figcaption><p>The New Basic Option to Create a TGA Report</p></figcaption></figure>

SeaLights is excited to introduce a more flexible and efficient approach to creating TGA reports.

### Key Improvement:

* **Simplified Quick Report Creation:** A new streamlined option allows you to create TGA reports by selecting only the app and branch. The system automatically selects all builds within the branch (up to the creation time), making the process faster and more efficient.
* **Enhanced Advanced Report Creation:** The advanced report creation option remains available for users who require more granular control over their reports. It now offers also the options to select all build within the selected branch, simplifying the report creation process.

<figure><img src="https://3871776571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTqMveDrJ1pB6OErwHvF0%2Fuploads%2F3Av4IqQ9Yu4T3oF1KHxe%2FScreenshot%202024-12-16%20at%2014.33.37.png?alt=media&amp;token=03bdb66a-4b76-40d8-b6c3-97882ca5852b" alt="" width="563"><figcaption><p>A third oprion for Buils Selection - All Builds</p></figcaption></figure>

* **Customizable Default Report Creation:** You can now choose the default report creation option (basic or advanced) for your organization, tailoring the experience to your specific needs.

### **Additional Features**

* **Automatic Baseline Selection:** When creating a report for a branched branch, the system automatically selects the appropriate baseline build, ensuring accurate analysis.
* **Easy Report Regeneration:** Regenerating a report with the "all builds in branch" option is now simpler, ensuring that the latest data is always included.

<figure><img src="https://3871776571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTqMveDrJ1pB6OErwHvF0%2Fuploads%2FIqBt15dvaDEXMuMkgFbf%2FScreenshot%202024-12-16%20at%2014.35.20.png?alt=media&amp;token=f22f5b50-dd44-4c35-bf02-4ebd0847ab06" alt="" width="563"><figcaption><p>Regenerating report including all builds</p></figcaption></figure>

By providing these enhanced features, SeaLights empowers you to gain valuable insights into your codebase more quickly and easily.


---

# 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://docs.sealights.io/knowledgebase/whats-new/december-2024/simplified-tga-report-creation.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.
