> 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/pdia-data-integration/10.2-data-integration/data-integration-perspective-in-the-pdi-client/work-with-transformations-cp/create-a-transformation.md).

# Create a transformation

Follow these instructions to create your transformation:

1. Perform one of the following actions:
   * Click **File** > **New** > **Transformation**.
   * Click the **New file** icon in the toolbar and select **Transformation**.
   * Hold down the CTRL N keys.
2. Go to the **Design** tab. Expand the folders or use the **Steps** field to search for a specific step.
3. Either drag or double-click a step to place it on the PDI client canvas.
4. Double-click the step in the PDI client canvas to open its properties window. For help with filling out the window, click the **Help** button that is available with each step.
5. To add another step, either drag or double-click the step in the **Design** tab to place it on the PDI client canvas.
   * If you drag the step to the canvas, you can add a hop by pressing the SHIFT key and drawing a hop from one step to the other.
   * If you double-click it, the step appears on the canvas with a hop already connected to your previous step.

After you have created a transformation, you must save the transformation before you can run it.


---

# 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/pdia-data-integration/10.2-data-integration/data-integration-perspective-in-the-pdi-client/work-with-transformations-cp/create-a-transformation.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.