Forms Overview

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

Journey Manager allows you to host Maestro forms so they are available to form users and applicants. Forms are exposed to users by being hosted on a user space. Each form has at least one form version, an entity that wraps the set of form-related data to be versioned. If multiple form versions exist, one of them is distinguished as the current form version, and is used when rendering the form. There is some data shared by all form versions, but most settings are maintained separately for each form version.

Manager recognizes forms of different form types, such as dynamic PDF forms or Composer SmartForms. Each form version has a form type and the artifacts needed to render the form. The form template file is used to render the form and possibly the form receipt. The receipt template file can be used to render the receipt instead. The form data configuration file defines the data structure underlying the form, and is vital for dynamic SmartForms hosted on Manager.

You create a form in Maestro using the Maestro editor. This form is called a Maestro form. Then you deploy it in Manager and then configure it to implement a user journey functionality, such as a back-end connectivity, transactions or receipts delivery. However, you are not limited to the Maestro tools to create a form and can use other alternatives.

Manager defines various form events, which you can use to trigger a function implementing some specific business requirements.


A Manager's form is represented differently in Maestro. For more information, see Maestro's form overview.

Next, learn about the form life cycle.