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 Design Info

   Journey Manager (JM) Previously known as Transact Manager (TM). |   Platform Developer Form Builder |   Updated in v17.10 This feature was updated in v17.10.

Manager allows you to view key information about the development and building of a form version and navigate back to the originating form version in Maestro via the Maestro Form Design url.

Note

In Manager releases prior to v17.10, the Form Design Info tab is named the Form Archive Info tab.

To view form design information for a form version:

  1. Select Forms > Forms.
  2. Locate a form version.
  3. Click Form Design Info to see the following form design and build audit details:
    • Maestro Form Design - displays a direct link back to the corresponding form version in Maestro. Click this link to open the form version. If you are not already logged in to Maestro, you will be prompted to enter your credentials.
    • Author - the login that was used to create the form version.
    • Organization - the organization that the form belongs to.
    • Form Type - the type of form created, such as Maestro or Composer.
    • Form Name - the name of the form.
    • Form Key - the key of the form.
    • Form Generation Date - the date that the form was generated (built).
    • Form Archive MD5 - the MD5 checksum of the form archive.
    • Build Server URL - the URL of the server used to build the form.
    • Maestro Release - the Maestro release number that was used to build the form.
    • Build Version - the version of the core Maestro platform used to build the form. A build version that is different than the Maestro Release version means that the form has not been upgraded to the new release and hence has been built to be compatible with the older version.
    • Build Number - the number of the build used to build the form version.
    • Build Environment - the environment used to build the form. For Maestro it is normally local,but for Composer can reflect the test and staging environments.
    • HTML Desktop Template - indicates whether this form version has an HTML desktop template.
    • HTML Receipt Template - indicates whether this form version has an HTML receipt template. This is for Composer use.
    • PDF Receipt Template - indicates whether this form version has a PDF receipt template. This is for Composer use.
    • Supports Save Challenge - indicates whether this form version supports the save challenge feature.
  4. Click Close.
Note

For Composer forms, the details displayed on the Form Design Info tab are slightly different. These variations in the fields are applicable to Composer features including legacy ones.

Next, learn about form version details.

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