8.5
Table Of Contents
- Table of Contents
- Welcome to PlanetPress Workflow 8.5
- System Requirements
- Basics
- Features
- The Nature of PlanetPress Workflow
- About Branches and Conditions
- Configuration Components
- Connect Resources
- About Data
- About Documents
- Debugging and Error Handling
- The Plug-in Bar
- About Printing
- About Processes and Subprocesses
- Using Scripts
- Special Workflow Types
- About Tasks
- Task Properties
- Variable Properties
- Working With Variables
- About Configurations
- About Related Programs and Services
- The Interface
- Copyright Information
- Legal Notices and Acknowledgements
Properties
General Tab
l Job Preset file:Select which Job Preset to use to generate the job. To be used in this dialog, a preset
must have been sent to PlanetPress Workflow using the Package File function in PlanetPress
Connect.
l
Default: The IDs in the metadata are used instead of a job preset file. Select this option if the
Print Content Set is the result of the "Retrieve Items" on page504 task.
l "%o":Select to use a dynamic preset name. Click on %o to change the expression that
determines the name of the preset to use. The preset name must be available in the list below.
l Preset Names:Select the appropriate preset to generate output.
Connect Proxy Tab
This tab is common to all OLConnect tasks and defines where to process the jobs send through these
tasks. When these fields are empty, they use the defaults set in the OL Connect User Options page of the
preferences.
Note
Defaults are not used unless the configuration is sent to the Workflow service.
l OL Connect Proxy Address: Enter the machine name or IPAddress where the OLConnectServer
resides.
l Port: Enter the port to use to communicate with the OLConnect Server. Default:9340
l User name:Enter the user name expected by the OLConnect Server.
l Password:Enter the password expected by the OLConnect Server for the above user name.
On Error Tab
The On Error tab is common to all tasks. Details can be found in the" Task Properties Dialog" on page666.
By default, any action task, branch, splitter or condition that generates an error will simply be ignored, and
the task just under it (not within a branch)will be given control of the job file without any modification. Any
initial input task that generates an error will stop the process from running as a whole, and output tasks will