Section | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
- 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 as a SharePoint Add-in
- Configure SharePoint for your Live Forms tenant
- Install the SharePoint Connector.
Connect your Forms/Flows using the SharePoint wizard.
Warning Prerequisites for this configuration:
Tip When configuring a test tenant for the SharePoint Connector, use the frevvo.certificate.signature property to bypass SSL Security. Do not do this for a Production tenant.
- 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 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
...
If your environment includes an in-house server, you must install the SharePoint Connector in the tomcat bundle on this machine. Cloud customers can skip this step.
- Stop
- Download the SharePoint Connector.
- Unzip the SharePoint Connector zipfile to a temporary location.
- Extract the sharepoint.war file to <frevvo-home>//tomcat/webapps directory on your server.
- Start .
...
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 Live Forms Tenant for SharePoint
...
Click Trust It to authenticate and grant permission to . You will not see the trust screen on subsequent logins. The wizard will display.
Tip |
---|
|
...
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
The SharePoint Connector generates it's own logfile. Typically, the log is first place to look for information when an issue is encountered. Information about the logfile and some common issues with solutions are listed below.
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 see DEBUG level messages in the SharePoint Connector log:
...
Code Block |
---|
logging.level.com.frevvo.connector=DEBUG
logging.level.com.frevvo.connectors=DEBUG |
Generate the SharePoint Connector log in JSON format
...
Code Block |
---|
spring.profiles.include=logging-json |
Doc Post Failure
If the submission doesnSome 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.
...
- Browse http://<your server:port>/sharepoint/info - the version information is returned as shown in the image.
...