> For the complete documentation index, see [llms.txt](https://docs.helmut.de/helmut4-releases/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.helmut.de/helmut4-releases/v4.6.1/helmut4-components/streamdesigner/wildcards/functional-wildcards/path-split.md).

# Path Split ?

This wildcard is replaced with the part of the file path that is defined. It is possible to define a part or a range to be used. This wildcard is used in the following ways.

* {path.split.#.?}
* For the following input (?) --> {path.split.0:2.\myserver\myfolder1\myfolder2\myfolder3}
* The output is going to be --> \myserver\myfolder1

{% hint style="info" %}
The split character is the \ (back slash) or / (forward slash) The individual path selection can be done from left to right (with positive numbers i.e 0,1,2,3,4) or right to left (negative numbers i.e -1,-2,-3,-4) (example -1,-2) When the : sign is used, it’s possible to specify a custom path range for the left and right side (example 0:-1). When a selection range is used (:), the number 0 can be used to set the left range on the first occurrence of the file path. -1 sets the right side selection to the end of the file path. Wildcard can be used on Windows and Unix file paths File path needs to be formated as \ (windows) or / (unix)
{% endhint %}

#### Advanced examples:

* Example 1:\
  • Input --> {path.split.2.\myserver\myfolder1\myfolder2\myfolder3}\
  • Output --> myfolder1
* Example 2:\
  • Input --> {path.split.-3.\myserver\myfolder1\myfolder2\myfolder3}\
  • Output --> myfolder1
* Example 3:\
  • Input --> {path.split.2:-1.\myserver\myfolder1\myfolder2\myfolder3}\
  • Output --> myfolder1\myfolder2\myfolder3
* Example 4:\
  • Input --> {path.split.2:-2.\myserver\myfolder1\myfolder2\myfolder3}\
  • Output --> myfolder1\myfolder2
* Example 5:\
  • Input --> {path.split.0:-2.\myserver\myfolder1\myfolder2\myfolder3}\
  • Output --> \myserver\myfolder1\myfolder2


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.helmut.de/helmut4-releases/v4.6.1/helmut4-components/streamdesigner/wildcards/functional-wildcards/path-split.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.