> 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/text-file-input-cp/select-an-engine-text-file-input/using-text-file-input-on-pentaho-engine-cp/options-text-file-input-reuse/file-tab-text-file-input-pentaho-engine/selected-files-table-text-file-input-reuse.md).

# Selected files table

The Selected files table shows files or directories to use as source locations for input. This table is populated by clicking **Add** after you specify a **File or directory**. The input step tries to connect to the specified file or directory when you click **Add** to include it in the table.

The table contains the following columns:

| Column                 | Description                                                                                     |
| ---------------------- | ----------------------------------------------------------------------------------------------- |
| **File/Directory**     | The source location indicated by clicking **Add** after specifying it in **File or directory**. |
| **Wildcard (RegExp)**  | Specify a regular expression to match filenames within a specified directory.                   |
| **Exclude wildcard**   | Specify a regular expression to exclude filenames within a specified directory.                 |
| **Required**           | Required source location for input.                                                             |
| **Include subfolders** | Whether subfolders are included within the source location.                                     |

Click **Delete** to remove a source from the table. Click **Edit** to remove a source from the table and return it back to the **File or directory** option.


---

# 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/text-file-input-cp/select-an-engine-text-file-input/using-text-file-input-on-pentaho-engine-cp/options-text-file-input-reuse/file-tab-text-file-input-pentaho-engine/selected-files-table-text-file-input-reuse.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.