> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pba/pipeline-designer/working-with-transformations.md).

# Working with transformations

Create, configure, and then run transformations to perform ETL tasks as part of specified workflow. After running a transformation, analyze its results to explore the data or to identify possible improvements or problems.

**Note:** You can schedule a transformation to run a single time or on a recurring schedule. For details, see&#x20;

* [Create a transformation](https://docs.pentaho.com/pba/pipeline-designer/working-with-transformations/create-a-transformation.md)

  Create a transformation to arrange a network of logical ETL tasks, called steps, into a data workflow.
* [Edit transformation properties](https://docs.pentaho.com/pba/pipeline-designer/working-with-transformations/edit-transformation-properties.md)

  Transformation properties describe the transformation and configure its behavior. You can use transformation properties to customize the processing of your data to achieve the desired output.
* [Run a transformation](https://docs.pentaho.com/pba/pipeline-designer/working-with-transformations/run-a-transformation.md)

  Run a transformation to step through the ETL tasks you set up, in the order specified by the transformation.
* [Analyze transformation results](https://docs.pentaho.com/pba/pipeline-designer/working-with-transformations/analyze-transformation-results.md)

  You can see if errors occurred, explore the data, and review how your transformation performed, by viewing logs, previewing data, and reviewing step metrics.
* [Transformation steps in Pipeline Designer](https://docs.pentaho.com/pba/pipeline-designer/working-with-transformations/transformation-steps-in-pipeline-designer.md)

  Steps extend and expand the functionality of transformations. You can use the following steps in Pipeline Designer.


---

# 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.pentaho.com/pba/pipeline-designer/working-with-transformations.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.
