Streamline document automation with XML job files
Any job created in Document Automation Server (DAS) Content Extraction is saved in a job condition file. These are xml files usually created in the conditions folder and can be used to execute jobs from the Command line using the –JobFile parameter.
Developers can also create, edit, or generate XML job files using the information below:
| Option | Description |
|---|---|
jobspecialoptions | Set of options for the specified operation. Described in detail in Job Settings |
outputnamemask | The Name Template explained in File Naming |
usenametemplate | If the value is true, the Name Template will be used instead of the script. |
Metadata | Metadata settings for resulting PDF files. By default, metadata fields are left blank. Described in detail in PDF Metadata |
docoptions | Document option settings for resulting PDF files. Described in detail in section Display Modes |
Security | Security settings for resulting PDF files. By default, files are not secured. Described in detail in Security |
Sourcefiles | Source PDF file, folder, or tree. Can be multiple files for merge operations. |
advancedflags | Used to pass extra parameters, do not use unless directed by our technical team. |
logfile | After each job run, the output will be logged to a file based on this template. See section Location Settings for details. The filename by default uses the %TIMESTAMP% variable. On completion of a run, the file referenced by kingfisherlivelog is copied to a new file based on this logfile template |
kingfisherlivelog | When a job is running, output is written to this file. At the end of a job, the logfile template is used as a destination for a copy. |
textextraction | This contains the definitions of text to be extracted. |
forceocr | When set to true, any file processed will be OCRed (see the OCR options for other related settings) irrespective of whether it would normally be considered searchable. |