2020.1

COTG Timesheet Form
The COTG Timesheet Form data mapping configuration is designed to extract data from the
sample data file (Sample Data.xml).
The configuration also adds two fields to each record, using JavaScript: a unique ID (guid) and
a field that contains the action of the Form.
Note that the COTG account is the same in all of the records in the sample data. It is inserted
into the sample data by the Project Wizard.
COTG Timesheet Report
The COTG Timesheet Form data mapping configuration is designed to extract the data that are
submitted via the app. It first extracts the common fields, and then the information from the rows
in the form, in a loop. For information about how to extract a variable number of similar
elements from an XML file, see: "From an XML file" on page234.
In order to create this data mapping configuration, the input data needed to be saved to a file
first (see "Saving input as sample data" on page150).
The sample data file is located in the Configurations\Data folder, but you will also see it when
you open the data mapping configuration itself.
The Workflow configuration
There are four processes in the COTG Timesheets Workflow configuration. Some of them use
the OL Connect tasks that are normally used in a Web process or a Print process (see "Web
processes with OL Connect tasks" on page186 and "Print processes with OL Connect tasks"
on page184).
Creating the forms
The cotg_ts_deploy_form process is triggered when any file enters the Workspace\In folder,
but its Execute Data Mapping task expects an XML file that is structured exactly like the Sample
Data.xml file (in the Resources\Data folder).
The Execute Data Mapping task outputs records in the Metadata.
Subsequently, the Metadata Sequencer task creates a loop; the rest of the process is
performed as many times as there are records in the Metadata, for one record at a time:
l
The Set Job Infos and Variables task reads data from the (current record in the)
Metadata and puts them into variables.
Page 148