# Search files in all virtual file systems

The **Monitoring** → **Search file in all Virtual File Systems** section lists all files stored in the configured Virtual File Systems.

<figure><img src="https://3170459594-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FptDwkwGfIbMhLdRlTAmx%2Fuploads%2F0s3g4ccTL1B3l6r7pgIQ%2Fimage.png?alt=media&#x26;token=a64834d7-06c6-4bfd-9386-75ef1028c054" alt=""><figcaption></figcaption></figure>

At the top of the list of results, a toolbar offers different options. Learn how to use it [here](https://docs.primeur.com/data-mover-1.20/getting-started/navigate-through-primeur-data-mover#the-toolbar).&#x20;

Note that in the <img src="https://files.readme.io/53a0d9a-icona_1.png" alt="" data-size="line"> **select columns** option, by default the File URI and STENG columns **are not selected** and need to be checked manually to be shown.

The list of results can contain hundreds or even thousands of files. You can use the **Filters** panel on the right to narrow down your search.&#x20;

### Filters panel

The **Filters** panel allows you to refine your search by selecting the fields in which the system should look for matches.

The file will be retrieved even if the column is not shown. For example, by enabling the **STENG** toggle, the search will be run on the STENG column even if not shown in the list of results.

The **Search in** field is **case sensitive**.

The **File name** toggle is enabled by default when the panel opens. The full or partial original filename will be searched.

When multiple toggles are enabled, the system performs the search using **AND** logic across all selected fields.

<figure><img src="https://3170459594-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FptDwkwGfIbMhLdRlTAmx%2Fuploads%2FYQxcwFfAo17yxNrrx2JK%2Fimage.png?alt=media&#x26;token=5ac6aa40-0dec-476e-9299-095c65047a57" alt="" width="206"><figcaption></figcaption></figure>

The following columns are available as search criteria:

* **File name**
* **File URI**
* **Virtual path**
* **Cluster**
* **STENG**
* **All columns** - global toggle

Each column includes a toggle that can be switched on or off to include or exclude it from the search.

The **All columns** option acts as a global selector:

* If you manually enable **all** individual column toggles, the **All columns** toggle is activated automatically.
* Enabling **All columns** applies the search to **every column**, even if not shown.

Use the **Clear all** option to reset all toggles and selections to their default status.

Click **APPLY** to confirm the selected filters and execute the search.

### Accessing file options

Each file row includes a ⋮  3-dot icon located on the right side. Clicking this icon opens a contextual menu that provides access to the following actions:

* **View Metadata**
* **Mark as unread** (available only if the file has been previously read)

#### View Metadata

Selecting **View Metadata** opens a dedicated window displaying all metadata associated with the selected file.

At the bottom of the Metadata window, a **Mark as unread** button is available. This option allows you to set the file back to an unread state, making it easier to track items that require follow‑up.

#### Mark as unread

The **Mark as unread** action is available **only for files that have already been opened or processed**.\
Choosing this action updates the file’s status accordingly and can help you keep better control of your workflow.

When a file is marked as unread, its read‑related metadata is updated automatically:

* The **First Read Date** and **Last Read Date** are **reset**.
* The **Last Read Date** column is **cleared**.
* The **End Date** is updated to **now +&#x20;*****EXPIRY AFTER PUT***.
  * This new value appears in the **End Date** column.

You can mark a file as unread in two ways:

1. From the row options menu, by selecting **Mark as unread**.
2. From the **Metadata** window, by clicking the **Mark as unread** button at the bottom.

Both methods perform the same action.

#### Logging

Every time a file is marked as unread - whether via the options menu or the Metadata window - the action is **recorded in the Centralized Log** for auditing and traceability purposes.

#### Important note about integration flows

Integration flows can be configured to trigger specific actions whenever a file is read.

When a file is marked as unread, it is **restored to its initial status**, i.e., the status it had before being read. As a consequence, any actions previously triggered by the original “read” event may be triggered **again** the next time the file is opened. This behavior is intentional and ensures that the system reacts consistently to a new read event.
