> 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-v6/getting-started/introduction-to-astera-6-webinar-video.md).

# Introduction to Astera 6 Webinar Video

This webinar video demonstrates the key new features and functionalities within Astera 6.0. Below is the outline of topics and the times they appear in the video.

{% embed url="<https://youtu.be/ceQBcxrnQPw?list=UUAOSJmfWVS0XDADZoEHR_Ww>" %}

​ **OUTLINE AND TOPIC TIMELINE**

New Features for Complex Hierarchical Data Integration 2:36

* Scoped Transformations 3:16
* FLWOR 6:00
* Tree Join Transformations 7:20
* Lookup Enhancements 9:16
* Dynamic Lookup Cache 9:48
* Persistent Lookup Cache 12:12
* SQL lookup enhancements 13:55
* New Transformations 16:11
* ApplyToAll 17:16
* Expression List Transformation 19:20
* Text Processors 20:48
* REST Web Service 24:07
* Enhancements 25:51
* In-Database Joins 26:48
* New Data Types 28:59
  * Decimal 29:10
  * TimeSpan 29:51
* Source as Transformation 30:26
* Detached Transformations 32:56
* Runtime Enhancements 35:08
* Variables
  * Action 35:57
  * Dataflow 38:22
* Job Restart 40:45
* OR Action 42:41
* Lineage & Impact Analysis 44:06
* Enhancements to Astera Integration Server 46:32
* Unified Server Management 48:28
* Scalability
* High Availability
* Job Management
* Scheduler Blackout Time


---

# 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-v6/getting-started/introduction-to-astera-6-webinar-video.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.