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  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:

Image Removed

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

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  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:

Image Added

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

...

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

Image Removed

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

Image Removed

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

Image Removed

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.

The pve connector by default does not send handwritten signature images to ImageSilo. This can be overridden by setting frevvo.send.signature.xml to true in web.xml in pve.war. steps to login to your PaperVision®/ImageSilo® account:

Image Added

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

Image Added

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

Image Added

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.

The pve connector by default does not send handwritten signature images to ImageSilo. This can be overridden by setting frevvo.send.signature.xml to true in web.xml in pve.war. 

 See  ImageSilo® integration for full details. 

Save to Google Documents

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

 See  ImageSilo® integration for full details. 

Save to Google Documents

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

Post Data

When the form is submitted,  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.

Info

If a form /flow is configured to Post Data to a web application and it does not reach the specified folder in your Google drive it's intended destination successfully, notifies the tenant admin of the failure via an email. If of the failure via an email. If a flow does not reach the web application successfully, the flow administrator(s) are configured, the flow admin(s) receive the email instead of the tenant admin. Image Removed

Post Data

When the form is submitted,  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.

Additional Email Wizard

When the form is submitted,  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.

If you want an email to show a different From:address than what is configured on the Edit Tenant page, enter that address in the From: field. You can enter a static address or use templates to make the the address dynamic. The From address replaces the default no-reply@… , an address configured on the Edit Tenant screen or any settings in web.xml or frevvo.xml config files for In-house customers.

...

Additional Email Wizard

When the form is submitted,  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.

If you want an email to show a different From:address than what is configured on the Edit Tenant page, enter that address in the From: field. You can enter a static address or use templates to make the the address dynamic. The From address replaces the default no-reply@… , an address configured on the Edit Tenant screen or any settings in web.xml or frevvo.xml config files for In-house customers.

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.

...