Live Forms v6.3 is no longer supported. Click here for information about upgrading to our latest GA Release.
Multi page forms
Â
On this page:
Go To Url
You can forward the user from one form to another by specifying the URI of the second form in the form action for the first. For example, suppose you have two forms in your application. One named ''formA'' and the other named ''formB''. When the user clicks the submit button on formA you want them to next see formB. In formA you open the form's edit properties and set the form action to "Go to URL" and in the URL property field you put the URI for formB.
This URI can be found by clicking the  Share icon for your form on the Forms Home Page.
Here is an example of a form's URI:
http://www.frevvo.com/frevvo/web/tn/<your tenant name>/user/designer/app/_DrBPUXM5Ed-glKSGT35lJA/formtype /_2j2vsJNAEd-Hauq_h2T-4Q?_method=post&embed=true
For portability, we recommend you use relative URIs such as:
frevvo/web/tn/<your tenant name>/user/app/_uJKtwbesEduG2Me8fheS4Q/formtype/_18go4Lx7EduG2Me8fheS4Q?_method=POST&embed=true
It is important that both forms have been made public. If formA is public but formB is not, when the user submits formA they will get a page not found error.
Using Templates
Fields in form B can also be initialized with data from form A using Url Parameters. Imagine form A contains a from palette text control labeled 'Customer Name' with Name property set to 'custName'. And form B has a palette text control labeled 'Full Name' with Name properity set to 'fname'. Using either Form Action Go to Url or Post with the URL set to that of Form B, append &_data=(fname:'{custName}') and when form B loads it's 'Full Name' field will be set to the value entered into form A's 'Customer Name' field.
See initializing via _data Url Parameters in the Initializing Forms with Data section for more details on using _data.