2022.2

Table Of Contents
Task properties
Data Mapper Tab
The Data Mapper step generates a Record Set from a specific source: data mapping on the appro-
priate source (Current Data File, Database or PDF/VT data file), Retrieving items from the Connect
Database (filter setting) or uses the current job Metadata. The resulting Record Set is given to the Con-
tent Creation part of the task. In order to optimize the process, blocks of 100 records are sent sequen-
tially to the Content Creation in parallel, instead of waiting for the whole record set to be created.
l
Source: Indicates the source of the Record Set Metadata:
l
Data Mapping Configuration: Executes data mapping on the appropriate source. Select
the appropriate data mapping configuration in the list:
l
"None": Select to execute default, basic data mapping on the input PDV/VT file.
l
"%o": Select to use a dynamic data mapping configuration name. Click on %o to
change the expression that determines the name of the data mapping configuration
to use. Right-click it to open the contextual menu that allows to select variables, data
and lookup functions (see "Data selections" on page49).
l
Configuration Names: Select the appropriate data mapping configuration. Adding
configurations is done through the Send to Workflow option in the DataMapper Mod-
ule.
Click the Open data model of selected configuration button to view the data
model attached to the configuration in the Data Mapper module, to verify that the
right one is used. Only works for configurations listed (will not work for "None" or
"Dynamic" options).
l
No storing or post-processing of the data records (faster): This option prevents
data from being written to the database. Instead, records are streamed directly into
the Content Creation process for immediate merging. Turning this feature on can
improve data mapping performance significantly, as well as the time required for the
cleanup process.
This option is unchecked by default.
Note: Since with this setting the data is not written to the database, it isn't pos-
sible to use a Job Creation Preset (see the Job Creation tab, below). There is
also no way to do post-processing on the extracted data after the All In One
operation has completed. Any post-processors defined in the data mapping
configuration will be disabled.
Page 496