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
Input
This task can use any data file, as long as it is accompanied by metadata. This metadata may have been
directly generated or could be extracted from a PDFusing the Embed and Extract PlanetPress Workflow
Metadata task.
Processing
The metadata is read and PDFindexes are located. These indexes are defined in the PlanetPress Design
document as data selections, in which the Archive / Email / Fax properties define the data as an index with a
name.
When all the indexes are collected, a PDIfile is generated with those indexes.
Output
The output is the same as the input, no modification is done to either the data file or the metadata. However,
a PDIfile is generated and saved in the location specified in the task.
Metadata to PDITask Properties are as such:
l Archive Folder:Specifies where the PDIfile should be saved. This should be the same location as
the PDFfile that the PDIrefers to.
l Filename:The file name for the PDI. This name should correspond exactly with the name of the
PDFthat the PDIfile refers to.
l Index Group:
l PDI:Only generate a PDI file.
l PDIand XML:Generate both the PDIand an XMLequivalent (not used by PlanetPress Search).
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
not generate output. The On Error tab can be used to overwrite the default behaviors.