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

Configure Form Details

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

Manager allows you to configure the following form details:

To configure form details:

  1. Select Forms > Forms.
  2. Select a form.
  3. Click the Details tab to edit the form configuration.
  4. Form Display Name is the name of the form that is displayed to the user. It uniquely identifies the form within a specific Organization.
  5. Form Code is a short alphanumeric string, which uniquely identifies the form across all organizations. It is generally not displayed to users.
  6. Ref Form ID is the identifier used internally by the Organization and will be passed through during various web service calls such as prefill and receipt generation. It is optional, only used if there is an identifier that is used internally by the Organization that the form version is associated with.
  7. Form Manager dropdown if you wish to set a dedicated Form Manager by choosing an existing Administrator user. This user will be notified via email whenever the form’s status changes.
  8. Transact Insights checkbox should be selected when wanting to enable Journey Analytics form event analytics.
  9. Active checkbox should be selected initially to indicate the form is in use. Otherwise, the form is treated as soft-deleted and will not be rendered.
  10. Note

    Clear the Active checkbox to retire a form, by making it inactive, without deleting it.

  11. Log Submission History XML checkbox, if selected, allows you to log all form XML changes in the submission history record. If a form uses Transact functions, this option creates a new submission history record for the formUpdate operation.
  12. Note

    Excessive logging can degrade performance of Manager applications with high throughput, so ensure that the form doesn't have the Log Submission History XML selected. Otherwise, every time the form does a formUpdate or background save operation, Manager stores a full copy of the submission XML which can result in large growth of the submission history XML data table on high throughput systems with modern form applications .

  13. Form Version Selector allows you to select the service responsible for selecting the version of the form that will be rendered at request time. If left blank, the system default Form Version Selector service is used. Normally this should be Current Form Version service.
  14. Tracking Code/Receipt Number configuration settings.
  15. Click Save to update the changes.

Next, you may want to configure form flow.

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