8.5

New Wild Card
Since all metadata data pages, and possibly all physical data pages, are treated by the task at run-time in
order to evaluate the condition at each level, it is necessary to dynamically define metadata as well as data
selections to check all occurrences instead of a fixed one. To accommodate this requirement, a syntax
modification is introduced in all current data and metadata functions (region(), @(), field(), xmlget()). The
parameter identifying the data page or the level can now be replaced with a question mark (“?”), indicating
that a dynamic update of the current data page or level is required before evaluating the condition.
For example, in a PDF emulation, the format of a selected region would look like this:
region(?,0.59375,2.21875,1.85416,2.51041,KeepCase,NoTrim)
where "?" represents the current page. Using this expression, if the metadata structure has 3 data pages,
then the task willproceed 3 times sequentially, with ?=1 for the first data page, ?=2 for the second and ?=3
for the third and last data page index from the metadata structure.
In the Metadata tab of the Data Selector, the syntax of the selection is:
GetMeta(ItemDesc[?], 2, Job.Group[?].Document[?].Datapage[?])
where "?" is replaced with the current level index.
Note: For a relative position, the string has to be edited manually.
Use Case
Given a document input (created with metadata), this task can be used to regroup the PDF pages of the
received print stream in logical (metadata) documents, based on the keyword “Page 1 of” printed on the
pages, and then, treat each newly created document individually in the rest of the process
The process begins with the following tasks:
1. WinQueue Input: Intercepts a printed data file sent to a Windows printer queue.
2. Metadata Level Creation:Begins a new document node when “Page 1 of” is found on a data page.
l Action:Document
l Delimiter:Begins when