1.8

l
Left/Right: Defines where to find the text value in the row.
l
Top/Bottom: Defines the start and end row of the data selection to
compare with the text value.
l
Entire width: Ignores the column values and compares using the whole
line.
l
Entire height: Ignores the row values and compares using the whole
column.
l
Entire page: Compares the text value on the whole page. Only available
with contains, not contains, is empty and is not empty
operators.
l
Times condition found: When the boundaries are based on the presence of
specific text, you can specify after how many instances of this text the
boundary can be effectively defined. For example, if a string is always found
on the first and on the last page of a document, you could specify a number of
occurrences of 2. This way, there is no need to inspect other items for whether
it is on the first page or the last page. Having found the string two times is
enough to set the boundary.
l
Delimiters before/after: Defines the boundary a certain number of data pages
before or after the current data page. This is useful if the text triggering the
boundary is not located on the first data page of the record.
l
Operator: Selects the type of comparison (for example, "contains").
l
Word to find: Compares the text value with the value in the data source.
l
Use selected text button: copies the text in the current selection as the one to
compare to it.
l
Match case: Makes the text comparison case-sensitive.
l
On script: Defines the boundaries using a custom JavaScript. For more information
see "Setting boundaries using JavaScript" on page257.
XML file boundaries
The delimiter for an XML file is a node. The Boundaries determine how many of those nodes go
in one record. This can be a specific number, or a variable number if the boundary is to be set
when the content of a specific field or attribute within a node changes (for example when the
invoice_number field changes in the invoice node).
Page 210