2018.2

Restrictions
l
Each Laserfiche Repository Output task uses a connection to Laserfiche. You can use
as many Laserfiche Repository Output tasks at the same time as your Laserfiche
license allows. If you see the error message ‘The session number was exceeded’ in the
PlanetPress Workflow Service Console, it means you have exceeded your allowed
number of connections.
l To use the “Use PlanetPress PDF/A archives” option, make sure to:
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
Page 408