8.4
Table Of Contents
- Table of Contents
- Welcome to PlanetPress Workflow 8.4.1
- 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
- Working With Variables
- About Configurations
- About Related Programs and Services
- The Interface
- Copyright Information
- Legal Notices and Acknowledgements
l To use the “Use PlanetPress PDF/A archives” option,make sureto:
l Check the field as Multiple, select CHAR type and enter the width fields in Laserfiche
administration console as long as your PlanetPress fields.
l Insert a folder path to your PDI source files in the PlanetPress Image archive folder.
l If a field is checked as Required in Laserfiche administration console, fill the field value.
l If you want to assign an Informational Tag, do not check the Security tag option in the Laserfiche
administration console.
l If the output repository folder does not have access rights to read and create documents, the task will
not be able to export documents to the selected Laserfiche folder.
l If you intend to use PDI for number type, your decimal separator in both your Regional and Language
Options and in PlanetPress Index (PDI) numbers should be a dot (".").
l
The Laserfiche output task will only work if an activated PlanetPress Image is found, either locally or
on the network.
Lookup in Microsoft® Excel® Documents
The Lookup in Microsoft® Excel® Documents action task is used to complement your job file's metadata
by retrieving data from a Microsoft® Excel® spreadsheet on your system.The data retrieved is based on
existing data in your metadata, and it will either be added to your metadata or will append or replace your
existing metadata if it exists.
Fields on any level (Page, Datapage, Document, Group, Job)can be used, and the result field will be added
on the same level as the lookup field.
Note
This task will automatically "loop" through the metadata and repeat its action for each of your
metadata's data pages. This task should not be placed after a Metadata Sequencer task, otherwise it
will run as many times as there are metadata sequences, which will result in decreased performance.
Input
Any compatible data file, requires metadata to be present.
Processing
The task parses each level of the metadata and, for each field of the specified name it finds, a lookup is
made. If a field of the same name appears on multiple levels, the lookup will happen for all fields, on all