2020.1

template. In the Data Model, data are converted to the native data type. Dates, for
example, are converted to a DateTime object. How they are displayed in the Data Model
depends on the current operating system's regional settings.
Properties and runtime parameters
A data mapping configuration's properties hold data that can be used throughout the data
mapping workflow to compare against in conditions or to complement the existing data.
A number of properties are predefined, such as the path of the file that is currently being
processed, and the current position of the pointer in the data.
It is also possible to define custom properties. For instance, a unique ID could be created to be
added to each record in the output for integrity checks later on, or a time stamp could be added
to create reports. A tag could be added to process certain records differently.
Ultimately data mapping configurations are meant to be used in OL Connect Workflow
processes, to extract data from a particular type of data file.
Runtime parameters are properties that will pass variables from OL Connect Workflow to the
data mapping configuration.
Certain runtime parameters are predefined, such as the ones that refer to the JobInfo variables
in Workflow. For an overview see "Fixed automation properties" on page330.
You can also define custom runtime parameters. With those, you could, for example:
l Pass a JSON structure, containing boundary information as well as the name and
location of fields to be extracted dynamically from a data stream. This way, a generic data
mapping configuration could be used to process several kinds of different files.
l Define default values that are different from one data mapping instance to the next, even
when using the same data mapping configuration.
Defining custom properties and runtime parameters
You can define custom properties and runtime parameters under Properties in the
"Preprocessor step" on page246 (see "Preprocessor step properties" on page329).
To add a property:
Page 224