...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
The frevvo SharePoint Connector and Save to Sharepoint document action 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.
Warning |
---|
To use the Sharepoint Connector, 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 Save the form/workflow data and metadata to a SharePoint destination. The destination could be a folder in a document library and/or a list item.
...
With point and click tools, designers can select the SharePoint destination
...
and map form/workflow control values to the SharePoint
...
metadata columns.
The SharePoint wizard guides you through connecting your forms/workflows to SharePoint.
...
width | 300px |
---|
On This Page:
...
frevvo - SharePoint Configuration Scenarios
- Cloud Customers Connecting to SharePoint Online - This configuration had been certified by frevvo. Follow these steps:
In-house Customers connecting to SharePoint Online - This configuration has been certified by frevvo. Follow these steps:
Info frevvo only supports/certifies the SharePoint Connector running in the Apache Tomcat container.
- Configure frevvo as a SharePoint Add-in
- Download the SharePoint Connector. Rename it to sharepoint.war. Copy it to the <frevvo-home>\tomcat\webapps folder
- Configure SharePoint for your frevvo tenant
- Connect your Forms/Workflows using the SharePoint wizard.
- In-house customers using SharePoint On-premise - this configuration is supported but not certified.
- 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.
- Customers are responsible for configuring the On-premise installation and the integration with SharePoint Online.
- The On-premise version of SharePoint must be version 2013+.
- Refer to this Microsoft website for information about how to use Office 365 to allow to authenticate.
- frevvo Cloud customers connecting to SharePoint On-premise - This configuration is supported but considered unlikely as SharePoint On-premise requires your On-premise SharePoint to be exposed to the Cloud.
- Customers are responsible for configuring the On-premise installation and it's exposure to the Cloud.
- Customers are responsible for configuring the On-premise installation and it's exposure to the Cloud.
Configuring the SharePoint Connector
...
Remember SharePoint only allows https.
Tip |
---|
We recommend that you create a separate user in SharePoint for frevvo forms connection, and use that user while configuring the Save 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. |
Step 2 - Configure the frevvo Tenant for SharePoint
...
Excerpt | ||||
---|---|---|---|---|
|
...
If your users see an error like "org.springframework.security.oauth2.client.resource.UserRedirectRequiredException: A redirect is required to get the users approval" when accessing or trying to submit a form, the cause is that your Sharepoint Token has expired. The user who owns the Sharepoint Account (usually the designer) will need to login and provide consent to refresh the token. You can learn more in this Microsoft Documentation. Currently frevvo does not provide a way to generate a new refresh token automatically. This feature may be added in a future release. However, until then the Sharepoint account user will have to provide consent for a fresh token every 6 months.