> For the complete documentation index, see [llms.txt](https://documentation.astera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.astera.com/astera-data-stack-v8/getting-started/ui-walkthrough-astera-8.0.md).

# UI Walkthrough - Astera 8.0

Astera is designed to support the integration of complex and high-volume data. It is a powerful ETL (Extract, Transform, Load) tool that provides connectivity to all leading databases, and flat and hierarchical file sources, and even supports legacy systems such as [COBOL](/astera-data-stack-v8/dataflows/sources/cobol-file-source.md). Moreover, [PDF Form Source](/astera-data-stack-v8/dataflows/sources/pdf-form-source.md), [Email Source](/astera-data-stack-v8/dataflows/sources/email-source.md), and [Report Source](/astera-data-stack-v8/dataflows/sources/report-source.md) enable users to extract data from a PDF file, Email, and Report Models in Astera.

It combines data profiling, data transformation, and data reporting in a single seamless user interface.

This document consists of a video that will walk you through the new and improved user interface of Astera and introduce you to its different features, components, and windowpanes.

{% embed url="<https://youtu.be/zFaaG-iEQqg>" %}

The video covers:

* Items, options, and shortcuts available on the menu bar
* How to access important windowpanes and panels in Astera – *Server Explorer, Project Explorer, Toolbox*, etc.
* How to work with different flow documents (dataflows, workflows, and subflows) with their embedded features
* Tools and tasks specific to each of the flow documents (transformations, workflow tasks, subflow input/output, etc.)
* Options related to data profiling and data quality checks
* How to schedule a job and monitor it’s progress
* Report Model and it’s functionality in Astera


---

# 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://documentation.astera.com/astera-data-stack-v8/getting-started/ui-walkthrough-astera-8.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.