2019.1

Input data
If your input data is in a file, but the file is of a different type or has a different structure, create a
new data mapping configuration to match it. (See "Creating a new data mapping configuration"
on page212.)
When it's finished, send the new data mapping configuration to Workflow (see "Sending files to
Workflow" on page439).
Then open the Workflow configuration, double-click the Execute Data Mapping task to open it
and select the new data mapping configuration.
To capture input data from a different source:
1. Replace the Folder Capture Input task by the appropriate Input task. See: Input tasks in
Workflow's Online Help.
2.
Add a Send to Folder task directly after the new Input task and set its output folder to the
Workspace\Debug folder (%{global.pr_prom_workspace}\Debug). This task
writes the job file to a file, which can then be used as sample data file when creating a
data mapping configuration and debugging the Workflow process.
3. Run the process once (see "Testing and running the project" on page160) to capture the
job file that contains the input data.
4. Use that file to create a new data mapping configuration, send the data mapping
configuration to Workflow, and adjust the Workflow configuration, as described above.
Note
If the input data is JSON, you don't need a data mapping configuration: JSON data can be used in a
template as is. See: "Adding JSON data from a JSON file" on page773.
However, if you want the data to be saved in the OL Connect database, put the XML/JSON
Conversion plugin before the Send to Folder task to convert the JSON to XML, and create an XML
data mapping configuration to extract the data.
The email
Often this type of email has a Call to Action button which redirects the user to the website of
the vendor, where the user could log on to the site and follow an online payment process, for
instance.
To get an example (or to start over) you could use one of the template wizards that start an
'action email'; see "Email Template Wizards" on page503.
Page 165