2022.2

Table Of Contents
l
PReS Classic 6.3.0 or higher must be installed on the same system.
l
A valid PReS Classic license (either dongle or software based) must be available on the same
system.
Note: All PReS Classic licenses are issued and controlled by the PReS License Server
and not Connect. Thus a separate PReS Classic license is required.
Input
A PReS Classic job and the resources it needs.
These resources include the data file to run against the job, plus any graphic or font resources the jobs
needs, along with any required PReS Classic specific resources, such as TRF or PDI files.
Processing
The selected data file is merged with the selected PReS Classic job to create a print output stream.
If the PReS Classic job selected is an uncompiled PReS Classic script (PDS), it will first be compiled on
the fly and then run using the selected data file.
If the PReS Classic job selected is a pre-compiled PReS job (PDC) file, then the pre-compiled job will
run with the selected data file.
Output
The available output print stream options are AFPDS, GOPReS (Graphic Output), IJPDS, PCL, PDF
and PostScript (PS) outputs.
Task properties
General Tab
l
PDC File: Select either an un-compiled PReS Classic script file (PDS) which will need to be com-
piled on the fly, or a pre-compiled PReS Classic job file (PDC).
The job needs to be specified exactly. If you want to compile the job at run time, then you must
select a PDS file. If you wish to use a pre-compiled PReS Classic job, then select the PDC file,
rather than the PDS.
If a PReS Classic script file (PDS) is selected, Connect Workflow will use PReS Classic to com-
pile the selected file and then run the resultant PDC file, regardless of whether there was an exist-
ing PDC file within the folder already. Any existing PDC file in that folder will be overwritten by the
new compilation.
Note that the PDS or PDC file can be explicitly selected, or it could be set via a Connect Workflow
variable; see "Variable task properties" on page289.
Page 461