7.4

Table Of Contents
l region():Always surrounds PDFdata selections.
l Page:The page of the PDFfrom which to retreive the data.
l Left:Exact horizontal position (in inches)that defines the left of the selection region.
l Top:Exact vertical position (in inches)that defines the top of the selection region.
l Right:Exact horizontal position (in inches)that defines the right of the selection region.
l Bottom:Exact vertical position (in inches)that defines the bottom of the selection region.
l Case Option: This can be one of three options:
l KeepCase:Keeps the current uppercase and lowercase letters as they are.
l UpperCase:Converts all letters to their uppercase equivalent.
l LowerCase:Converts all letters to their lowercase equivalent.
l Trim Option:Can either be "Trim"if you want to trim empty spaces before and after the data selection or "NoTrim"if
you want to retain the extra spaces.
Metadata Selections
These selections are used with any type of file, as long as a metadata file was created by a previous task.
Syntax
GetMeta(Field Name [, Option Flags, Metadata Path])
Here is a breakdown of the syntax:
l GetMeta():Always surrounds metadata selections.
l Field/Attribute Name:specifies the name of the field (or attribute, if the GetAttribute option flag is set) to retrieve.
l Option Flag (optional):Sets the options for the selection (see table below)
l Metadata Path (optional):Defines the precise path where the Metadata Field is located.
Option Flags
Name Value Behavior
GetAttribute 1 Search for the name argument in the attribute collection instead of the default field collection.
NoCascade 2
Search only the level specified by the path argument (defaults to Page level when path argu-
ment is empty), instead of default behavior, going from the Page level to the Job level.
FailIfNotFound 4
Raise an error and crash the job is the specified name is not found instead of returning an empty
string.
SelectedNodesOnly 8 Returns values from the selected nodes only.
Data File and Job File
Whichever source it may come from, a serial port, an e-mail message, or an LPR request, for instance, and whatever its for-
mat, data entering a PlanetPress Suite process via an input task is always referred to as a data file. Job file is a more general
term, that can refer to data files as well as other types of files traveling through a process. Image files, for example, can be
passed from task to task in order to be downloaded to a printer. So files traveling within a process are mostly referred to as
job files.
By default, job file names are generated using the %f variable. You may change the wayPlanetPress Suite Workflow Tools
names job files by using any combination of static characters, PlanetPress Suite Workflow Tools variables and Job info var-
iables. You could for instance enter Process_%w_Job_%f in the File name box to add the process name in the name gen-
erated by the PlanetPress Suite Workflow Tools.
Data in PlanetPress Suite Workflow Tools