> For the complete documentation index, see [llms.txt](https://academy.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.pentaho.com/pdi-developer-path-sandbox/speciality-courses/pipeline-designer.md).

# Pipeline Designer

Coming soon — build pipelines in Pentaho 11's browser-based Pipeline Designer, alongside the PDI desktop client.

{% hint style="warning" icon="eye" %}
**SANDBOX — draft page.** **🚧 In development — coming soon.** Pipeline Designer is Pentaho 11's browser-based pipeline designer. This Speciality is still being written: the outline below is a draft, and items marked REPLACE-ME need an owner's confirmation.
{% endhint %}

Pipeline Designer is a web-based interface for designing, running and managing data integration workflows directly in your browser. It is a server-side plugin installed by default with Pentaho Server, and updated through the Plugin Manager. Build transformations and jobs visually in the Design view, or review and edit the raw XML in the XML view, then run them and analyse the results.

The concepts carry straight over from the desktop client — nodes, hops, transformations and jobs are the same ideas you already know from Spoon — so this Speciality is about the interface rather than the fundamentals.

{% columns %}
{% column %}

<p align="center"><i class="fa-file-lines" style="color:green;">:file-lines:</i><br><strong>REPLACE-ME lessons</strong><br><em>3 in the draft outline</em></p>
{% endcolumn %}

{% column %}

<p align="center"><i class="fa-flask" style="color:orange;">:flask:</i><br><strong>REPLACE-ME workshops</strong><br><em>1 in the draft outline</em></p>
{% endcolumn %}

{% column %}

<p align="center"><i class="fa-clock" style="color:cyan;">:clock:</i><br><strong>REPLACE-ME</strong><br><em>time to be confirmed</em></p>
{% endcolumn %}
{% endcolumns %}

{% hint style="success" icon="cloud-arrow-up" %}
Every workshop is hands-on and runs on Pentaho's hosting platform. The Lab Guide is embedded in each lab and loads automatically when you open it — nothing to install.
{% endhint %}

***

<h3 align="center">Before you start</h3>

{% columns %}
{% column %}
{% hint style="success" icon="circle-check" %}
**What you'll need**

PDI Developer, Level 1 — Practitioner, or day-to-day work in Spoon. You should already be comfortable with transformations, jobs, steps and hops.
{% endhint %}
{% endcolumn %}

{% column %}
{% hint style="info" icon="tag" %}
**Built against**

Pentaho Enterprise Edition **11.0.0.0-232**, the build every course on the Academy runs. Pipeline Designer is installed by default with Pentaho Server.
{% endhint %}
{% endcolumn %}
{% endcolumns %}

***

<h3 align="center">Skills you'll gain</h3>

<table data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><i class="fa-browser" style="color:blue;">:browser:</i> <strong>The interface</strong></td><td>Design view · XML view · the main page · favourites, folders, duplicates, downloads and trash</td></tr><tr><td><i class="fa-diagram-sankey" style="color:blue;">:diagram-sankey:</i> <strong>Concepts</strong></td><td>Transformations · nodes · hops · jobs and job hop conditions · notes · data movement</td></tr><tr><td><i class="fa-play" style="color:blue;">:play:</i> <strong>Running pipelines</strong></td><td>Build, run and stop a transformation · analyse the results</td></tr></tbody></table>

***

<h3 align="center">Course outline</h3>

<p align="center"><i class="fa-file-lines" style="color:green;">:file-lines:</i> reading · <i class="fa-flask" style="color:orange;">:flask:</i> hands-on workshop</p>

{% hint style="info" icon="circle-info" %}
Draft outline — modules, lessons and times are still being confirmed. REPLACE-ME.
{% endhint %}

<table data-search="false"><thead><tr><th>Module</th><th width="100" align="center">Reading</th><th width="110" align="center">Workshops</th><th width="100" align="right">Time</th></tr></thead><tbody><tr><td>Introducing Pipeline Designer</td><td align="center">1</td><td align="center">—</td><td align="right">REPLACE-ME</td></tr><tr><td>Concepts &#x26; Terminology</td><td align="center">1</td><td align="center">—</td><td align="right">REPLACE-ME</td></tr><tr><td>Hello World</td><td align="center">—</td><td align="center">1</td><td align="right">REPLACE-ME</td></tr><tr><td><strong>Total</strong></td><td align="center"><strong>2</strong></td><td align="center"><strong>1</strong></td><td align="right"><strong>REPLACE-ME</strong></td></tr></tbody></table>

{% stepper %}
{% step %}

### <i class="fa-browser" style="color:blue;">:browser:</i> Introducing Pipeline Designer

`1 reading · REPLACE-ME`

What Pipeline Designer is and where it fits alongside the desktop client. Find your way around the main page, switch between the Design and XML views, and manage your work — favourites, folders, duplicates, downloads and the trash.

<details>

<summary>See the reading</summary>

<table data-search="false"><thead><tr><th width="79"></th><th>Lesson</th><th width="90">Time</th></tr></thead><tbody><tr><td><i class="fa-file-lines" style="color:green;">:file-lines:</i></td><td>Pipeline Designer — what it is, Design and XML views, managing your work</td><td>REPLACE-ME</td></tr></tbody></table>

</details>
{% endstep %}

{% step %}

### <i class="fa-diamonds-4" style="color:blue;">:diamonds-4:</i> Concepts & Terminology

`1 reading · REPLACE-ME`

The vocabulary in the browser: transformations built from nodes, hops that carry data between them, jobs and their hop conditions, notes that document your work, and how data moves across multiple outgoing hops.

<details>

<summary>See the reading</summary>

<table data-search="false"><thead><tr><th width="79"></th><th>Lesson</th><th width="90">Time</th></tr></thead><tbody><tr><td><i class="fa-file-lines" style="color:green;">:file-lines:</i></td><td>Concepts &#x26; Terminology — transformations, hops, jobs, notes, data movement</td><td>REPLACE-ME</td></tr></tbody></table>

</details>
{% endstep %}

{% step %}

### <i class="fa-flask" style="color:blue;">:flask:</i> Hello World

`1 workshop · REPLACE-ME`

Build, run and check a simple transformation end to end in the browser.

<details>

<summary>See the workshop</summary>

<table data-search="false"><thead><tr><th width="79"></th><th>Lesson</th><th width="90">Time</th></tr></thead><tbody><tr><td><i class="fa-flask" style="color:orange;">:flask:</i></td><td>Hello World — build a simple transformation</td><td>REPLACE-ME</td></tr></tbody></table>

</details>
{% endstep %}
{% endstepper %}

Pipeline Designer is a standalone Speciality: there is no capstone and no exam.

***

<p align="center"><a href="https://academy.pentaho.com/pdi-developer-path-sandbox/speciality-courses.md" class="button secondary" data-icon="arrow-left">Back to Speciality Courses</a></p>


---

# 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://academy.pentaho.com/pdi-developer-path-sandbox/speciality-courses/pipeline-designer.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.
