| Section | ||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Database Connector
The Database Connector makes it very easy to connect to most databases. You can save form submissions in your database or initialize forms from a database. Note that this connector uses XML schema.
...
Google Connector
Connecting your Live Forms frevvo to Google sheets and drive is very easy to do with the frevvo Google Connector. See the Google Connector chapter for help installing and using this connector.
Confluence Add-on
The Live Forms frevvo Add-on for Confluence is available as an add-on to either ' Online service or In-house installations. You need to install it into Confluence before you can add forms and submissions pages to Confluence. You will also need to download and install Live Forms frevvo for Confluence.
See Live Forms frevvo ™ for Confluence documentation for help installing and using this plugin.
PaperVision® / ImageSilo® Connector
Live Forms frevvo supports form submissions sent directly into Digitech Systems PaperVision® and ImageSilo® document management products.
...
The Filesystem Connector saves submissions to a local or remote filesystem or an Enterprise Content Management system (ECM). See Filesystem Connector for easy installation and configuration information.
Box Connector
Save your submission data from an automated frevvo form or workflow to your box account using the box connector. Refer to the /wiki/spaces/frevvo90/pages/1063683756to see how easy it is to connect your forms and flows to the Box Content Management Platform.
SharePoint Connector
Store documents and information to a secure Microsoft SharePoint website. Configure the frevvo SharePoint Connector for your tenant then use the SharePoint wizard to connect your forms/flows to the SharePoint website for document storage. . Refer to the SharePoint Connector topic for the details.
Connector Security
connectors installed on-premise should only be accessible to the server and should not be remotely accessible. recommends only allowing HTTPS access to the server (not external HTTP access). Since the connector(s) is not exposed over HTTPS, remote code execution vulnerability can be mitigated (a remote attacker cannot exploit this vulnerability as it is not exposed).
If you choose to allow external access to HTTP, you should only allow requests with paths starting with /frevvo for port 8082 (or the port you are using for frevvo and the Connector(s)).
See also Database Connector Security.