Destinations

A destination defines a final intake directory and a separate staging directory. Paperweight writes and validates staging content before a non-overwriting rename into the final location.

Option	Default	Accepted values	Behavior
id	required	1-64 letters, digits, _ or -	Stable destination identifier
folder	required	Absolute local or UNC path	Existing final intake directory
stagingFolder	required	Absolute local or UNC path	Separate non-overlapping directory on the same filesystem root
naming	PreserveStem	PreserveStem, JobId	Final basename policy

With PreserveStem, folder-acquired documents use their original basename with .pdf or .tif. Scanner capture has no original source pathname, so its filename uses the job ID. JobId always uses the job ID. A conflicting final filename is held; Paperweight does not overwrite it or invent a suffix.

Set up delivery and import

Make the final destination exist before use. Staging can be created by Paperweight if the operator has permission. Ensure the receiving application ignores staging and only ingests complete final files. Local drive letters must match; for UNC destinations use sibling folders on the same share. Passing the root check does not establish actual SMB atomic-rename behavior.

The signed-in operator needs permission to write and rename files in these folders. Paperweight records delivery to the folder; the receiving application handles import and filing.

Healthcare workflow targets

Paperweight delivers finished files to a local or network folder for the receiving workflow to import. The receiving workflow controls where those documents are filed and how staff access them.

Target	What to check in your workflow
TouchWorks EHR	Receiving import workflow, potentially through an intermediary document filer
Veradigm Practice Management	The site's supported document import workflow and naming/format requirements
Keena InteleFiler	SMB file intake, staging exclusion, filename contract, and downstream ingestion
DocuWare	File import, including the expected folder, document format, and metadata
OneDrive / SharePoint	Your upload or sync process sends finished files to the intended library or folder
Network shares and other targets	Accepted format/codecs, permissions, completion behavior, and naming contract

Important

Keep Paperweight's working files and recovery copies in a protected folder on the PC, outside OneDrive or other synced folders. Use your organization's upload or sync process to send finished documents to OneDrive or SharePoint. Keep passwords and other credentials out of configuration files.