2019.1

Fortunately, there is a workaround for this; see "Using COTG Elements" on
page573.
The Form's validation should ensure that the data that the user submits is valid (see
"Changing a Form's validation method" on page692 and "How to make COTG
elements required" on page575).
2.
Create a data mapping configuration
Use the resulting XML file to create a data mapping configuration (see "Data mapping
configurations" on page211).
1.
Choose File > New > Data mapping Wizards > From XML file.
2.
Select the XML data file as its source and click Next.
3.
Set the XML Elements option to /request/values. This will automatically add an
extraction step for the submitted form fields.
4.
Click Finish. The file is opened in the DataMapper and the form fields are
automatically extracted including the data for the signature and camera object.
5. Save the data mapping configuration.
3.
Create a template
Create a Designer template and personalize it using the data mapping configuration (see
"Personalizing content" on page761). Strings, base64-encoded strings and SVG data,
stored in data fields using the DataMapper can be added to the template just like any
other variable data; see "Variable Data" on page775. They will show up in the template
as they are.
Strings and base64-encoded strings show up as strings.
SVG data will be interpreted and displayed as an image.
Note
The Signature data returned by the COTG app (as of Android 10.6.0, iOS 10.6.0,
and Windows 6.0) is formatted so that the signature will automatically be scaled to
fit in the containing box in a template. With previous versions of the app the format
of returned signatures could vary.
Page 554