Under Bind to a value on a field select your created field for email validation message.
Click the pencil icon by Validation timestamp.
Under Bind to a value on a field select your created field for email timestamp.
If you have configured an email mapping for additional email data (see section below) click the pencil icon by Mapping name.
Select Bind to a static value and in the text box enter the Mapping name from the Map fields tab in the configuration page.
If a mapping name has been provided in the previous step then the edq_formmanager web resource will need to be added to the form if it hasn't already been added. Follow the steps below to add this web resource to the form:
Select Form Properties from the ribbon to open the Form Properties dialog box. In the Events tab click the top "Add" button and add the web resource "edq_formmanager" to the form.
With the OnLoad event selected, click the bottom "Add" button to open the "Handler Properties" dialog box. For library select the previously added "edq_formmanager" and in the textbox labelled Function type in "edq_onLoadHandler" (exclude the quotes). Be sure that both checkboxes labelled "Enabled" and "Pass execution context as first parameter" are selected.
Click "OK" to close the Form Properties dialog box.
Configure additional email data in an Email Mapping
Additional data values returned by the email API can optionally be configured in a mapping to populate entity fields by following the steps below:
Go to the Configuration page.
Click the Map fields tab.
From the entities list on the left select the entity for which you want to configure an email mapping.
Either select an existing mapping from the list in the MAPPINGS column or click + ADD to create a new mapping (enter a name in the textbox labelled Name in this case).
The data properties for the Result and Metadata property groups that have been selected under the Configure additional data tab are shown under the tab heading Email data fields.
Click on the drop-down listbox for each data property you would like to map and select the entity field that you want populated by the value returned by the API. You will need to ensure that the fields to accept the data values have been created on the entity beforehand.
Five types of entity fields can be selected: Number, Text, Choice, Lookup or DateTime. If you select:
Number, the integer or decimal value returned by the API is stored in the field. If the entity field only holds integers and a decimal value is returned by the API, the value will be truncated to an integer value.
Text, the text value returned by the API is stored in the field.
Choice, the item selected for the choice field will be the one where the text of the choice item matches the text returned by the API using a case insensitive match.
Lookup, the lookup record selected for the field will be the one where the text of the primary name column of the Lookup entity matches the text returned by the API using a case insensitive match.
DateTime, the date and time value returned by the API is stored in the field.
Without additional configuration, for both the Choice and Lookup cases, an empty value will be saved to the mapped field if a match is not found amongst the Choice or Lookup values.
For any data property that you want to ignore, choose the value Not mapped from the drop-down list.
When populated fields are unmapped
If a form field mapped in an Email Mapping has been used to populate entity records and is subsequently unmapped from the mapping, the field values for the records that have already been populated will need to be cleared. Otherwise, there is the possibility that the value in the field is associated with an email address returned from a subsequent email validation.