Form Configuration Mapping

   Journey Manager (JM) The transaction engine for the platform.  |    Platform Developer |  All versions This feature is related to all versions.

Manager allows you to override the default form XML configuration paths for the system to write to and read from XML data form. This, in turn, let you pass some key data into and out of a user’s form session. You can modify the following form's operations:

• Attachments
• Payments
• Signatures
• Email verifications
• Form saving and retrieval
• Anonymous submissions

To configure form version’s configuration mapping:

1. Select Forms > Forms.
2. Select a form and then click Edit.
3. Select a form version and click Edit Form Data Config.
4. Click the Configuration Mapping tab.

   

5. Select the Default Mappings checkbox to use default Configuration Mappings for attachments, payment details, receipts, and signatures. Clear this checkbox to change the defaults for the following five XPathXPath (XML Path Language) is a query language for selecting nodes from an XML document. In addition, XPath may be used to compute values (e.g., strings, numbers, or Boolean values) from the content of an XML document. XPath was defined by the World Wide Web Consortium (W3C). locations.
Note

If Use Default Mappings is not selected, you can change the default XPath in the Form XML Data.

6. Select the Use Default Mappings checkbox to uses default Configuration Mappings for Attachments, Payment Details, Receipts, and Signatures. Otherwise, clear the Use Default Mappings checkbox to configure the following XPath locations manually.
7. Attachments XPath - edit the default XPath of the Attachments element in the Form XML Data.
8. Payment Details XPath - edit the default XPath of the PaymentDetails element in the Form XML Data.
9. Abandonment Reason XPath - edit the default XPath of the AbandonmentReason element in the Form XML Data.
10. Receipt XPath - edit the default XPath of the Receipt element in the Form XML Data.
11. Contact Phone XPath - The XPath that points to the element in the Form XML Data where the user's contact telephone number is stored. This may also be defined in Maestro.
12. Contact Email XPath - The XPath that points to the element in the Form XML Data where the user's contact email address is stored. This may also be defined in Maestro.
13. Contact Postcode XPath - The XPath that points to the element in the Form XML Data where the user's contact postcode is stored.
14. Contact Gender XPath - The XPath that points to the element in the Form XML Data where the user's contact gender is stored.
15. Contact Age XPath - The XPath that points to the element in the Form XML Data where the user's contact age is stored.
16. Enter an XPath to an element containing the answer to the challenge question users will need to answer to return to an anonymously saved form in the Save Challenge XPath field. The element in question must not be blank when the form is saved.
    Note

    You can also configure a save challenge for a form in Maestro.

17. Transaction Ref Number XPath - The XPath in the Form XML Data that points to the element that contains the transaction reference number which will be stored with the submission. This is provided for backward compatibility.
18. Transaction Value XPath - The XPath in the Form XML Data pointing to an element that contains the numeric value of this transaction.
19. Old Wet Signatures Required XPath - The XPath in the Form XML Data pointing to an element that contains true if the form requires wet signatures.
20. Click Save to update the changes.

Next, learn how to view form XML data.