Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Section
Column

The Google Connector 2.0 and 2.1 support Oauth2 - Open Standard for authorization. This requires the account holder to provide consent to the Google connector to access data on their behalf. This is a manual process and must be done for each Google account associated with the connector.

Cloud customers using the Google Connector for the first time will need to:

New in-house customers using the Google Connector for the first time will need to:

Existing in-house customers upgrading from a previous version of the Google Connector will need to:

Column
width350px

On this page:

Table of Contents
maxLevel2

...

  1. Make sure the version of  is compatible with the version of the Google Connector you are installing. View the compatibility matrix to check the versions. If you are not using the correct version of , first upgrade your

     server software.  

  2. Stop '.

  3. If you are using the tomcat-bundle, 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. 

  4. If you need to download the connector separately, click  here  . Extract the google.war file to the <frevvo-home>/tomcat/webapps/ folder. 

    Note

    If you are currently using a previous version of the Google Connector and you want to upgrade to version 2.1, follow these steps if you are using the Tomcat bundle:

    1. Stop

    2. Download the frevvo Google Connector.

    3. Extract the google.war file to replace the existing one in <frevvo-home>\tomcat\webapps.

    4. Delete the <frevvo-home>\tomcat\webapps\google directory. If this directory is not deleted then the Google Connector will run from the old directory and the newer version won't take effect.

    5. Continue with step 5.

  5. If you are running  on your local machine, you must set a domain name for your machine - otherwise you can skip this step. 

    1. Ex: For Windows edit the C:\WINDOWS\system32\drivers\etc\hosts file as an administrator and modify the 127.0.0.1 entry with a domain name:  

      Code Block
      127.0.0.1 example.com
  6. Go to https://console.developers.google.com. Login to the google account that you are going to use with the Google connector.

  7. Create a new project – name it , you can modify the id if you like, check I agree then click Create. You will see activity window while its creating the project When complete, you should be on the project dashboard page.
  8. Click  APIs and Auth → APIs → enable the Google Drive API named Drive API. It is listed under the Google Apps APIs label. It will move to the top section of the page  when you turn it on.
  9. Click Consent screen. Select the email address you want to associate with this project. Provide a project name. Click Save.
  10. Go to Credentials → OAuth → Create new client ID
    1. The Consent screen must contain a product name and email address before continuing.
    2. Application Type = Web Application
    3. Authorized Javascript Origins = Empty
    4. Authorized Redirect URIs = http://<DOMAIN_NAME>/google/credential. Replace <DOMAIN_NAME> with your domain name. If you are using localhost, this name must match the entry in your hosts file and you must provide the port number.
    5. Click Create Client ID.
  11. Click the Download JSON file.
    1. Rename the JSON file as client_secrets.json
    2. Copy it to tomcat/lib folder
  12. Start . Don't forget to  start the Insight server first if you are using the Report feature.
  13. Paste this url in your browser: http://<DOMAIN_ NAME>/google/health to check the Google Connector status. Provide your domain name and the port number if you are running locally. You should see a {"status":"UP"} message.

...

Obtaining an Access Token

Form designers must obtain a Google access token for every Google account you wish to use with your forms/flows. So for example if you connect your forms/flows to a Google account info@frevvo.com and support@frevvo.com, you will need to obtain two access tokens.

Follow these steps to use the frevvo Google connector consent UI to obtain an access token for each Google Account.

...

Open your web browser and login to your Google Account

...

Go to:

  1. Live Forms Online Cloud customers: https://app.frevvo.com/google/consent

  2. Live Forms In-house customers: http://<your frevvo server domain name>/google/consent

...

Click on the Accept button

...

Note

An access token generated for a in-house installation running the Google connector, will not work with the Google connector running in the frevvo cloud. You must generate a separate token for each environment.

    

...

Refer to the migration topic for the next step. 

...

Insert excerpt
frevvo71:Obtain an Access Token
frevvo71:Obtain an Access Token
nopaneltrue

Connecting Forms/Flows to Google Sheets & Drive

...

 business rules are used to retrieve and update data in Google sheets via the Google Connector. Passing user names, passwords, sheet and worksheet names as part of a URL in  rules has been deprecated . This method will not work when the sheet or worksheet name contain certain special characters.  

...