7.4

Table Of Contents
interprets it as a thousand while interpreting 1.000 (with a dot separator), as one.
l .: Treat every value with the dot (".") decimal separator. Commas (",") are treated as thousand sep-
arator.
l ,: Treat every value with the comma (",") decimal separator. Dots (".") are treated as thousand sep-
arator.
l Condition: Define criteria for the Metadata Field Management action execution. The condition must be TRUE for the
action to execute. To set up conditions, the Rule Interface is displayed, allowing to edit the condition for the given
action. See theRule Interface page for more details.
On Error Tab
The On Error Tab is common to all tasks. Details can be found on Task Properties Dialog.
If storing the message or ID, if they are store in a jobinfo they will be available in any error handling process where errors are
being forwarded. In all cases, if your process continues after the error, the contents of the variables selected in this window
will be available for the rest of your process, or whenever they are overwritten.
Common Errors
Though some error messages are specific to a task in particular, others may apply to any and all tasks because they are
related more to the system than to PlanetPress itself. Some examples would be W3813, W3830, W3991, W4005. These cor-
respond to issues such as not having any space to write files, permission errors on folders or files, etc.
NewWild Card
For a given Metadata Field Management action, all nodes of a given level mightbe updated with a new Field Value.To accom-
modate this,metadata/data selection functions have beenmodified to accept a wild card parameter "?", indicating the function
operates on allnodes (not just one) of a given level.For example, in a PDF emulation, the format of a selected region is:
region(?,0.59375,2.21875,1.85416,2.51041,KeepCase,NoTrim)
where “? represents the current physical data page processed by the task.
Limitations
l The name of the metadata field to add must adhere to thess syntax rules: start with a letter, followed by zero or more
letters, numbers, underscore or dash. The name is not case-sensitive.
l Metadata Fields Management actions on the Page level are not possible since the entire task execution is based on the
data page node.
l The task raises an error if the selected Metadata Fields Management action is Sum and if one of the field valuesis not
numeric.The task supports approximately 15 digits of precision in a range from 2.23 x 10
-308
to 1.79 x 10
308
.
Metadata File Management
The Metadata File Management Action Task is used to execute actions on Metadata files. This task does not modify the data,
job infos, variables or any other part of your process.
Input:
This task takes any file as input and does not modify it.
Process:
This task does not execute any change to the process, its files or variables. It only executes the selected action on Metadata.