8.8

l Result Field:The metadata field name in which the result should be stored. This
field will appear in the same metadata level as the Lookup Field.
l Result Column:The name of the column where the information you want to retrieve
is located. For example, this could be a client email or full name.
l
button:Ads a new lookup line. You can have as many lines as you want. The
lines will be executed in order from top to bottom, so you can rely on a previous line
to bring additional information.
l
button:Removes the currently selected (highlighted) line.
l
button:Moves the currently selected line up one place.
l
button:Moves the currently selected line down one place.
l Search option group
l
Match case:Will force the lookup column names to be in exactly the same case as
the Lookup column name. This means if you type in "CustomerID"in the lookup
column and the actual column is named "customerid", it would not return any result.
On Error Tab
The On Error tab is common to all tasks. Details can be found in the" Task Properties Dialog"
on page771.
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.
l Send to Process: Check this option to send the job file to an error management process.
l
Error Process drop-down:Enabled only when the Send to Process option is checked.
Lists any process of which the initial input task is the Input Error Bin task.
l Action:In the initial input tasks, this group is disabled and defaults to Stop Process. In
all other tasks where the On Error tab is present, the following options are available:
l Default:By default, the task is ignored as if it did not exist and the error is logged
before continuing the branch or process; the job file is passed on to the next task in
the process. When an error occurs in a loop (or in a plugin that acts like a loop), the
loop may log the error, terminate the current iteration and proceed with the next
iteration.
Page 438