Versions Compared

Old Version 47

changes.mady.by.user Former user

Saved on

compared with

New Version 48

changes.mady.by.user Former user

Saved on

Key

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

 

The frevvo SharePoint Connector and wizard, make it easy to create forms and approval workflows that validate information, route for signatures as required and save the data and documents to a secure SharePoint website.

The Connector was designed to integrate with Office 365 SharePoint online. It will also work with SharePoint On-premise.

All customers need a valid Office 365 SharePoint account.

Submissions can contain multiple files of different types - Invoice, Receipt, PO etc. You may want to save these files in different locations on your SharePoint site.

The SharePoint Connector wizard, allows you to:

  1. Save the form/flow data and metadata to a SharePoint destination. The destination could be a folder in a document library and/or a list item.
  2. Designers select the SharePoint destination from a dropdown
  3. Map form/flow control values to the SharePoint columns.
  4. Configure two destinations for your data.

The SharePoint wizard guides you through connecting your forms/flows to SharePoint.

Column
width300px

On This Page:

Table of Contents
maxLevel2

...

  1. Cloud Customers Connecting to SharePoint Online - This configuration had been certified by frevvo. Follow these steps:
    1. Configure Live Forms as a SharePoint Add-in
    2. Configure SharePoint for your Live Forms tenant.
    3. Connect your Forms/Flows using the SharePoint wizard.

  2. In-house Customers connecting to SharePoint Online - This configuration scenario has been certified by frevvo. Follow these steps:
    1. Configure Live Forms as a SharePoint Add-in
    2. Configure SharePoint for your Live Forms tenant
    3. Download the SharePoint Connector. Rename it to sharepoint.war. Copy it to the <frevvo-home>\tomcat\webapps folder
    4. Connect your Forms/Flows using the SharePoint wizard.

  3. In-house customers using SharePoint On-premise - this configuration is supported but not certified.
    1. Customers using SharePoint On-premise also need an Office 365 SharePoint Online account. This is necessary to obtain an authorization token. There is no data transfer from the SharePoint On-premise to SharePoint Online.
    2. Customers are responsible for configuring the On-premise installation and the integration with SharePoint Online.
    3. The On-premise version of SharePoint must be version 2013+.
    4. Refer to this Microsoft website for information about how to use Office 365 to allow  to authenticate.

  4. Live Forms Cloud customers connecting to SharePoint On-premise - This configuration is supported but considered unlikely as SharePoint On-premise as it requires your On-premise SharePoint to be exposed to the Cloud.
    1. Customers are responsible for configuring the On-premise installation and it's exposure to the Cloud. 

Configuring the SharePoint Connector

...

  1. Test your form/flow by filling in data, adding attachments, and submiting/completing it.
  2. Login to your SharePoint account and navigate to the specified destination. The image shows submissions saved to a SharePoint list named Demo List and the John Edwards submission data and attachments.

Troubleshooting

SharePoint Connector Logfile

If you are using the frevvo tomcat bundle, the SharePoint Connector log is located in <frevvo-home>\tomcat\logs. The logfile is named sharepoint-connector.YYYY-MM-DD.log. Generating separate logfiles make it much easier to search for errors when troubleshooting connector issues. The connector is designed to use the frevvo-config.properties file.

The SharePoint connector logfile defaults to INFO loglevel. To configure DEBUG level logging for the Google connector log:

  1. Stop
  2. Create/edit a frevvo-config.properties file in <frevvo-home>\tomcat\conf
  3. Add the logging.level.com.frevvo.connectors.sp=DEBUG property to the file. NOTE: the syntax of the property is logging(dot)level(dot)com(dot)frevvo(dot)connectors(dot)<connector name>=DEBUG
  4. Save the file
  5. Restart

Code Block
logging.level.com.frevvo.connector.sp=DEBUG

Doc Post Failure

If the submission doesn't reach your SharePoint website - if does not receive a response back from SharePoint with a status code of 200, you can find information about the error from the submission table.

...