Open a form or a template in the Maestro editor and select the Integration tab to see the form's integration options.
The Integration tab was called the Data tab in Maestro prior to 17.10 and it included Field Reference ID that is now called ID and is available in the Properties tab.
The Integration pane is broken down into the following sections:
TM Form Data
Expand the TM Form Data section to configure the data that will be sent to Journey Manager. The configuration options in this section vary depending on the data structure of the selected Maestro form and its assets.
Select the Include in Submission Data checkbox to include the component in the submission data.
Select the Use Entity XML Path checkbox to populate default values for the Full Path properties, which are based on the ID property of the component and include the selected asset’s data structure, for example, //AboutYou/FirstName.
You can't see this option unless the Include in Submission Data checkbox is selected.
Expand the Transact Integration section to configure how default values are defined for a component and how to set up submission data extract mappings to be used in Journey Manager.
Provide a field name in the Transact Insights FieldName field that is used for integration with Journey Analytics. If there are multiple fields in a form with the same label, for example, First Name, and the Insights Field Name is not set, Journey Analytics will combine the data for all fields with the same label. By default, Journey Analytics captures data through the field label, if the Insights Field Name is not filled out with a unique identifier.
Select one of the following options from the Data Extract Name that the name of the submission data extract field in Journey Manager.
Select one of the following system values from the Form Data Config Mapping dropdown list that are used in Journey Manager processes: Contact Email, Contact Phone, or Save Challenge.
Specify a default value displayed when the form is loaded in the Initial Data field .
Expand the Hidden Data section to configure the behavior of form data in an item when it is hidden by a visibility rule. The clear hidden data property only checks for visibility on the parent level of the component. It does not check for visibility on the children level of the component if this level is made visible. For the hidden data property to function correctly, the current block which contains the component in the form must be hidden. Clear hidden data options determine when, if ever, the component data is cleared. The options include:
When parent is cleared - use the parent's clearing rule to clear this item.
Immediately - clear the item as soon as it's hidden.
On submit - preserve the data in the item until the form is submitted.
Never - preserve the data regardless of the item's visibility.
Click Save to update the changes in the form or the template.