Live Forms v5.1 is no longer supported. Click here for information about upgrading to our latest GA Release.

Skip to end of metadata
Go to start of metadata

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. The wizards are accessible from the form designer toolbar via the one button labeled Form Action and another labeled Doc Action. The action settings are summarized in the form properties Form Info tab.

On this page:

Form Action Wizards

The form action wizards configure what users will see when they submit your form.

Using these wizards you can:

  • Close the form window
  • Display a message to the user in the existing form windows
  • Forward to a nicely formatted web page that you have created elsewhere
  • Forward to Paypal if your form has sold items to the user
  • Post the form data to a service and then forward the user to a web page
  • Display a message formatted using a Google Document

The wizards help guide you through the configuration process. Many of the wizards allow you to use form controls as templates to dynamically create what the users sees rather than hard coding this. See the section on using templates in form/doc/error actions for full details.

Close the Window

After the user submits the form, if the form was shared via "Full Page/Popup" or "Link (Email/Web page)", the window containing the form will be closed.

Display Message

After the user submits the form, the browser will display a standard Live Forms 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.

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 a 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 in form/doc/error actions for full details.

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

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

Thank You!<br/><br/> 
{Company}'s account will be created within 24 hours.<br/> 
A "A New Account" email will be sent to {Email}.<br/><br/> 
<i>RedStone Customer Support</i><br/><br/> 
Click <a href="http://test.frevvo.com/frevvo/web/tn/redstone/user/designer/app/_OLlAYUouEd-0jOS-XMShUg/formtype/_YRsQYEyBEd-OltN4g8wchQ?_method=post &embed=true&locale=">here</a> to request another demo account

Javascript is not allowed in the display message. Plain text, html and control templates are allowed. Anything else will break the message and nothing will be displayed.

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 to Web Page of Your Choice

After the user submits the form, 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 application can have a Form Action Base URL which you set in the application properties. For example, you can have http://myhost.com/ in the application  baseURL and simply “thankyou.html” in the Form Action URL field.

You can use a form 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.

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.

Forwarding users to a web page that is located in a different domain will not work, with or /without the use of templatized strings.

Forward to Paypal

When the form is submitted, users will be forwarded to Paypal to complete payment. This multi-step wizard guides you through configuration:

  • Paypal account login
  • Paypal invoice description based on form values
  • Paypal payment amount from form values

and more...

Post Data then Forward to 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.

You URL field must include the http:// prefix (e.g., http://myhost.com/services/processPayment). The application can have a Form Action Base URL which you set in the application properties. For example, you can have http://myhost.com/services/ in the application  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. 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.

You have the option of also sending the data as a PDF attachment or other image type using the Send Snapshot dropdown. You can also attach an XML data document using the Send Data checkbox.

Forwarding users to a web page that is located in a different domain will not work, with or without the use of templatized strings.

Display Message formatted Using a Google Document

The Google Document wizard is deprecated. The standard Display Message now supports HTML and CSS formatting plus form fields templates to pull any data entered into the form into your email message subject and body.

Live Forms supports direct connectivity with Google Documents. This wizard allows you to format a display message using an online Google Document.

After the user submits the form, the browser will display a standard Live Forms page with text formatted using your google document. This wizards steps you through the process of logging into your google account and locating the document you want to use to format the message. See the Live Forms Google Documents connector for details.

Here is an expense report form that shows what you can do using the Google Documents Wizard. 

Form

Formatted Display

Error Action Wizards

These wizards optionally allow you to customize what the user sees if an error occurs. You can either display a message or forward users to a web page of your choice. The wizards behave exactly like the corresponding Form Action wizards above. The Display message can be customized to display the actual error that occurred by adding the special {frevvo_root_cause_msg} template to your message text. This is helpful for debugging, especially if your are using Live Forms Online.

Doc Action Wizards

The doc action wizards configure what happens to the entered data when a user submits your form. See Doc URI Wizards below for details on using the wizards to config the doc URI settings. Please also refer to the processing submissions tutorial .

This wizard has three tab as show in the screen images below:

  • Doc Actions
  • Additional Email
  • Doc URIs  

Using these wizards you can:

  • Do nothing with the data
  • Email the data to an email address
  • Post the form data to your web application
  • Format and Email the data using a Google Document
  • Save the data to PaperVision®/ImageSilo®
  • Save the data to a Google Document.

The wizards help guide you through the configuration process. Many of the wizards allow you to use form controls as templates to dynamically configuring wizard parameters hard coding this. For example you can dynamically set the email address to send the data to instead of hard coding an email address. See the section on using templates in doc action/doc URI wizards for full details.

Do Nothing

This is the default option, which simply stores the data in Live Forms' submissons repository if desired. (The other options also store the data in the repository if desired, but provide additional functionality.)

Do nothing is typically selected when you plan to do one or more of the following: 

The form's save property controls whether or not your form submission data is also stored in Live Forms' submission repository

Email Data

When the form is submitted, Live Forms will send an email message with the submission data, an optional XML document(s) , and optionally an image of the filled form via the Send Snapshot dropdown. The email can be sent to multiple comma separated email addresses. See Email Integration for further details. The "To:" email address is required. All other properties are optional.

The tenant admin can configure the from email address on the tenant admin's Edit Tenant page.

Save to PaperVision® /ImageSilo®

Live Forms integrates directly with Digitech Systems' PaperVision® and ImageSilo® document management products. This Wizard enables an easy way for you to save form submissions to your PaperVision® and ImageSilo® document management repository as PDF, TIFF, .JPG and .GIF format.

The wizards walks you through simple steps to login to your PaperVision®/ImageSilo® account:

To select the correct PaperVision®/ImageSilo® project where you want to store the form submission:

And finally to map your form fields so that the entered form field values become the index field values for your document.

Now when a users fills and submits your form and image of the form and any uploaded attachments will automatically be stored into the selected PaperVision®/ImageSilo® project. The document's index fields will be set to the values the user entered into the form.

See  ImageSilo® integration for full details. 

Save to Google Documents

Form submissions can be saved to your Google Apps Premier account. See the documentation for Connecting to Google Apps for full details. Also refer to the Leave Approval Workflow Tutorial for step by step instructions.

Do not use spaces or special characters when creating submission folder names.

Post Data

When the form is submitted, Live Forms POSTs the document set to the specified URI and ignores any returned XHTML or redirect. This option may be used for additional processing of data. Use form action post if you want to both submit data to your URI and forward to a web page or display returned XHTML.

You have the option of also sending a filled form image using the Send Snapshot dropdown as well as sending an XML attachment containing the form data.

Format & Email Using a Google Document

Tthe Google Document wizard is deprecated. The standard Email wizard now supports HTML and CSS formatting plus form fields templates to pull an data entered into the form into your email message subject and body.

Live Forms supports direct connectivity with Google Documents. This wizard allows you to format an email message using an online Google Document.

After the user submits the form, the data will be formatted using your google document and then emailed to the addresses of your choice. The wizard supports multiple comma separated addresses. This wizards steps you through the process of logging into your google account and locating the document you want to use to format the message. See the Live Forms Google Connector for details.

Here is an example of a form submission that was formatted using a Google document.

Additional Email Wizard

When the form is submitted, Live Forms can send an additional email message with the submission data, an optional XML document(s) , and optionally an image of the filled form via the Send Snapshot drop down  The email can be sent to multiple comma separated email addresses. The "To:" email address is required. All other properties are optional.

This is in addition to any document action you may have configured. For example, consider a Vacation Request Approval workflow. When the workflow is complete, we want to send a PDF to the internal HR system (using the document action) but in addition, we want to notify the employee requesting the vacation by email. Use the Additional Email wizard for this scenario.

To use the wizard, click Doc Action in the toolbar at the top of the form and select the Additional Email Tab. See  Email Integration for further details on configuring the content of the email.

Doc URI Wizards

The doc URI wizards enables you to manually set a URI to which the data will be sent when your form is submitted. The Google Spreadsheet wizard provides additional assistance in setting up the login to your google account and in selecting the spreadsheet.

Using these wizards you can:

  • Unset the document URI - do nothing 
  • Save Submissons to a Google Spreadsheet 
  • Manually set document URIs - to connect to database and other back end systems

Unset the Document URI

This is the default option. If one of the other 2 options is set you can clear them by clicking this one.

Save Submission to Google Spreadsheet

Live Forms supports direct connectivity with Google Spreadsheets. This wizard allows you to save submissions directly into Google Spreadsheets

After the user submits the form, the data will be written into a new row in the Google spreadsheet. This wizards steps you through the process of logging into your google account and locating the spreadsheet you where you want to save the submissions. See the Live Forms Google Connector for details.

Here is an example Google spreadsheet that is updated with a new row each time the form is submitted.

Manually set Document URIs

For an example of using Document URIs, see  the chapter Integrating with REST Applications and also the chapter on connecting to your database.

Using Templates in Form and Doc Action Wizards

The values/entries in all doc action/doc URI wizards can be customized with data entered in the form using templates. The values set in the following Form Action wizards can be customized with data from the form:

  • Display a message
  • Forward users to a web page
  • Post data and forward users to a web page

For instance, in the display message, you may wish to display a customized message with the user's name. You can use templates in the display message to do this.

  • Make sure you have two controls in the form called FirstName and LastName.
  • Click on Form Action
  • Click on Display a Message.
  • In the Message area of the wizard, type: Thank You {FirstName} {LastName} for submitting my form.
  • As a shortcut, you can also select the appropriate control from the drop down immediately below the Message area.
  • Click Finish.

Use the form by clicking on the Test button. Enter something into the First Name and Last Name controls. When you click submit, Live Forms will display the above message with {FirstName} and {LastName} replaced by the values entered by you.

Templates work the same way when used in URLs for forwarding to a web page or Post data. When referring to repeat controls you must use a special template syntax. See templates for repeat control for details.

There are built-in templates you can use:

  • {frevvo_root_cause_msg} - Add this to the Error Action Display Message to display the actual error that occurred.

Templates work the same way when used in Error Action Wizards as documented above.

 

 

  • No labels