7.5

l Job: Apply the action on the specified field at the Job level.
l Group: Apply the action on the specified field at the Group level.
l Document: Apply the action on the specified field at the Document level.
l Data page: Apply the action on the specified field at the Data page level.
l Field Name: Enter the metadata field name on which the task will operate.
l Field Value: Enter the metadata field value. Note that if the chosenaction is Delete, this parameter is
disabled.For otheraction types,in order to set the field value, click the [...] button. This button opens the Data
Selector, which allows to specify a data selection as the field's value.
l Decimal Separator: Set the decimal separator for the Sum option. 3 possible modes are offered:
l Auto-detect: Interpret automatically the value. This option is ideal for documents using mixed decimal
separators. Note that the auto-detect option encountering the value 1,000 (with a comma separator),
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.
Comments Tab
The Comments tab, added in PlanetPress Suite 7.5, is common to all tasks. It contains a single text area (Task
comments)that lets you write comments about the task. These comments are saved when the dialog is closed with the
OKbutton, and are displayed in The Task Comments Pane.
NewWild Card
For a given Metadata Field Management action, all nodes of a given level mightbe updated with a new Field Value.To accom-
modate this,metadata/data selection functions have beenmodified 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.