What are you looking for?

    Didn't find what you were looking for?

    Extend your Search in Community

    Got any questions?

    We're always happy to help with questions you might have. Contact Us

    Didn't find what you were looking for?

    Extend your Search in Community

    Got any questions?

    We're always happy to help with questions you might have. Contact Us

Manager Topics

Form Configuration Mapping

   Journey Manager (JM) Previously known as Transact Manager (TM).  |    Platform Developer |  v5.1 & Higher This feature is related to v5.1 and higher.

Manager supports the following form operations:

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

This mechanism provides some data elements to pass key details into and out of a user’s form session.

Note

Configuration mappings enable you to override the default form XML configuration paths for the system to write to and read from XML data form.

To configure form version’s configuration mappings:

  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. Configuration Mapping tab

  6. 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.
  7. Note

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

  8. Use Default Mappings - If selected, Manager will use default Configuration Mappings for Attachments, Payment Details, Receipts, and Signatures. Only when this is unticked may you change the defaults for the following five XPath locations.
  9. Attachments XPath - If Use Default Mappings is unticked, you may change the default XPath in the Form XML Data that contains the Attachments element.
  10. Payment Details XPath - If Use Default Mappings is unticked, you may change the default XPath in the Form XML Data that contains the PaymentDetails element.
  11. Form Signatures XPath - If Use Default Mappings is unticked, you may change the default XPath in the Form XML Data that contains the Signatures element. This element determines the type of Form Signature required. This must have a SignatureTypeSelected child element specifying the type of signature required.
  12. Abandonment Reason XPath - If Use Default Mappings is unticked, you may change the default XPath in the Form XML Data that contains the AbandonmentReason element.
  13. Receipt XPath - If Use Default Mappings is unticked, you may change the default XPath in the Form XML Data that contains the Receipt element.
  14. 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.
  15. 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.
  16. Contact Postcode XPath - The XPath that points to the element in the Form XML Data where the user’s contact postcode is stored.
  17. Contact Gender XPath - The XPath that points to the element in the Form XML Data where the user’s contact gender is stored.
  18. Contact Age XPath - The XPath that points to the element in the Form XML Data where the user’s contact age is stored.
  19. Save Challenge XPath - The XPath in the Form XML that contains the ‘Save Challenge’ element. This may also be defined in Maestro.
  20. 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.
  21. Transaction Value XPath - The XPath in the Form XML Data pointing to an element that contains the numeric value of this transaction.
  22. 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.
  23. Click Save to update the changes.

Next, learn how to configure form XML data.

Feedback

Did this topic provide the information you need or leave you wanting to know more? Is there some way we can make this topic better? Let us know how we can improve this documentation.

Contact Us

Community

Our Community is a dynamic, user-driven source of information that provides a home for sharing Journey platform knowledge where you can ask questions and get answers quickly.

Explore Community

Support

Temenos is committed to supporting our customers with Journey platform solutions installed in the cloud or on premise. Learn more about our Customer Care Team, and its policies, procedures, and processes.

Learn More