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

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

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.

Some designers want to show a logo or other image in the Form Action Message. You can do this using HTML. If your logo is stored on a static site, you can point the HTML img tags to that image. However, if you prefer you can store the image right within the frevvo form.

1. Add an image control to your form. You can uncheck the Visible and Printable properties if you do not want to display them to users in the actual form.
2. Upload your logo or another image.
3. Right-click the image control and select "Copy image address".
   

4. Paste the image address into the HTML img tags, as in this example.

   Thanks for completing your Employee OnBoarding, and welcome to the team! <br/><br/><img src="https://app.frevvo.com/frevvo/web/tn/frevvodocs/u/e1dd0efb-f368-4e60-937a-fe08849485d5/app/_WtkW4A9KEeOGyY8morCUKA/formtype/_BuFnUJW0EeyG_9ERIIwC7A/asset/_ESA8oZW0EeyG_9ERIIwC7A_languageballoons.png" style="width:200px;height:100px;"/>

   

5. When the user completes the form, the image will display in the Form Action Success Message.
   

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.

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 Share for formB on the Forms and Workflows Home Page.

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

https://<your server>:<your port>/frevvo/web/tn/<your tenant name>/u/60b97620-6e5b-4d97-a93e-6b81e803a671/app/_mzwYwGMrEeeemceeobqUCg/formtype/_6NZG8GMrEeeemceeobqUCg?_method=post&embed=true

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

//frevvo/web/tn/<your tenant name>/user/app/_uJKtwbesEduG2Me8fheS4Q/formtype/_18go4Lx7EduG2Me8fheS4Q?_method=POST&embed=true

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.

Passing Data from One Form to Another

If formA and formB both contain the same data source, and the Form Action in form A is set to '''Post''' to the raw form Url of form B, then form B's fields from schema will be initialized with the values entered into form 1. Follow these steps:

1. Create formA and formB from the same schema.
2. Edit formA
3. Select the Settings mode.
4. Select the Form Actions tab.
5. Select the Post data and forward users to your web page wizard.

6. Enter the raw form link for formB in the URL property of the wizard. Here is an example of the raw link share URL

   http://<your server>:<your port>/frevvo/web/tn/<your tenant name>/user/max/app/_mzwYwGMrEeeemceeobqUCg/formtype/_6NZG8GMrEeeemceeobqUCg?_method=post&embed=true

   Remember, you can use a relative URL if you are concerned with portability.
   
   

   //frevvo/web/tn/<your tenant name>/user/max/app/_mzwYwGMrEeeemceeobqUCg/formtype/_6NZG8GMrEeeemceeobqUCg?_method=post&embed=true

7. Test formA by filling in the fields and clicking Submit. formB displays with the fields populated with the data in formA.

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 property set to 'fname'. Using either Form Action Forward to Webpage 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.

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 the 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 canceled. 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 acknowledgment email.

• Invoice Value: PayPal will return this invoice value (such as an Invoice Number) in the IPN as well as the acknowledgment 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.

Workflow Action: Forward Users to a Webpage of Your Choice

Open the workflow properties, and select the Workflow Actions tab. Click the Forward Users to a webpage of your choice radio button. Add the URL (configured like this example) to the URL field. After submitting the last step, the user will be redirected to PayPal for payment processing.

Example: https://www.sandbox.paypal.com/cgi-bin/webscr?cmd=_xclick&business=mycompany@gmail.com&amount=2&item_name={BMyDesc}&currency_code=USD&return=http://localhost:8080/frevvo/web/tn/t1/u/53f402db-5ef2-4052-95a0-a44a2d000832/app/_JuJjkWogEeq1EfoSPaFbFA/formtype/_6Vmn0G02EeqEf75e1_YeJg?_method=post&embed=true&cancel_return=http://localhost:8080/frevvo/web/tn/t1/u/53f402db-5ef2-4052-95a0-a44a2d000832/app/_JuJjkWogEeq1EfoSPaFbFA/formtype/_6Vmn0G02EeqEf75e1_YeJg?_method=post&embed=true&custom=123&invoice=123&notify_url=

Individual Step

If you need PayPal integration in specific step of a workflow, add a link control in that step with above URL and set return URL pointing back to current step of the workflow using built-in data. They can then submit the step and the workflow will continue as designed.

Example: https://www.sandbox.paypal.com/cgi-bin/webscr?cmd=_xclick&business=mycompany@gmail.com&amount=2&item_name={BMyDesc}&currency_code=USD&return=http://localhost:8080/frevvo/web/tn/{form.tenant.id}/u/{form.user.uuid}/app/{form.application.id}/flow/{flow.id}/current?typeId={flow.type.id}&cancel_return=http://localhost:8080/frevvo/web/tn/{form.tenant.id}/u/{form.user.uuid}/app/{form.application.id}/flow/{flow.id}/current?typeId={flow.type.id}&custom=123&invoice=123&notify_url

Error

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 you are using frevvo Online.

Display Message if an error occurs

Forward users to an error page of your choice

Document Actions

The document action wizards configure what happens to the entered data when a user submits your form/workflow. You can access the Document Actions 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 for dynamic behavior. See the section on Form and Doc Actions#UsingTemplatesinForm/Doc/ErrorActions for full details. Hover over any field in the wizards for a helpful hint.

See Form and Doc Actions#DocURIWizards below for details on using the wizards to configure doc URI settings. Please also refer to the processing submissions tutorial.

This wizard has three tabs as shown in the screen image below:

• Send Documents
• Send Data
• Additional Email

Send Documents

Using this wizard you can:

• Do nothing with the data
• Email the data to an email address
• Post the form data to your web application
• Save the data to a Google Document
• Save the frevvo submissions to a local or remote filesystem using the Filesystem connector.
• Save submissions to a SharePoint site
• Save submissions to an External System such as Docuware

The wizards help guide you through connecting your forms/workflows to various destinations. Many of the wizards allow you to use form controls as templates to dynamically configure wizard parameters. 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 for full details.

Do Nothing

This is the default option, which simply stores the data in frevvo's submissions repository. (The other options also store the data in the repository but provide additional functionality.)

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

• View the submissions using the submission repository.
• Form and Doc Actions#SaveSubmissiontoGoogleSpreadsheet.
• Save submissions to your own database or other backend system using Form and Doc Actions#ManuallysetDocumentURIs
• Use the form action wizard to Form and Doc Actions#PostDatathenForwardtoWebPage

Send Email

When the form/workflow is submitted, frevvo will send an email message with the following selectable options attached. These include submission data,  an XML document, an image of the filled form/workflow, attachments uploaded to the form/workflow, and any, all, or none of the Generated Forms (mapped PDFs) associated with your form/workflow.

Fill in the Send Email wizard with the following information:

• Enter destination email addresses in the To: Reply to: Cc;, Bcc: fields. The email can be sent to multiple addresses separated by a comma or a semicolon. The "To:" email address is required. All other email fields are optional.

  The tenant admin can configure the from email address on the tenant admin's Edit Tenant page. 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 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.

  You can even use the standard internet address convention, for example: From: frevvo Client Services <services@frevvo.com>, so that your emails appear in people's inboxes looking like this:

  

• Customize the email body and Subject text in the Message field. You can use HTML and templates.
• Send the form/workflow 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 email.
• Files 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. 

See Email Integration for further details.

POST data to your web application

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

Fill in the Post Data to your web 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 choices are PDF, PNG and 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 Attachment 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.

Send to Google Drive

The Send to Google Drive wizard steps you through the process of saving your documents to Google Drive.

1. In Google Drive, create a parent folder that will hold all the submissions for this form/workflow.
2. Log into your frevvo tenant as a designer user.
3. Edit your form/workflow and go to the Settings editing mode.
   
4. Click the Document Actions tab. Select Send to Google Drive on the Send Documents tab.
5. In the wizard that appears, enter your credentials (see above for how to get an access token). Note that the email field is optional and intended only to describe which account is associated with the access token. This email does not validate against the token provided.
   
6. Select the parent folder you created earlier in Step 1.

7. For the Submission folder, you may enter a fixed value (not recommended) or use a template. In this case, we have chosen the StudentsName control. For example, if you enter John Adams in the Student Name control, the submission documents will be stored in a subfolder called JohnAdams.

8. Select which documents to send.
   1. Snapshot (PDF, PNG, or JPG)
   2. Data (the submission.xml)
   3. Attachments uploaded by the user
   4. Generated PDF forms - send all, none, or select mapped PDFs.

See Google Connector for full details. 

Send to File System

The Save to Filesystem wizard is used to connect forms/workflows to the frevvo Filesystem Connector. The connector saves submissions in a specified location and can be configured to create metadata files for importing your submissions into a document Management system.

Saving files to a local or remote location is easily done with the Send to File System wizard if generating metadata is not required.

Let's begin with a very simple example. Here are the requirements:

1. You have created a small form that has a Name, Address, City, State and Zip Code fields. A mapped W - 4 PDF is included in the form. The Save PDF property is selected and the PDF Name property is configured with the template {Name}.

2. You want to store the submission files for this form in a directory on your local machine named Submissions. 
3. You want to create a subdirectory for each submission under the Submissions directory. The name of the subdirectory is created from the value entered into the Name field on the form
4. You want to save the form/workflow PDF, any mapped PDFs associated with the form, an xml file and any attachments uploaded to the form in the subdirectory. 

Follow these steps to fulfill the requirements by using the doc action Send to File System wizard

1. 1. Log into your frevvo tenant as a designer user.
   2. Open your form/workflow.
   3. Going the the Settings mode in the Guided Designer navigation toolbar.
      
   4. Click the Document Actions tab. Select Send to File System on the Send Documents tab.

   5. To fulfill the requirements listed above, we only need to fill in the URL, Submission Directory and File sections of the wizard. Here is an explanation of the fields:

      1. The URL: this is the URL to the location where you installed the Filesystem Connector. Be sure to include the /filesystem/submission in the URL after you change the server and port.

         1. In-house: The location of the Filesystem connector is set for the installation using the frevvo.filesystem.connector.url parameter in the <frevvo-home>\tomcat\conf\frevvo-config.properties file. It defaults to http://localhost:8082/filesystem in the tomcat build. The <localhost:8082> in the default URL can be changed to the <server:port> where you installed the Filesystem connector in your environment. This is a required field. The value entered here overrides the value in the frevvo-config.properties file.

         2. Cloud customers will see the placeholder http(s)://host:port/filesystem/submission - enter the https url to the location where you installed your frevvo Filesystem Connector.
      2. Submissions Directory - Enter a relative path from the root directory specified by the connector.file.root.dir parameter in the configuration file created above. Control templates are allowed in this field. You can use a control template to store submissions in subdirectories. The template, {Name}, will populate the Template field. Copy the template from the Template field and add it to the Submissions Directory path after the forward or backward slash. Note the forward or backward slash can be used to create subfolders.
      3. Examples
         1. If the value of the connector.file.root.dir parameter in the configuration file is "c:\" then entering Submissions in the Submission Directory field in the wizard saves the files in the local directory c:\Submissions.
         2. File Section - One or more types of submission content can be specified by checking the Send Snapshot, Files, Gen Forms and Data checkboxes:
            1. Select the snapshot format to be sent by selecting a choice form the Send Snapshot dropdown. The format choices are PDF, PNG or JPEG.
               1. Check the Attachments checkbox to send any file attachments uploaded to the form.
               2. Check the Gen Forms(PDF) checkbox to send the mapped W - 4 PDF.
               3. Check the Data checkbox to send the form XML document for the form.
   6. Save the form.
   7. Create some submissions by testing the form ( Save and Test), filling in the form and clicking submit.
   8. The results of 3 submissions are shown in the image.
      

Refer to the Filesystem Connector chapter for the installation and configuration details plus information about using the Save to File System wizard and generating metadata.

Send to SharePoint

Connecting your forms/workflows to your SharePoint site is easy with the Save to SharePoint wizard. Your tenant must be configured for SharePoint in order for this wizard to display.

Login and Create Form/Workflow

Log in as a frevvo designer user. If you are On Premise frevvoconnecting to Sharepoint in the cloud, use the URL https://<server>:<SSL port>/frevvo/web/login. Example: https://localhost:8443/frevvo/web/login. Port 8443 is the default. Create your form or workflow with controls that capture the data that you want to store in the columns configured in the Lists and Libraries on your SharePoint site.

Configure Send to SharePoint Document Action

1. Go to Settings mode in the Guided Designer navigation bar.
   

2. Click the Document Actions Tab and the Send Documents sub-tab.
   
3. Select the action Send to Sharepoint. If the tenant is not configured for SharePoint, the Send to SharePoint option will not display.
   

   First-time SharePoint Login

   You will be redirected to log in to SharePoint or Office 365 if you are logging into your account for the first time. On successful login, you will be asked to grant or deny access for your frevvo SharePoint add-in.

   
   Click Trust It to authenticate and grant permission to frevvo. You will not see the trust screen on subsequent logins. The wizard will display.
   
   

   • We recommend that you create a separate user in SharePoint for frevvo forms connection, and use that user while configuring the Send to SharePoint wizard in frevvo forms. This frevvo-specific SharePoint user always remains active and eliminates issues if the designer user configured your forms to submit to SharePoint using their own SharePoint login and then leaves the company.
   • If your tenant is configured with the Azure SAML Security Manager, at least one designer user must also be a SharePoint user with the correct privileges to provide consent when invoking the Send to SharePoint wizard 

Set up Route(s)

You can set up a single Document Action to write to two places (i.e. SharePoint Library and List). Route 1 will be automatically expanded. Expand Route 2 to add a second destination if desired.

1. Send Snapshot - Select a format for the Snapshot to be saved in SharePoint. The choices are: PDF, PNG or JPEG. PDF is the default. If you are sending attachments to a Sharepoint List, you must enable attachments on the List.
   

2. The Site URL is automatically prefilled from the SharePoint tenant configuration. This is the SharePoint site or subsite containing the destination e.g. https://frevvo.sharepoint.com. If you use a site and/or subsite, simply add it to the URL, e.g. https://frevvo.sharepoint.com/sites/Docs/docsub1. This URL must use the https protocol. 

3. Pick a Destination. SharePoint destinations can be a Library (and optionally a Folder), or List. Select Library or List from the Destination Type dropdown.

4. Pick a Library or List from the new dropdown that appears. This dropdown shows all the available Libraries or Lists in your SharePoint site.

   1. If you select a Library, you will also see the Folder field. If you want to send to a subfolder, enter the server relative path of the folder within the library. For example, for folder 'test' in library 'mylib', enter /mylib/test.
      
      

      
      

      The folder path may not always match exactly the visible name in the Sharepoint UI. For example, for my Library named 'Documents', the path is actually 'Shared Documents'. You can find the path in the folder's properties.

       Click for detailed steps to capture the correct path for your Sharepoint folder.

      1. Go to your Sharepoint site or subsite, and click on the folder where you plan to save your frevvo documents.
      
      
      2. Click the Info icon (i) in the upper right side to open a properties panel.
      3. Scroll down towards the bottom to the "Path" property. Click the copy icon.
      
      
      4. Paste the copied path into a text pad. Copy everything after the domain name (in my case, /sites/Docs/docsub1/Shared%20Documents/TestFolder) and replace the encrypted character(s) as needed e.g. /sites/Docs/docsub1/Shared Documents/TestFolder

      5. Log in to frevvo, edit your form and go to Document actions.
      6. If using a subsite, make sure the Site URL includes your subsite, e.g. https://frevvo.sharepoint.com/sites/Docs/docsub1
      7. Choose Library, then pick the correct Library from the dropdown. (If you don't automatically see them, try changing "Library" to "List" and back again; this reconnects the SP connector).
      8. In the Folder field, enter the path you copied from Step 4.
      

5. Select a Content Type from the dropdown. The wizard automatically pulls the content type choices from your SharePoint site. The Content Type determines the available metadata column names for mapping. For example, if the destination is a List you would see Item as a choice for the Content Type. This means your submission is saved as a new item on your SharePoint list. Document Libraries show Document as the Content Type.

6. Check the types of files to be saved to the selected destination. The choices are:
   1. Snapshot - include a snapshot of your form/workflow in the format selected in the Send Snapshot field

   2. Data - include the frevvo XML document (only available when sending to a List)

   3. Attachments - include attachments uploaded to your forms/workflows. In Workflows, when Attachments is selected you will see a list of available upload controls and can choose which to include in your Sharepoint submission. 

   4. Gen Forms(PDF) - this checkbox appears if you have mapped PDFs associated with your form/workflow e.g. W-4 and I-9 filled out by a new employee. In Workflows, when Gen Froms(PDF) is selected you will see a list of available PDFs and can choose which to include in your Sharepoint submission. 
      
      
      
      Workflows only:
      

7. Add Metadata. Map the Control Names in your form/workflow to the column names in your SharePoint destination.

   1. Click the  blue add icon to add a row.

   2. The wizard will populate the Column Name dropdown with all the columns in the destination

   3. In the Control Name field, you can type static text (not recommended), select one or more control from your form, or a combination of control(s) and static text. To use a control from your form, type an open curly brace and the first few letters of your control name, i.e. {Fir. A list of controls in your form appears. Select the correct one.

      When mapping Message controls with templates to the SharePoint Connector, the Save Value property should be checked.

      
      

      
      

Mapping Multi-Value Controls

You can map multi-value controls such as controls inside repeats, table columns, and checkboxes to Sharepoint columns. To map to a single value Sharepoint column, you can use any regular separator, such as a comma, in your repeat template syntax. This results in a single, comma-separated string value in the Sharepoint target column. For example, you can map the Items column in a table to a text column named with the syntax {,|Items}. This results in a single value sent to the target Sharepoint column as a comma-separated string, e.g "Widgets, Wingdings, Whatzits".

You can also map a repeat control to a multi-value (checkbox) Choice column. In this case, you must use a special syntax to send separate values that populate the Sharepoint checkboxes. For a Sharepoint list, use the repeat separator 'json'. 

List: {json|Items}

For a Sharepoint library, use the repeat separator ';#'. 

Library: {;#|Items}

These separators send the control values in an array, which populates the checkboxes in the target Choice column.

Clear Route

If you configure a second Route, clicking the Clear Route button removes the information for Route 2 only.

Save and Test

Click thesave and test icon to save the form/workflow and bring up Test mode popup.

Refer to the SharePoint Connector chapter for configuration details and more information on the Send to SharePoint wizard.

Send to External System

You can connect forms/workflows to a frevvo-provided connector that your admin has configured in the Manage Connectors page using the Send to External System doc action. The connectors currently available are the DocuPhase Pro Connector, the Docuware Connector and the DocuShare^® Flex Connector.

Connect a Form/Workflow to DocuPhase Pro 

1. Go to your form/workflow's Settings tab in the Guided Designer Navigation bar.
   
2. Click the Document Actions tab. You will automatically be on the Send Documents sub-tab. Select Send to External System.
   
3. Select DocuPhase Pro from the Select Connector dropdown. The DocuPhase Pro Wizard will open.

4. Select a DocuPhase Pro cabinet from the dropdown.

5. Optionally, select a Tab from the dropdown. Tabs are also known as Document Types in DocuPhase Pro. At this time, only non-indexed document types are available in this list.

6. Optionally, select a workflow that will run when the submission is posted.
7. Add metadata Fields. Click Add to add rows.
   
   1. In the first column, select the name of the target field in your DocuPhase Pro tab. Each time you add a row, only the remaining available fields will display so you cannot accidentally map a field twice. Once all available fields are mapped, the add button is disabled. If you wish to delete a row for any reason, simply click the Delete icon to the right of that row to remove it.

   2. In the second column, add the value you want to send. At least one index field is required. To use a field from your form, type an open curly brace '{' following by the first few letters of the control name. Then, select the control name from the dropdown.

   3. You can optionally select which field to search existing folders by. If none are selected, a new folder will be created. If the folder matching the values is not found, a new folder will be created.

      Repeat Controls

      Multivalue fields like checkboxes and repeats are supported. The recommended approach is to use the template syntax for a comma-separated list, e.g. {,|controlname}. 

8. Select any attachments you would like to send, such as the PDF Snapshot (set by default), the submission xml document, any attachments uploaded by the form user, and any mapped PDFs. 

Save.

Connect a Form/Workflow to Docuware

1. Go to your form/workflow's Settings tab in the Guided Designer Navigation bar.
   
2. Click the Document Actions tab. You will automatically be on the Send Documents sub-tab. Select Send to External System.
   
3. Select Docuware from the Select Connector dropdown. The Docuware Wizard will open.
   
4. Select a File Cabinet. The Wizard will find eligible cabinets based on the connector configuration set by your Tenant Admin.
   
5. Add Fields. Click Add to add rows.
   
   
   1. In the first column, select the target field in your Docuware cabinet. Each time you add a row, only the remaining available fields will display so you cannot accidentally map a field twice. However, after all fields are mapped you can still click the Add button, but no fields will show in the dropdown. In this case, or if you wish to delete a row for any reason, simply click the Delete icon to the right of that row to remove it.
   2. In the second column, the field Type will be automatically set based on your Docuware settings.

   3. In the third column, add the value you want to send. To use a field from your form, type an open curly brace '{' following by the first few letters of the control name. Then, select the control name from the dropdown.
      
      
      

      Repeat Controls

      To map values from repeating controls to the Keywords field type, the value should be a template string that resolves to multiple values. The recommended approach is to create a template that results in a JSON array using the built-in separator 'json' i.e. {json|controlname}. This special separator resolves to JSON format. The same result can be accomplished by specifying the JSON format i.e. ["{","|controlname}"]. 

6. Select any attachments you would like to send, such as the PDF Snapshot (set by default), the submission xml document, any attachments uploaded by the form user, and any mapped PDFs.
   

Save.

Connect a Form/Workflow to DocuShare^® Flex

1. Go to your form/workflow's Settings tab in the Guided Designer Navigation bar.
   
2. Click the Document Actions tab. You will automatically be on the Send Documents sub-tab. Select Send to External System.
   
3. Select DocuShare^® Flex from the Select Connector dropdown. The DocuShare^® Flex Wizard will open.

4. Enter the name of a DS Folder (this can be a path). If the folder(s) already exist they are used, otherwise they are created.

5. Select the Document Type from the dropdown.

6. Add metadata Fields. Click Add to add rows.
   
   1. In the first column, select the target field in your DocuShare^® Flex folder. Each time you add a row, only the remaining available fields will display so you cannot accidentally map a field twice. However, after all fields are mapped you can still click the Add button, but no fields will show in the dropdown. In this case, or if you wish to delete a row for any reason, simply click the Delete icon to the right of that row to remove it.
   2. In the second column, the field Type will be automatically set based on your DocuShare^® Flex settings.

   3. In the third column, add the value you want to send. To use a field from your form, type an open curly brace '{' following by the first few letters of the control name. Then, select the control name from the dropdown.

      Repeat Controls

      To map values from repeating controls to the Keywords field type, the value should be a template string that resolves to multiple values. The recommended approach is to create a template that results in a JSON array using the built-in separator 'json' i.e. {json|controlname}. This special separator resolves to JSON format. The same result can be accomplished by specifying the JSON format i.e. ["{","|controlname}"]. 

7. Select any attachments you would like to send, such as the PDF Snapshot (set by default), the submission xml document, any attachments uploaded by the form user, and any mapped PDFs. The filename needs to be unique within the destination folder.

Save.

Send Data

Using these wizards you can:

• Do Nothing
• Post submissions to a Google Spreadsheet
• Manually set document URIs - to connect to database and other back-end systems

The Send Data wizards enable you to manually set a URI to which the data will be sent when your form is submitted.

Do nothing

This is the default option. Selecting Do nothing will also clear the other options if they are set.

Post Submissions to a Google Sheet

frevvo supports direct connectivity with Google Spreadsheets. This wizard allows you to save submissions directly into Google Spreadsheets. It also provides additional assistance in setting up the login to your Google account and in selecting the spreadsheet.

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.

1. Edit your form/workflow
2. Go to the Settings mode in the Guided Designer navigation bar.
   
3. Click on the Document Actions tab, then click the Send Data tab.
4. Check Post Submissions to a Google Spreadsheet.
   
   
5. This launches the Google Sheet Wizard.
6. Enter your Oauth token (from Step 1). Note that the email field is optional and intended only to describe which account is associated with the access token. This email does not validate against the token provided.
7. A Spreadsheet dropdown appears listing all the spreadsheets in your Google account
8. Select the Google Sheet from the list. 
9. Select the worksheet of your Google Sheet from the dropdown.

10. Click Submit.
    
    

11. That’s it. When the form is submitted, the data will be saved to the selected Google Sheet.  

See the frevvo Save your Submissions to a Google Sheet for details.

Manually set document URIs

After you have generated controls from the elements in your database schema, set your form’s Document URI to the database connector query URL. Follow these steps:

1. Click the Settings mode.
   
2. Click the Document Actions tab. Click Send Data then select Manually set document URIs.
   

The first section in the wizard is for the form's default document. This is indicated by the Document Name of "default" displayed in the wizard. The default document maps to all of the controls you added to this form by dragging and dropping from the palette. This is typically not the document you want to configure.

• The second section is for the next schema document. You should see the Document name change to your schema's document name. 

The next screen has two sections: Read URI and Write URI. Typically, when the form loads, frevvo customers read form data from their database to initialize the form and send the updated XML document to the same database upon form submission. Enter the same URI in the Read URI and the Write URI fields, as shown in the image, with the appropriate SQL statement to run if you are reading from and writing to the same database using the database connector. It is possible to read the form initialization data from one database and then update a different database. Enter different URIs in the Read URI and the Write URI fields if this is your situation.

• Enter the database connector Url to your query in the wizard's URL input. If the database connector is running in the same host and port as the frevvo form server, then you can omit http://<host>:<port>/ from the URL. Use templates to create dynamic URLs. See this example below.
  

You also must specify which of the four SQL statements to run—you do this by choosing the appropriate values in the Document URI Read Method and Document URI Write Method dropdowns according to the table below. (You may notice in the Forms Designer that the Document URI Read Method drop down box includes a POST option, but it is not shown below because it is not used by the database connector.)

You’ll see one set of Document URI properties for each schema in your form. Type the Document URI next to the schema name—make sure not to type it next to the Default schema. To specify which of the four SQL statements to run, choose the appropriate values in the Read Method and Write Method dropdowns, based on the information below. 

• Read Method - Choose GET if your form will be initialized with data from your database; leave the dropdown blank if it won’t. (Don’t set the Read Method to POST; this is used for integrating forms with different back ends.) 
• Write Method - If your form is read-only, leave this blank. Otherwise, use the chart above chose either PUT or POST. PUT maps to the update method while POST maps to create.

Note that you may choose only one Write Method in the Forms Designer.

See  the chapter on connecting to your database for all the details.

Additional Email Wizard

When the form is submitted, frevvo can send an additional email message with optional XML document(s) , an image of the filled form, attachments and Pixel Perfect PDFs (referred to as Generated Forms), 

Slide the toggle to the right to turn on the Additional Email wizard.

The email can be sent to multiple comma separated email addresses. The "To:" email address is required. All other properties are optional.

• Enter destination email addresses in the To: Reply to: Cc;, Bcc: fields. The email can be sent to multiple addresses separated by a comma or a semicolon. The "To:" email address is required. All other email fields are optional.

• Customize the email body and Subject text in the Message field. You can use HTML and templates.
• 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 email.
• Files 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 Gen PDF Forms control:

  • Check All to send all the Pixel Perfect PDFs. This is the default value.

  • Check None to send none of the PDFs.

  • Check Select to display a list of all the PDFs associated with your form/workflow. Click the ones you want to be part of the submission.  

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. The email to the employee will contain whatever documents are selected on the Additional Email wizard screen.

To use the wizard, click the Doc Actions section in the left toolbar and select the Additional Email Tab. See Email Integration for further details on configuring the content of the email.

How to set up Multiple Document Actions

It is important to remember that doc action wizards are single select by design. The Additional Email wizard can be used to send an email if you are configuring more than one doc action on a form/workflow. 

Let's say you have a workflow where you want to

1. Save a copy of the form to Google Drive
2. Email a copy of workflow pdf to the IT department

Set up the Save to Google wizard. Then use the Form and Doc Actions#AdditionalEmail tab to configure the email to the IT department.

Using Templates in Form and Doc Actions

The values/entries in all doc action/doc URI wizards can be customized with data entered in the form/workflow 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 by clicking the  down arrow on the right side of the field.
• 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,  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 as documented above when used in Doc and Error Action Wizards.

Form & Doc Action Failure Notifications

An email notification is sent to all tenant administrators or the workflow administrator(s) (if configured) when a Form Action post, DOC URI or DOC Action fails and the submission does not reach it's intended destination. When the form/workflow is submitted, the user sees the message "Thank You! Your submission has been received." and then the appropriate admin is notified via email. The email is sent when the following Form/Doc actions are configured in a form/workflow:

• Form Action
  • Form and Doc Actions#PostDataandforwarduserstoyourwebpage
• Doc Action
  
  • Form and Doc Actions#SendtoGoogleDrive
  • Form and Doc Actions#SendtoFileSystem
  • Form and Doc Actions#SendtoSharePoint

  • Form and Doc Actions#ManuallysetdocumentURIs

This is not applicable to the email doc action since it is asynchronous and the notification would fail if the service were unavailable. Refer to each topic for more information.