> 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/9.3-data-integration/pdi-transformation-steps-reference-overview/modified-java-script-value/sample-transformations.md).

# Sample transformations

The `design-tools/data-integration/samples/transformations` directory contains the following example KTRs that show how to use this step:

* JavaScript - Access database connection metadata
* JavaScript - Access environment variables
* JavaScript - Add 2 and a half seconds to a Date
* JavaScript - Base64 Decoder and Encoder
* JavaScript - create new rows
* JavaScript - date to string conversion
* JavaScript - dialog
* JavaScript - extract date from filename
* JavaScript - Get the filename from a path
* JavaScript - Hex to Integer conversion
* JavaScript - parse Debet-Credit prefix in numbers
* JavaScript - Parse XML
* JavaScript - process all fields per row
* JavaScript - replace values in a string with other values
* JavaScript - Skip rows after x rows
* JavaScript - Split String
* JavaScript - String to Number to String conversion
* JavaScript - Strip line feeds from text
* JavaScript - truncate a date


---

# 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/9.3-data-integration/pdi-transformation-steps-reference-overview/modified-java-script-value/sample-transformations.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.