> 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/pdi-transformation-steps-reference-overview/jms-consumer/general-jms-consumer/create-and-save-a-new-child-transformation.md).

# Create and save a new child transformation

If you do not already have a child transformation, you can create one while setting up the JMS Consumer step. When you click the **New** button, a new child transformation will automatically generate the required Get Records from Stream step in a new canvas tab. All your fields and types are customized in the child transformation's Get Records from Stream step to match the fields and types specified in the **Fields** tab of the parent JMS Consumer step.

1. In the JMS Consumer step, click **New**.

   The Save As dialog box appears.
2. Navigate to the location where you want to save your new child transformation, then type in the file name.
3. Click **Save**.

   A notification box displays informing you that the child transformation has been created and opened in a new tab. If you do not want to see this notification in the future, select the **Don't show me this again** check box.
4. Click the new transformation tab to view and edit the child transformation.

   It automatically contains the Get Records from Stream step. Optionally, you can continue to build this transformation and save it.
5. When finished, return to the JMS Consumer step.


---

# 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/pdi-transformation-steps-reference-overview/jms-consumer/general-jms-consumer/create-and-save-a-new-child-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.