> 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/solution-analyst-path-sandbox/solution-analyst/schema-workbench.md).

# Schema Workbench

The second Solution Analyst course: Schema Workbench. 18 lessons in 9 modules: build, extend, secure and publish Mondrian cubes, query them with MDX, and hand in a Budget v Actual schema.

{% hint style="warning" icon="eye" %}
**SANDBOX — draft page.** Built from `bi-developer-sw-associate` 0.1.9 in Pentaho Content Manager. Module and lesson names, the reading-or-workshop kinds and the times come straight from each lab's manifest. Items marked REPLACE-ME need an owner's confirmation.
{% endhint %}

The second of the five courses on the Solution Analyst path. Build the Mondrian cubes that Analyzer slices: schemas, dimensions, hierarchies, levels and measures, then calculated members and named sets, queried directly in MDX, locked down with role-based security, translated for a French audience and sped up with aggregate tables. The capstone is a cube of your own for the finance team.

{% columns %}
{% column %}

<p align="center"><i class="fa-file-lines" style="color:green;">:file-lines:</i><br><strong>18 lessons</strong><br><em>across 9 modules</em></p>
{% endcolumn %}

{% column %}

<p align="center"><i class="fa-flask" style="color:orange;">:flask:</i><br><strong>11 workshops</strong><br><em>hands-on labs</em></p>
{% endcolumn %}

{% column %}

<p align="center"><i class="fa-clock" style="color:cyan;">:clock:</i><br><strong>~11h</strong><br><em>two to three days, or a week of evenings</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**

Business Analyst, or day-to-day use of Analyzer. The course models the SteelWheels SampleData schema, so comfort with relational tables, keys and basic SQL will make the labs quicker — but every step is shown.
{% 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 — the Pentaho Server and the Schema Workbench design tool that ships with it. The hosted labs run this exact release, so every screen, menu and dialog matches the guide step for step.
{% endhint %}
{% endcolumn %}
{% endcolumns %}

***

{% hint style="info" icon="cubes" %}

#### What you'll build

The SteelWheels cube explored, the Classic Models cube built step by step and the Miniature Models cube built independently — then extended with time and geographic dimensions and calculated members, queried in MDX, locked down with four Mondrian roles, translated into French and sped up with aggregate tables. The capstone is Budget v Actual: a schema of your own on the `QUADRANT_ACTUALS` table, with a calculated member, a named set and a region-restricted role, published and handed in. Its five checks decide your course accreditation.
{% endhint %}

***

<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-lightbulb" style="color:blue;">:lightbulb:</i> <strong>OLAP concepts</strong></td><td>OLAP vs OLTP · multidimensional cubes · star and normalised schemas · the ROLAP Mondrian engine</td></tr><tr><td><i class="fa-cubes" style="color:blue;">:cubes:</i> <strong>Schemas</strong></td><td>Cubes, dimensions, hierarchies, levels and measures · the SteelWheels, Classic Models and Miniature Models schemas</td></tr><tr><td><i class="fa-diagram-project" style="color:blue;">:diagram-project:</i> <strong>Extended models</strong></td><td>Shared time dimensions · geographic annotations · member properties · degenerate dimensions · calculated members</td></tr><tr><td><i class="fa-code" style="color:blue;">:code:</i> <strong>MDX</strong></td><td>SELECT, FROM and WHERE · axes and slicers · member references · named sets</td></tr><tr><td><i class="fa-lock" style="color:blue;">:lock:</i> <strong>Security, localisation and performance</strong></td><td>Mondrian roles and the grant hierarchy · French localisation with a dynamic schema processor · aggregate tables</td></tr><tr><td><i class="fa-trophy" style="color:blue;">:trophy:</i> <strong>Capstone — Budget v Actual</strong></td><td>A schema of your own · a calculated member, a named set and a region-restricted role · published and handed in</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" %}
Full lessons unlock once you're enrolled — this is the outline only. Times are the lab guides' own estimates.
{% endhint %}

<table data-search="false"><thead><tr><th width="382">Module</th><th width="115" align="center">Reading</th><th width="132" align="center">Workshops</th><th width="100" align="right">Time</th></tr></thead><tbody><tr><td>Getting Started</td><td align="center">1</td><td align="center">—</td><td align="right">~5m</td></tr><tr><td>Key Concepts &#x26; Terminology</td><td align="center">1</td><td align="center">—</td><td align="right">~20m</td></tr><tr><td>Schemas</td><td align="center">1</td><td align="center">3</td><td align="right">~2h 25m</td></tr><tr><td>Extend Model</td><td align="center">1</td><td align="center">2</td><td align="right">~1h 20m</td></tr><tr><td>MDX Query</td><td align="center">1</td><td align="center">2</td><td align="right">~45m</td></tr><tr><td>Data Security</td><td align="center">1</td><td align="center">1</td><td align="right">~2h 30m</td></tr><tr><td>Localization</td><td align="center">1</td><td align="center">1</td><td align="right">~1h 20m</td></tr><tr><td>Performance</td><td align="center">—</td><td align="center">1</td><td align="right">~45m</td></tr><tr><td>Capstone Project</td><td align="center">—</td><td align="center">1</td><td align="right">~1h 30m</td></tr><tr><td><strong>Total</strong></td><td align="center"><strong>7</strong></td><td align="center"><strong>11</strong></td><td align="right"><strong>~11h</strong></td></tr></tbody></table>

{% stepper %}
{% step %}

### <i class="fa-rocket" style="color:blue;">:rocket:</i> Getting Started

`1 reading · ~5m`

How to get the most out of this guide, and how to set your machine up — whether you are on a lab VM or installing Pentaho Server and Schema Workbench on your own laptop.

<figure><img src="https://1021209504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu2m9COjKaS0E9nT7B9bQ%2Fuploads%2F3xMMBkT24NikQzssqL3q%2Fsw-lab-setup.svg?alt=media" alt="Schema Workbench reads tables and columns from the SampleData HSQLDB database on port 9001 and publishes schemas to Mondrian on the Pentaho Server; Analyzer sends MDX to Mondrian, which sends SQL to SampleData through the hsqldb_sampledata data source; the server keeps its repository in PostgreSQL on port 5432"><figcaption><p>Schema Workbench, the Pentaho Server and the sample data</p></figcaption></figure>

<details>

<summary>See the full breakdown</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>Before You Start</td><td>~5m</td></tr></tbody></table>

</details>
{% endstep %}

{% step %}

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

`1 reading · ~20m`

OLAP vs. OLTP, multidimensional cubes, star vs. normalised schemas, and the ROLAP Mondrian engine — the mental model behind every lab.

<figure><img src="https://1021209504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu2m9COjKaS0E9nT7B9bQ%2Fuploads%2FoDvFhasyog2ykrPhGlyt%2Fdata-pipeline.svg?alt=media" alt="Five columns left to right: sources (operational systems; files and APIs) feed Pentaho Data Integration, which loads star-schema data marts; Mondrian on the Pentaho Server maps cubes onto the marts and serves Analyzer, reports from Report Designer, and CTools dashboards"><figcaption><p>From source systems to analysis: the cube sits at the end of the pipeline</p></figcaption></figure>

<figure><img src="https://1021209504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu2m9COjKaS0E9nT7B9bQ%2Fuploads%2FyQfszL5cX1pKjM9i7e2k%2Fsteelwheels-star.svg?alt=media" alt="The SteelWheels star schema: the ORDERFACT fact table with foreign keys CUSTOMERNUMBER, PRODUCTCODE and TIME_ID, the STATUS column and the QUANTITYORDERED and TOTALPRICE measures, joined to CUSTOMER_W_TER (read by the MARKETS and CUSTOMERS dimensions), PRODUCTS (PRODUCT) and DIM_TIME (TIME)"><figcaption><p>The SteelWheels star schema, with the columns its cube uses</p></figcaption></figure>

<figure><img src="https://1021209504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu2m9COjKaS0E9nT7B9bQ%2Fuploads%2FE6mRnB4x2cIBBNO8dHoy%2Fmondrian-request.svg?alt=media" alt="Four steps: 1, Analyzer, reports and dashboards send an MDX query to Mondrian on the Pentaho Server; 2, your published schema maps the cubes onto tables; 3, Mondrian sends SQL to the data mart, SampleData in this course; 4, rows come back and Mondrian sums them into cells for the tool"><figcaption><p>From a click in Analyzer to SQL and back</p></figcaption></figure>

<details>

<summary>See the full breakdown</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>Key Concepts &#x26; Terminology</td><td>~20m</td></tr></tbody></table>

</details>
{% endstep %}

{% step %}

### <i class="fa-cubes" style="color:blue;">:cubes:</i> Schemas

`1 reading · 3 workshops · ~2h 25m`

The building blocks of a Mondrian schema, then three guided builds against the SteelWheels SampleData: explore the prebuilt SteelWheels cube, build the Classic Models schema step by step, then prove your skills by constructing the Miniature Models schema independently.

<figure><img src="https://1021209504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu2m9COjKaS0E9nT7B9bQ%2Fuploads%2Fts6kHDZ58eseAnFnTjxz%2Fsteelwheels-schema.svg?alt=media" alt="The SteelWheels schema: the Sales_2003_2005 cube reads ORDERFACT, has two measures, Quantity (sum of QUANTITYORDERED) and Sales (sum of TOTALPRICE), and five dimensions: MARKETS (Territory, Country, State Province, City), CUSTOMERS (Customer, six member properties), PRODUCT (Line, Vendor), TIME (Years, Quarters, Months) and ORDERSTATUS (Status, degenerate)"><figcaption><p>One cube, its fact table, two measures and five dimensions</p></figcaption></figure>

<figure><img src="https://1021209504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu2m9COjKaS0E9nT7B9bQ%2Fuploads%2FlCAZrflro9Rntrqzsux1%2Ftwo-connections.svg?alt=media" alt="Two separate connections called hsqldb_sampledata: Schema Workbench&#x27;s, used while you design, and the Pentaho Server&#x27;s, set in Manage Data Sources. Publishing ClassicModels.xml with that name records it as the Classic Models catalog&#x27;s DataSource, and the server finds its own connection by it. Both reach SampleData on port 9001 separately"><figcaption><p>Two connections, joined only by the name you type when you publish</p></figcaption></figure>

<details>

<summary>See the full breakdown</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>Overview of Schemas</td><td>~30m</td></tr><tr><td><i class="fa-flask" style="color:orange;">:flask:</i></td><td>SteelWheels</td><td>~25m</td></tr><tr><td><i class="fa-flask" style="color:orange;">:flask:</i></td><td>Basic Model</td><td>~45m</td></tr><tr><td><i class="fa-flask" style="color:orange;">:flask:</i></td><td>Standard Model</td><td>~45m</td></tr></tbody></table>

</details>
{% endstep %}

{% step %}

### <i class="fa-diagram-project" style="color:blue;">:diagram-project:</i> Extend Model

`1 reading · 2 workshops · ~1h 20m`

Take a basic cube to production grade: shared time dimensions, geographic annotations for maps, member properties, degenerate dimensions, and calculated members (UnitPrice, Top 10 Customers) that embed business logic in the semantic layer.

<figure><img src="https://1021209504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu2m9COjKaS0E9nT7B9bQ%2Fuploads%2FWYHqOln5XhrkLgbPdvqq%2Fdimension-kinds.svg?alt=media" alt="Three ways a dimension reaches ORDERFACT in the Sales_FY2003_2005 cube: MARKETS, CUSTOMERS and PRODUCTS are private, each joined from its own table through its foreignKey; ORDER STATUS is degenerate, its Type level reading ORDERFACT&#x27;s STATUS column with no table or join; TIME is shared, defined once under Schema on DIM_TIME and joined through DimensionUsage on TIME_ID"><figcaption><p>Private, degenerate and shared dimensions</p></figcaption></figure>

<details>

<summary>See the full breakdown</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>Overview of Extend Model</td><td>~20m</td></tr><tr><td><i class="fa-flask" style="color:orange;">:flask:</i></td><td>Extended Model</td><td>~40m</td></tr><tr><td><i class="fa-flask" style="color:orange;">:flask:</i></td><td>Calculations</td><td>~20m</td></tr></tbody></table>

</details>
{% endstep %}

{% step %}

### <i class="fa-code" style="color:blue;">:code:</i> MDX Query

`1 reading · 2 workshops · ~45m`

Query cubes directly with MDX to validate and troubleshoot your schemas — SELECT / FROM / WHERE, axes vs. slicers, member references — then centralise reusable member collections with Named Sets.

<figure><img src="https://1021209504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu2m9COjKaS0E9nT7B9bQ%2Fuploads%2FjPv2RyfwicPytu8uvC36%2Fmdx-anatomy.svg?alt=media" alt="An MDX query mapped onto its result: the COLUMNS set, Sales and Quantity, becomes the column headers; the ROWS set, 2004 and 2005, the row headers; FROM names the Sales_2003_2005 cube; the WHERE slicer, APAC, shows on no axis but is part of every cell&#x27;s coordinates, and in the SQL becomes a condition on the cell query"><figcaption><p>Where each part of a query lands in the result</p></figcaption></figure>

<details>

<summary>See the full breakdown</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>Overview of MDX Query</td><td>~15m</td></tr><tr><td><i class="fa-flask" style="color:orange;">:flask:</i></td><td>MDX Query</td><td>~15m</td></tr><tr><td><i class="fa-flask" style="color:orange;">:flask:</i></td><td>Named Sets</td><td>~15m</td></tr></tbody></table>

</details>
{% endstep %}

{% step %}

### <i class="fa-lock" style="color:blue;">:lock:</i> Data Security

`1 reading · 1 workshop · ~2h 30m`

Lock cubes down with Mondrian's role-based security: roles and role mappers, then the grant hierarchy (Schema, Cube, Hierarchy, Member) and rollup policies, applied hands-on as four progressively restrictive roles on the Miniature Models schema.

<figure><img src="https://1021209504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu2m9COjKaS0E9nT7B9bQ%2Fuploads%2FulmNSSQEhfwvtHvmQn8U%2Fgrant-nesting.svg?alt=media" alt="Grants nested on the Miniature Models schema. The Regional Manager Role: SchemaGrant access none holds a CubeGrant on Sales_FY2003_2005 with access all, holding a custom HierarchyGrant on Customers with topLevel State and MemberGrants on NJ, NY and PA. The Analyst Role&#x27;s Customers grant: Territory hidden above topLevel, Country to City visible, Customer Name hidden below bottomLevel"><figcaption><p>Where each grant applies, on the course's own schema</p></figcaption></figure>

<figure><img src="https://1021209504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu2m9COjKaS0E9nT7B9bQ%2Fuploads%2FSetPH89vu3b0zULCel7w%2Frole-mapping.svg?alt=media" alt="One row per test user: exec_user, Executive, Executive Role, sees everything; sales_mgr, Sales Manager, Sales Manager Role, this cube only; region_mgr, Regional Manager, Regional Manager Role, NJ, NY and PA; analyst, Analyst, Analyst Role, Country to City with no customers. The lookup map turns each platform role into its Mondrian role"><figcaption><p>From a User Console user to what Mondrian lets them see</p></figcaption></figure>

<figure><img src="https://1021209504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu2m9COjKaS0E9nT7B9bQ%2Fuploads%2FFrix8jkOCxnWLEDGRsIp%2Frollup-policies.svg?alt=media" alt="The same grant, MemberGrants on NJ, NY and PA with no topLevel, under three rollup policies. full: All Customers 10,645,949.18, NA 3,852,061.39 and USA 3,627,982.83, so USA minus the visible states leaks 2,625,083.61. partial: all three show 1,002,899.22. hidden: all three empty. The states show the same Sales in every column"><figcaption><p>One grant, three rollup policies</p></figcaption></figure>

<details>

<summary>See the full breakdown</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>Overview of Data Security</td><td>~30m</td></tr><tr><td><i class="fa-flask" style="color:orange;">:flask:</i></td><td>Mondrian Security</td><td>~2h</td></tr></tbody></table>

</details>
{% endstep %}

{% step %}

### <i class="fa-language" style="color:blue;">:language:</i> Localization

`1 reading · 1 workshop · ~1h 20m`

Serve a global audience from a single schema. Tokenize the Classic Models schema, deploy English and French property files, and configure Mondrian's dynamic schema processor so cubes translate automatically by user locale.

<figure><img src="https://1021209504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu2m9COjKaS0E9nT7B9bQ%2Fuploads%2FycSG2r60zA7sQ9kAvw1V%2Flocalization-pieces.svg?alt=media" alt="Schema Workbench publishes the tokenized schema to the Classic Models catalog. On the Pentaho Server the message bundles, localePropFile in mondrian.properties and the catalog&#x27;s DynamicSchemaProcessor and UseContentChecksum parameters feed token replacement, giving Analyzer French captions in a French session and English in an English one. Publishing again resets the catalog&#x27;s parameters"><figcaption><p>Where each piece lives</p></figcaption></figure>

<details>

<summary>See the full breakdown</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>Overview of Localization</td><td>~20m</td></tr><tr><td><i class="fa-flask" style="color:orange;">:flask:</i></td><td>FR Localization</td><td>~1h</td></tr></tbody></table>

</details>
{% endstep %}

{% step %}

### <i class="fa-gauge-high" style="color:blue;">:gauge-high:</i> Performance

`1 workshop · ~45m`

Speed up the cube with aggregate tables: build two pre-computed roll-ups from ORDERFACT, switch Mondrian's aggregate matching on, declare them with AggName in the schema, and prove from the generated SQL that queries hit the small tables.

<figure><img src="https://1021209504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu2m9COjKaS0E9nT7B9bQ%2Fuploads%2FGw3TXpfDHOY4klA9KV5z%2Faggregate-pick.svg?alt=media" alt="Three MDX queries on Sales and the table each one&#x27;s SQL reads: Territory reads Miniature_Sales_AGG_2 (55 rows), in both aggregates but the smaller; Country reads Miniature_Sales_AGG_1 (129 rows), the only aggregate with Country; State Province is in neither and reads ORDERFACT (2,996 rows) joined to its dimension tables"><figcaption><p>The smallest aggregate that fits</p></figcaption></figure>

<details>

<summary>See the full breakdown</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>Aggregate Tables</td><td>~45m</td></tr></tbody></table>

</details>
{% endstep %}

{% step %}

### <i class="fa-trophy" style="color:blue;">:trophy:</i> Capstone Project

`1 workshop · ~1h 30m`

Budget v Actual: a schema of your own on QUADRANT\_ACTUALS, with a calculated member, a named set and a region-restricted role, published and handed in. Its five checks decide the course accreditation.

<figure><img src="https://1021209504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu2m9COjKaS0E9nT7B9bQ%2Fuploads%2FgJ7YBVg88qWGVaEW1bOP%2Fcapstone-budget.svg?alt=media" alt="The target design: the Quadrant Budget schema holds the Budget_v_Actual cube on QUADRANT_ACTUALS. REGION and DEPARTMENT (Department, then Position) read the fact table&#x27;s own columns with no join; ACTUAL, BUDGET and VARIANCE feed the measures, then Variance % and the Over Budget Departments named set; the Central Region Manager role restricts the cube to Central"><figcaption><p>What you build: one schema, one cube, one role</p></figcaption></figure>

<details>

<summary>See the full breakdown</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>Budget v Actual</td><td>~1h 30m</td></tr></tbody></table>

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

***

<h3 align="center">Exam &#x26; accreditation</h3>

{% columns %}
{% column %}
{% hint style="info" icon="clipboard-check" %}
**The course exam**

40 questions drawn at random from a pool of 50, covering the taught modules. The pass mark is 80%. It's open-book: browse any module or ask the AI assistant while you work. The Capstone Project is assessed by its own five checks rather than by the exam.
{% endhint %}
{% endcolumn %}

{% column %}
{% hint style="warning" icon="file-certificate" %}
**Course accreditation**

Finish the lessons and workshops, pass the exam and complete the capstone's checks, and you'll automatically be able to download your course accreditation. It states your name, the course and the Pentaho version you studied against, and is valid for two years. The exam is self-paced and not proctored. REPLACE-ME — the course names the accreditation "Pentaho Schema Workbench"; confirm the name.

This course is the second step on the Certified Solution Analyst learning path: Business Analyst, then Schema Workbench, Metadata Editor, Report Designer and CTools, leading to the Certified Solution Analyst credential — which closes with a proctored exam delivered through Kryterion's Webassessor.
{% endhint %}
{% endcolumn %}
{% endcolumns %}

***

<p align="center"><a href="https://academy.pentaho.com/solution-analyst-path-sandbox/solution-analyst.md" class="button secondary" data-icon="arrow-left">Back to the Solution Analyst path</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/solution-analyst-path-sandbox/solution-analyst/schema-workbench.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.
