2020.2

interface. All options, including those that cannot be set in Design view, can be set via the
data-params attribute in the HTML, or in code; see "Using the COTG plugin: cotg-
2.0.0.js" on page587.
Image & Annotation
The Image & Annotation element is meant to be used with an image that needs input from the
user. When inserting an Image & Annotation element you have to select the image. The user
can simply click (or rather, touch) the image to bring up the annotation dialog. Annotations can
be made in a Marker (semi-transparent) or Pencil (solid) style, in different colors and with
different widths.
Annotations are submitted in SVG format by a hidden input. The name of that input is the ID of
the Image & Annotation element, followed by "-note-data", for example image_annotation1-
note-data.
Locale
The Locale Element does not have a UI element in the form. Inserting it adds a hidden input
field that will contain the device's set locale when the form is submitted. This data is sent in
plain text format and is available when processing the form data. The format is defined by the
device.
Repository ID
The Repository ID element retrieves the repository ID (read only) from the app based on the
currently logged on COTG user. You could put the Repository ID in a hidden input, so that
when the form is submitted, the Repository ID is submitted as well. This information can be
used on the server side to take specific actions, such as sending properly branded emails.
Signature
The Signature Element adds a signature box to a COTG form. These signatures are filled in via
touch input, either with a finger or capacitive pen. Touching the signature box opens up a
fullscreen box used to sign (generally more useful in Landscape mode depending on the
device); after confirming, the dialog saves the data into the Form.
Signature data is transmitted in SVG plain text format. This type of data can be stored in a data
field in a Data Mapping and dragged from the Data Model into a template as is. In Preview
mode it will be displayed as an image because the Designer, just like web browsers, knows
how to display this kind of data.
Page 694