> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.itential.com/itential-platform/6/studio/tasks/reference/transformation/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.itential.com/_mcp/server.

# transformation

> Use the transformation task to run JSON Schema Transformations (JSTs) during workflow job execution.

The `transformation` task runs JSON Schema Transformations (JSTs) during job execution, allowing JSON data to be consumed by endpoints with different formatting requirements.

For more information about JSTs, see the JST Designer documentation.

## Task variables

All `transformation` task variables are accessed via the **Data** tab of the task details window. The available variables depend on which JST the task is configured to run:

* **Input** variables are sourced from the **incoming schema properties** of the selected JST.
* **Output** variables (except `error`) are sourced from the **outgoing schema properties** of the selected JST.

The data type of each variable matches the data type specified by the corresponding schema property.

![](/_fern-img/d500ece2f26fc0a1f9439c2a966983b800c3c44f2e65de62d429afc722b3deb8.webp)

### Configure task variables

#### Select the JST

Click the **Transformation** dropdown at the top of the **Data** tab. Select the JST you want to run from the menu. The input and output variables populate based on the JST's incoming and outgoing schema properties.

#### Define input variables

Click the **Input** subtab to view all input variables. Define each variable using one of these sources: **Static** (manually type or paste the data), **Job** (data from a job variable), or **Task** (data from a previous task's output).

#### Define output variables

From the **Output** subtab, check the **Store Output as Job Variable** checkbox for any output you want to save, and specify which job variable to store it in.

![](/_fern-img/a88217ed626d9b29f2f56a095310105144b0dd702779373db8dd5f52f9bad51b.webp)

## Task options

Task behavior can be further customized by enabling or disabling options in the **Task Options** dropdown on the **Advanced** tab.

| Option                     | Description                                                                                                                                                                             |
| :------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Mask Input Variable Names  | Hide input variable names at runtime.                                                                                                                                                   |
| Mask Output Variable Names | Hide output variable names at runtime.                                                                                                                                                  |
| Extract Output             | If only a single outgoing schema property exists, removes it from its wrapper object.                                                                                                   |
| Validate Incoming          | Confirms that input is compatible with the incoming schema.                                                                                                                             |
| Revert to Default Value    | Enables the use of the `default` keyword in schemas. See the [JSON Schema documentation](https://json-schema.org/understanding-json-schema/reference/annotations) for more information. |

### Configure task options

#### Go to the Advanced tab

Select the **Advanced** tab on the task details window.

#### Expand Task Options

Expand the **Task Options** dropdown.

#### Enable or disable options

Click the checkbox of the relevant option.

![](/_fern-img/fc8d59b2fb6f1cba5d8233cae520c82206abef282bc916a312c67eda9b69c94f.webp)

> Use the transformation task to run JSON Schema Transformations (JSTs) during workflow job execution.