7.4

name is of type Date, you can use a Month Calendar to select the date and use only available Laserfiche var-
iables.
Laserfiche available data types:
l Character (Char): This type may contain a string of any type of characters. This is the most flexible type of field.
Use this type when you are not sure if the constraints of the other types will be appropriate.
l Integer: This type may contain a whole number between zero and 64,999.
l Long integer: This type may contain a whole number between zero and 3,999,999,999.
l Number: This type may contain a decimal number that supports up to 13 digits and 5 decimals.
l Date: This type may contain a date.
l Date/Time: This type may contain a date and time.
l Data: This type is unsupported by the Laserfiche repository output task and the Laserfiche client.
Note that Character, List, Integer, Long intger, Number and Date types allow you to use PlanetPress Image archive fields
(PDI).Also, note that all fields are validated by the Laserfiche repository output task.
LaserFiche Repository Output Task - Configure Tags
Tags are an optional method for categorizing documents that can be added to, or removed from a document at any point.
Configure Tags
l Selecting a tag will assign it to the exported documents.
l There are two types of tags: informational tags (icon with an exclamation mark ("!")), and security tags (icon with a
lock).
l All tag properties are the same as in the Laserfiche client console.
l The Comments columns allow the addition of comments to the tag. This column supports the use of any PlanetPress
Suite Workflow Tools variables.
Restrictions
l The column Comments in the Configure Tags interface allows a maximum of 200 characters.
l If you want to assign an Informational tag, do not select the Security tag option in Laserfiche admin console.
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.
This task will automatically "loop" through the metadata and repeat its action for each of your metadata's datapages.
This task should not be placed after a Metadata Sequencer task, otherwise it will run as many times as there are meta-
data sequences, which will result in decreased performance.
Input
Any compatible data file, requires metadata to be present.