1 Form/Workflow Actions
- 1.1 Success
  - 1.1.1 Display Message when User Submits Form
  - 1.1.2 Forward Users to a web page of your choice
  - 1.1.3 Post Data and forward users to your web page
  - 1.1.4 Forward to Paypal to complete payment
  - 1.1.5 Paypal for Workflows
    - 1.1.5.1 URL Parameters
    - 1.1.5.2 Workflow Action: Forward Users to a Webpage of Your Choice
    - 1.1.5.3 Individual Step
- 1.2 Error
  - 1.2.1 Display Message if an error occurs
  - 1.2.2 Forward users to an error page of your choice
2 Document Actions
- 2.1 Send Documents
  - 2.1.1 Do Nothing
  - 2.1.2 Send Email
  - 2.1.3 POST data to your web application
  - 2.1.4 Send to Google Drive
  - 2.1.5 Send to File System
  - 2.1.6 Send to SharePoint
- 2.2 Send Data
  - 2.2.1 Do nothing
  - 2.2.2 Post Submissions to a Google Sheet
  - 2.2.3 Manually set document URIs
- 2.3 Additional Email Wizard
  - 2.3.1 How to set up Multiple Document Actions
3 Using Templates in Form and Doc Actions
4 Form & Doc Action Failure Notifications

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.

Form and Document Actions functions for workflows are very similar to those for forms. The term "Form Actions" used on this page also refers to "Workflow Actions".
Forward to PayPal is not available in workflows, but can be configured following this documentation.
Document Actions that happen in between steps are known as Activity Doc Actions. See the Email & Webhook documentation for details.

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.

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 UsingTemplatesinForm/Doc/ErrorActions 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

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.

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 UsingTemplatesinForm/Doc/ErrorActionsfor 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

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

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

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.

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.

Forwarding users to a web page that is located in a different domain will not work.

Forward to Paypal to complete payment

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

Paypal for Workflows

Workflows do not have a corresponding "Forward to PayPal to complete Payment" action. However, you can configure either the Workflow Action: Forward users to a webpage of your choice or a link control in an individual step to connect to PayPal from a workflow.

Replace the values in the <> brackets in the examples with your values. (These parameters are explained below.) You can also substitute the value of a form control in below URLs using templates, for example: to use a control named "amount" in the URL, configure it as:

&amount={amount}

PayPal Sandbox: https://www.sandbox.paypal.com/cgi-bin/webscr?cmd=_xclick&business=<Paypal business name>&amount=<Payment amount>&item_name=<Payment Description>&currency_code=<Currency Code>&return=<Return URL>&cancel_return=<Cancel URL>&custom=<Custom Value>&invoice=<Invoice Value>&notify_url=<Notification Url>

Production: https://www.paypal.com/webscr/webscr?cmd=_xclick&business=<Paypal business name>&amount=<Payment amount>&item_name=<Payment Description>&currency_code=<Currency Code>&return=<Return URL>&cancel_return=<Cancel URL>&custom=<Custom Value>&invoice=<Invoice Value>&notify_url=<Notification URL>

URL Parameters

Paypal business name: Paypal business name. Typically, this is the email address you use to sign in to Paypal.
Payment amount: The payment amount.
Payment Description: The payment description is what your users will see when paying.
Currency Code: The currency code used in payment. Example: USD, CAD, INR
Return URL: A user will be redirected to this page after payment is complete. If you leave this blank, users will be redirected to a standard platform URL.
Cancel URL: A user will be redirected to this page if payment is cancelled. If you leave this blank, users will be redirected to a standard platform URL.
Custom Value: PayPal will return this custom value in the IPN as well as the acknowledgement email.
Invoice Value: PayPal will return this invoice value (such as an Invoice Number) in the IPN as well as the acknowledgement email.
Notification URL: A notification URL. If you enter a URL here, PayPal will notify you using Instant Payment Notification. Please see the PayPal documentation for details.

Form and Doc Actions