Section | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Column | |||||||||||
Section | |||||||||||
|
...
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 Live Forms 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 Live Forms frevvo tenant
- Connect your Forms/Flows 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.
- Live Forms 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
These instructions assume you are a frevvo Cloud customer or have an in-house installation of up and running using the frevvo Tomcat bundle. Follow these steps:
Step 1 - Configure
...
frevvo as a SharePoint App/Add-in
must be added as a SharePoint provider hosted add-in by your global Office 365 tenant SharePoint Administrator. The process is described in Steps 1 and 2 on this Microsoft SharePoint website. Copy the Client Id and client Secret and save them somewhere on your desktop. You will need to add these values when configuring your tenant for SharePoint.
...
Code Block |
---|
<AppPermissionRequests AllowAppOnlyPolicy="true"> <AppPermissionRequest Scope="http://sharepoint/content/tenant" Right="Manage" /> </AppPermissionRequestsAppPermissionRequests> |
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
Cloud and in-house customers must configure their tenant to connect to SharePoint as a client. frevvo expects that customers will only be integrating with one SharePoint instance for their organization. You will need the SharePoint Client Id and the Client Secret from Step 1.
...
Excerpt | ||||
---|---|---|---|---|
|
...
- If you leave the PDF Name property blank, Live Forms frevvo uses the flow/form name as the pdf file name. The PDF will not post to SharePoint generating an HTTP 403 status error if the Form Name contains special characters. To avoid any issues, name your form/flows using characters that are suitable for filenames and explicitly set the pdf name in the form/flow using the same standard. Following the POSIX filename standard (A–Z a–z 0–9 . _ - ) will ensure it works.
- Special characters in filenames will cause the submission to be flagged with an error in the submission table. We recommend POSIX naming standards as there are some special characters that are not supported by the connector.
...
Section | |||||||
---|---|---|---|---|---|---|---|
|
Check Submissions on SharePoint
When the form is submitted or the flow is completed, submission data, metadata and attachments are uploaded to the specified destination in your SharePoint account
Verify your stored submissions on your SharePoint website:
- Test your form/flow by filling in data, adding attachments, and submiting/completing it.
- 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.
Using the SharePoint Connector in an Azure SAML Security Manager tenant
At least one designer user that is going to be connecting forms/flows to SharePoint with the Save to SharePoint wizard must also be a SharePoint user with the correct privileges to provide consent if your tenant is configured with the Azure SAML Security Manager.
Troubleshooting
Some common issues with solutions are listed below.
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.
All tenant admin(s) in your tenant or flow admin(s) configured for specific workflows will receive a Doc Post Failure notification email to alert them that an issue has occurred. The <server-name> will be provided in the email subject.
Max file size
The maximum size for all fevvo connectors is set to unlimited. Any size file can be uploaded to and posted to SharePoint.
Determine the version of the SharePoint Connector you are using:
To determine the version of the SharePoint connector you are using:
...
|
Check Submissions on SharePoint
When the form is submitted or the flow is completed, submission data, metadata and attachments are uploaded to the specified destination in your SharePoint account
Verify your stored submissions on your SharePoint website:
- Test your form/flow by filling in data, adding attachments, and submiting/completing it.
- 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.
Using the SharePoint Connector in an Azure SAML Security Manager tenant
At least one designer user that is going to be connecting forms/flows to SharePoint with the Save to SharePoint wizard must also be a SharePoint user with the correct privileges to provide consent if your tenant is configured with the Azure SAML Security Manager.
Troubleshooting
Some common issues with solutions are listed below.
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.
All tenant admin(s) in your tenant or flow admin(s) configured for specific workflows will receive a Doc Post Failure notification email to alert them that an issue has occurred. The <server-name> will be provided in the email subject.
Max file size
The maximum size for all fevvo connectors is set to unlimited. Any size file can be uploaded to and posted to SharePoint.
Determine the version of the SharePoint Connector you are using:
To determine the version of the SharePoint connector you are using:
- Browse http://<your server:port>/sharepoint/info - the version information is returned as shown in the image.
Refresh Token Expired
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.