Export destinations
Choose where exported files land and how name collisions are handled.
Every export output sends its files to a Destination. This page is the reference for which destinations Scanix Desktop offers, what each one needs, how it decides on a folder, and what happens when a file with the target name already exists. For the bigger picture of formats and patterns, start with the Export overview.
Destinations
Each output card has a Destination dropdown and a Path / URL field (placeholder /output/path or https://...). The destination you pick decides what that field means and which extra fields appear.
| Destination | Path / URL field means | Extra fields | Delivery |
|---|---|---|---|
| Local Folder | A folder on disk. A Browse button opens a folder picker. | — | Delivers files today |
| An address. | Email To, Email Subject | Selectable; delivery not confirmed | |
| EDMS Connector | A connector address. | — | Selectable; delivery not confirmed |
| Database | A database target. | — | Selectable; delivery not confirmed |
| Web Service | An HTTP endpoint. | — | Selectable; delivery not confirmed |
Only Local Folder is a guaranteed delivery path today
Email, EDMS Connector, Database, and Web Service appear in the dropdown and can be selected and saved, but only Local Folder is verified end to end as a delivered file. Treat the other destinations as available options rather than guaranteed delivery, and use Local Folder for production output until the others are confirmed for your setup.
Local Folder
Local Folder is the primary, fully supported destination.
Choose Local Folder
On the output card, set Destination to Local Folder.
Pick the folder
Click Browse next to the Path / URL field and select a folder, or type the path in directly.
What you can rely on with a Local Folder destination:
| Behavior | Detail |
|---|---|
| Folder is created | If the chosen folder doesn't exist yet, Scanix creates it on first write. |
| Path is validated | Empty paths, .. traversal, and network or device paths are rejected, and a write through a symlink is refused. Output file names are sanitised too, so a reserved name can't slip through. |
| Writes stay inside the folder | Every file is pinned within the folder you chose. |
| Recent folders remembered | Your last 5 export folders are kept so you can reselect them quickly. |
Screenshot
An export output card with Destination set to Local Folder, the Path / URL field filled, and the Browse button beside it. — shot export-destinations-01
Subfolders
Two channels file output into subfolders automatically so a busy destination stays organised.
| Channel | Subfolder behavior |
|---|---|
| Hot Folder | Each run's files land under a per-batch subfolder (named from the batch) inside the output's destination. |
| Job Group (per-type subfolders) | A Per-type subfolders toggle files each routed document type under its own subfolder — for example …/Invoices, …/Receipts, …/Unrecognized. Default on. |
A document a Job Group can't route is filed under a visible Unrecognized (or Unclassified) subfolder, never silently mixed into the first type.
Process honors folder outputs only
When you press Process in the Viewer, outputs whose Destination is a Local Folder are exported; any output set to a non-folder destination is skipped. This matches the guidance above — keep production outputs on Local Folder.
Collision Handling
When a file with the target name already exists in the destination, the output's Collision Handling dropdown decides what happens.
| Option | Behavior |
|---|---|
| Auto-increment (_001, _002…) | Default. Appends _001, _002, … until a free name is found. |
| Overwrite | Replaces the existing file. A write through a symlink is still refused. |
| Error if exists | Fails the export for that file rather than overwriting or renaming it. |
Filenames vs collisions
Collision Handling only changes a name when one already exists. The base name itself comes from your Filename Pattern — if you want unique names up front (for example with a date or counter token), set them there. See File naming patterns.
Next steps
Export overview
Formats, destinations, and how Process, Hot Folders, and Job Groups all use the same export engine.
File naming patterns
Build output names from tokens like the date, source file name, counter, and captured fields.
Connectors
Where the Email, EDMS, Database, and Web Service destinations fit in the wider Scanix model.