Installation 

The information on this page refers to the Google Connector v1.4. Click here for the details about Google Connector v2.0.

Installation 

If you are using  In-house and have downloaded the Google Connector:

1.  rename the download file named connector-google-apps.zip to google.war
2.  copy google.war to c:\frevvo\<frevvo-home>\tomcat\webapps
3. If you are using the tomcat-bundle, the google.war file is located in <frevvo-home>/ext/connectors. Copy the war file from this location to c:\<frevvo-home>\tomcat\webapps.

Tomcat will automatically expand the war file and start the connector running. If you are not using the frevvo the  tomcat-bundle or have not installed the bundle into c:\frevvo make the necessary path adjustments to step 2 above.  

Google Spreadsheets Spreadsheets

 forms can both write to and read from your Google spreadsheets.

...

 provides wizards and a Google Connector that support easy direct connectivity with Google Spreadsheets. You'll need a Google Docs account and a frevvo account account.

To save submissions to your Google spreadsheet, edit your form and use the Doc Action Wizard to configure your form to save your submissions into a Google spreadsheet. Each time someone uses and submits your form, a new row is added to your Google spreadsheet.

...

If your form contains multiple documents because one or more controls are from the palette while other controls are from one or more XSD data sources, you can write each document to a different Google Spreadsheet. To do this use the Google Connector Url Manual Doc URI wizard to configure each Uri to a different spreadsheet or workbook within the spreadsheet. 

...

Read from a Spreadsheet 

 forms can be initialized with data from a Google Spreadsheet by retrieving data from the Google Spreadsheet via a business rule. This form allows the user to select a customer from the dropdown. Once selected a business rule retrieves the address details from a Google Spreadsheet.

...

And the following Url parameters:

•  media=jason json - This must be set as shown
•  query=<query string> - This is where you specify which rows to match based on the data in your spreadsheet.

...

You can test your queries directly in the web browser. Note that characters such as the equals and double quotes must be URL encoded as shown in the examples below where you see %22 for quote and %3D for = 

http://www.frevvo.com/google/spreadsheets/query/u/<user>/p/<password>
    /s/DisclosureAddresses/w/ByName?media=json&query=name%3DHMF

http://www.frevvo.com/google/spreadsheets/query/u/<user>/p/<password>
    /s/DisclosureAddresses/w/ByName?media=json
    &query=name%3D%22AAA Insurance%22

Update Spreadsheet Cells Cells

In addition to retrieving rows from a Google spreadsheet and adding rows to a spreadsheet, you can also update an data in an existing row. See the business rule example Sequential Numbers.

...

And the following Url parameters:

•  media=jason json - This must be set as shown
•  query=<query string> - This is where you specify which rows to match based on the data in your spreadsheet.
•  update=<update string> - This is where you specify which cell(s) to update in the matched row(s)
•  method=put - A hard coded Url parameter that must exist in the Url string

...

Form submissions can be saved to your Google Apps Premier account. Note that Google Apps for Education account are currently not supported.

The first step is to create a Collection (effectively a folder) in your Google Apps account. This will be the location where your form submissions will be stored. For example, create a Collection called Leave Approvals. 

Use the Google Documents wizard

...

1. Click the Doc Action button in the toolbar at the top of the form.
2. In the wizard that pops up, select the Save to Google Documents button.
3. Enter your login credentials.
4. After your login has succeeded, the wizard will show the list of Folders (Collections) availableshow the list of Folders (Collections) available. Sub-folders are not listed in the folder list.
5. Select the collection you created earlier (Leave Approvals).
6. Choose a name for the Submission Folder. This name should be unique for each submission. The best approach is to choose a combination of controls in the form that will generate a unique name. For example, if your form contains controls named EFulName and StartDate for employee's full name and start date of the leave, then choose: {EFullName}_{StartDate}.
7. Click the Finish button.
8. Your form is now configured to save submissions to your Google Apps account. 

...

...

...

Image Removed

...

The Google Documents Connector can be used to format emailed form submissions and to echo a formated document back to the page that submitted the form. Here is a sample email formated using the Google Document template [[#Google_Document_Template_Syntax|template shown below]].

To use the Google Connector, edit your form and use the Form Action Wizard to echo a formatted document back to the page and/or use Doc Action Wizard to format an email message.

Google Document Template Syntax

This feature is currently in alpha release. The syntax may change. The Google Document Connector uses a template syntax to insert values from a submitted form into the document. The syntax is ${form.[Name]}. Where [Name] is the name you gave to the particular form field in the frevvo Form  Form Designer. Read more about naming form fields.

Here is a Google document using the template syntax:

Repeats

Repeat controls have a special syntax. Assume that your form contains a repeating section named Expense. First you must add a Repeat As tag to the document. ${repeat form.[Name] as [alias]}. For example: ${repeat form.Expense as exp}. Then use the alias to reference the controls inside the repeat. The Connector's template processor will add a row to the table for each repeating item in the form submission.

Sections

Form controls nested inside sections must be referenced using a nesting notation. If two text controls named Firstname and LastName are nested inside of a section named PersonalInfo then the templates in your google document must be written as:

...

${form.MedicalHistory.PersonalInfo.FirstName} ${form.MedicalHistory.PersonalInfo.LastName}

Limitations

...

Google Connector Known Issues

...