Wizards make it easier to configure what happens to the data when a user submits your form and what the users see after submitting the form. Configure Form Actions (what the user sees) and Document Actions (what happens to my data) on the associated tabs in the Settings wizard. 

Open

Form/Workflow Actions

The Form/Workflow Action wizards help set up what the user sees when the form/workflow is submitted. You can access the Form/Workflow Action tab in the Guided Designer Settings mode.

Open

The wizards help guide you through the configuration process. Many of the wizards allow you to use form controls as templates to dynamically personalize what the user sees. See the section on Using Templates for full details. Hover over any field in the wizards for a helpful hint.

You can only configure one Form action for a form/workflow. This is as designed.

Success

The Form Actions available on the Success tab are:

• Display Message when User Submits Form

• Forward users to a web page of your choice

• Post data and forward users to your web page

• Forward to Paypal to complete payment

Open

Display Message when User Submits Form

After the user submits the form/workflow, the browser will display a standard frevvo page with a text message. For example, the message might say, “Thank you for completing our form.” You supply the specific text in the Message field. This option works best for relatively brief messages. It can be tricky to enter or edit large amounts of text in the wizard's Message field, so for verbose messages consider creating a simple HTML page for your message and choosing the Forward User to your Web Page wizard.

Open

The message can be customized, using the wizard's control dropdown, with values the user enters into the form. For example, if your form contains fields named firstName and lastName, you can set your message to "Thank you {firstName} {lastName}". Now when a user submits the form the controls templates {firstName} and {lastName} will automatically be replaced with field values "Thank you Joe Smith". See Using Templates for full details.

Another useful message is to display a link back to the form. For example the display message:

Open

The display message would be written as follows. The URL back to the form is the share dialog Raw Form link.

The form/workflow URL in the above HTML example can be constructed dynamically in a business rule. See this rule example.

Show In

Both the display message wizard and the forward to web page wizard allow you to select where the message is displayed on the page using the "Show In" dropdown. There are three choices: Frame, Parent and Top. This tells the browser where to show the text (if you chose Display Message) or the new Web page (if you chose the Forward to Web Page).

• Frame means inside the form's iframe

• Parent means inside the form iframe’s immediate parent

• Top means at the top of the page, regardless of how many parents are outside the iframe.

Forward Users to a web page of your choice

After the user submits the form/workflow, the browser will be redirected to another URL, which you supply in the  URL field. You must include the http:// prefix (e.g., http://myhost.com/thankyou.html). The project can have a Form Action Base URL which you set in the project properties. For example, you can have http://myhost.com/ in the project baseURL and simply “thankyou.html” in the Form Action URL field.

You can use a form/workflow field template in the URL field. Ex: http://localhost:8082/{URL!encode=false}. The encode=false template parameter is important to avoid mangling the URL. See Templatized String Parameters for details.

Open

Show In

These are the same options as described under the display message wizard above. Unless you have created a special page that you know will fit correctly within the form’s iframe you should not choose iframe. Choose the Parent or Top option instead.

Forward to another Form

You can forward the user from one frevvo form to another by specifying the raw URL of the second form in one of the Form Action wizards in the first form. When the user clicks Submit on the first form, you can choose to:

• Display the second form with data passed from the first form - use the Post data and forward users to your web page wizard.

• Display the next form without the data - use the Forward users to a web page of your choice wizard.

Suppose you have two forms in your project. One named ''formA'' and the other named ''formB''. When the user clicks the submit button on formA you want them to see formB next.

1. Edit formA

2. Select the Settings mode.

3. Select the Form Actions tab.

4. Select the Forward users to a web page of your choice

5. Enter the raw form URL for formB in the URL property field.

6. Click Submit then save the form.

7. Browse the URL for formA, click Submit. formB displays.

The raw form link URL can be found by clicking

Here is an example of a formB's raw form URL:

For portability, we recommend you use relative URLs such as:

Post Data and forward users to your web page

After the user submits the form, the browser will POST the user’s data to the URL you specify in the wizard’s URL field and display whatever is returned—the next page to display.

Fill in the Post Submission to your Application wizard with the following information:

• Enter the URL to the application where you want to post data:

  • Your URL field must include the http:// prefix (e.g., http://myhost.com/services/processPayment). The project can have a Form Action Base URL which you set in the project properties. For example, you can have http://myhost.com/services/ in the project baseURL and simply “processPayment” in the Form Action URL field.

  • The URL can also include control templates. This can be useful when you wish to specify a production versus a test server. For example: http://{serverURL}/services/processPayment/{customerId}. Using this form URL, you can specify serverURL using &_data=(serverURL:'testhost'). This makes switching from a test server to a production server a matter of setting the form URL parameter "serverURL" rather than editing the form itself. See Initializing Forms with Data for more details on _data usage.

  • You can use a form field template in the URL field. The encode=false template parameter is important to avoid mangling the URL. See Templatized String Parameters for details.

• Send the data as a PDF attachment or other image type using the Send Snapshot dropdown. The image type options are PDF, PNG or JPG.  Select the blank option from the dropdown to exclude this attachment in the submission.

• Attach an XML data document using the Data checkbox. This checkbox is checked by default. Uncheck it to exclude the XML data document in the submission.

• Attachments uploaded to your form/workflow are included if the Attachments checkbox is checked. This checkbox is checked by default. Uncheck it to exclude attachments in the submission.

• If you have Pixel Perfect mapped PDFs (ex: W-4, I-9 etc…) associated with your forms/workflows, choose  the action you want to take from the Send Generated PDF Forms control:
  • Check All to send all the mapped PDFs. This is the default value.
  • Check None to send none of the mapped PDFs
  • Check Select to display a list of all the mapped PDFs associated with your form/workflow. Click the ones you want to be part of the submission. Click again to deselect.

• POST responses must be displayed in the frevvo form frame.