Folders & Triggers

PDF Enhancer folder paths and the file-based trigger workflow for hotfolder processing.

Folder configuration

Folder paths for the PDF processing workflow.

Parameter	Type	Default	Description
srcFolder	String	C:\ProgramData\…\PDFHotFolder	Source folder for input PDF files
destFolder	String	C:\ProgramData\…\PDFDestFolder	Destination folder for processed PDFs
archiveFolder	String	C:\ProgramData\…\ArchiveFolder	Archive folder for original files
statusFolder	String	C:\ProgramData\…\PDFDestFolder	Status folder for processing logs
debugFolder	String	""	Debug folder for diagnostic files

Folder requirements

• All folders must exist and be accessible to the PDF Enhancer process
• Source folder is monitored continuously for new PDF files
• Archive folder stores originals when archiving is enabled
• Debug folder contains diagnostic data only when debug = 1

---

Trigger configuration

File-based processing triggers and completion notifications.

Parameter	Type	Default	Description
trigger	String	order.ready	Name of the trigger file to monitor
removeTrigger	Boolean	0	Remove trigger file after processing
renameTrigger	Boolean	1	Rename trigger file during processing
outTrigger	String	""	Output trigger file name (signals completion to downstream systems)

Trigger workflow

1

Drop trigger file

Your upstream system places a file matching the trigger name (default order.ready) in the source folder once all PDFs for the order have been written.

2

Enhancer picks it up

The PDF Enhancer detects the trigger file, then processes all PDFs in the source folder.

3

Trigger handling

After processing, the trigger file is renamed (default) or deleted depending on renameTrigger and removeTrigger settings.

4

Optional completion signal

If outTrigger is set, a completion file is written to the destination folder for downstream systems to detect.