...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
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
- Download the SharePoint Connector. Rename it to sharepoint.war. Copy it to the <frevvo-home>\tomcat\webapps folder
- Configure SharePoint for your Live Forms 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.
- 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
...
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
...
Login to as the tenant admin
Click the Edit Tenant link.
- Click the blue arrow to expand the SharePoint section.
Enter the Connector URL. - This URL is needed if you are using in the cloud and installing the connector locally. Enter the URL where your installation that is configured for SharePoint is located. This URL must use the https protocol.
The URL in the Connector URL field will override the connector URL that is specified in the configuration property in the <frevvo-home>\tomcat\conf\frevvo-config.properties file. In some cases you can leave this field blank.
Info The default value is shown below:
frevvo.sharepoint.connector.url=http://localhost:8082/sharepointEnter the Client Id and the Client Secret that you saved in Step 1 into the respective fields.
- Enter the SharePoint Domain Name e.g. <Your SharePoint tenant name>.sharepoint.com - there is a dot between the SharePoint tenant name and sharepoint.com
- To determine the realm for your SharePoint site :
Navigate to https://<tenant>.sharepoint.com/_layouts/appprincipals.aspx - change the <tenant> to the name of your SharePoint tenant - e.g. https://frevvo.sharepoint.com/_layouts/appprincipals.aspx
Find your registered application in the list and and look at the App Identifier column. The unique identifier after the @-sign in the App Identifier is the app realm and must be entered in the Realm field.
- Click Submit
- Browse http://<your server:port>/sharepoint/health (replace <your server:port> with your frevvo server:port) to check the status of the connector. If the connector is up and running, you will see { "status" : "UP" }.
- Proceed to Connect Forms/Workflows with the Save to SharePoint wizard
Step 3 - Connect Forms and Workflows with the SharePoint wizard
...
Excerpt | ||
---|---|---|
|
...
|
Special Characters in Filenames
...
- If you leave the PDF Name property blank, Live Forms uses the workflow/form name as the pdf file name. The PDF will not post to SharePoint generating an HTTP 500 403 status error if the Form Name contains special characters. To avoid any issues, name your form/workflows using characters that are suitable for filenames and explicitly set the pdf name in the form/workflow 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.standard. Following the POSIX filename standard (A–Z a–z 0–9 . _ - ) will ensure it works.
- The special characters listed below in filenames will cause the submission to be flagged with an error in the submission table. This can happen if you do not set a PDF filename and it defaults to the form/workflow name if that name has special characters.
Section | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Check Submissions on SharePoint
...
At least one designer user that is going to be connecting forms/workflows 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.
...
- Browse http://<your server:port>/sharepoint/info - the version information is returned as shown in the image.
...