2019.1

Note
If the PDC File selection contains a folder path and the Working Folder also has
an entry, then the PDC File entry will be appended to the Working Folder entry.
One should be very cautious doing this, as it could easily lead to errors.
l
PDL Type: Select the desired PReS Classic output type for the job.
Note
Not all PReS Classic jobs can be swapped between output types. Jobs designed
for certain output types (such as AFPDS) will likely have settings specific to the
original output type.
Changing the output type at this point will likely lead to errors or require job
modifications to suit the changed output type.
l
Log level: Specifies the verboseness of messages returned by job processing. The
available levels are Error, Warning, Information and Debug.
Connect Workflow logs a successful PReS Classic job processing with a “Job Status:
Finished” status, followed shortly after by “Exec Status: 1”.
A successful PReS Classic job usually returns a zero value, but non-zero return values
do not necessarily signal job failure, as PReS Classic jobs can be set to return specific
values as part of job processing.
If the job still finishes with a Job Status of “Finished” and Exec Status “1” then the job
completed without error.
l
Instance: Used for specifying the PReS Classic Print Control instance. PReS allows up
to four instances of the same Print Control type (license dependent), and any one of those
instances can be selected here.
Selecting 1 would force Connect Workflow to use Print Control PRN1, whilst selecting 2
would launch PRN2, and so on. This is useful if you have a variety of Print Control
license speeds, and each license is assigned to a different PRNx instance. This allows
for manual load balancing, by selecting specific Print Control speeds for different jobs,
based upon your own criteria. Such as the size or urgency of the job being processed.
The default Auto option lets Connect Workflow choose whichever instance is available.
Page 460