Saving submission data from an automated frevvo form or workflow to your box.com account, is easily done with the Box connector and the Save to box.com wizard. Once the connector is installed (in-house) and configured, simply run the Save to box.com wizard to connect your form/flow to box. Submissions from are posted to the Box Connector using the Doc Action Save to box.com wizard.

You can also choose which documents get saved including generated files e.g. a Government W-4 for an Employee On-Boarding workflow.

When the form or flow is submitted, the selected documents, such as Student Registrations, Purchase Orders, mapped PDFS like a W-4, Patient Referrals etc, are uploaded to your box account to the specified folder. Once in box, you can use all their features to collaborate, share and manage the documents.

Signatures are not saved as they are a different content type than attachments.

The Box Connector is available for cloud and in-house customers. All customers will need a valid Box account.

frevvo only supports/certifies the Box Connector running in the Apache Tomcat container.

In-house customers must perform a few additional configuration steps as described below

On This Page:

Installing the Box Connector

Cloud Customers

If you use the Live Forms Cloud hosted server, the connector is already installed and configured. You can immediately begin to Connect your Forms/Flows using the Save to Box.com wizard.

In-house Customers using the frevvo Tomcat bundle

The Box connector can be installed behind your firewall where it can connect to your back end system in order to read/write data. These instructions assume you have an in-house installation of up and running and you are using the frevvo Tomcat bundle:

To install the Box connector in the same tomcat as :

Stop .
Download the box connector zipflile from here.
Extract the box.war file to your <frevvo-home>\tomcat\webapps directory.
Create a Box.com Application for Live Forms
Configure the Box Connector - (In-house only)

Create a Box.com Application for Live Forms

You must create a content API application for . A tutorial that will walk you through the basics is available on this website.

Click here for information specific to the box application for Live Forms

Follow these steps;

Navigate to https://developer.box.com/ and signup for an account.
Navigate to the same link and login. Click Getting Started on the My Applications screen.
You are prompted to create an box application. Give the application a unique name (name has to be unique across entire ecosystem of developer applications (both private and public)).
On the General Information section of the screen, the application name and support email will be prefilled. Verify that the Content API Access Only button is checked.
On the OAuth2 Parameters section of the screen,
1. Copy the client_id and save it somewhere. You will need this to configure the frevvo.xml file in .
2. Copy the client_secret and save it somewhere. You will need this to configure the frevvo.xml file in .
3. Enter the base uri for your installation in the redirect_uri field. Change the <your server name> and <port #> shown in the image to your information:
4. Verify that Read and Write all files and folders stored in box is checked in the Scope section. This is the only scope required by .
Save the box application.

Configure the Box connector (in-house only)

The Box connector is configured using context parameters in the file, frevvo.xml.

Follow these steps:

Navigate to <frevvo-home>\frevvo\tomcat\conf\Catalina\localhost directory.
Edit the frevvo.xml file.
Locate the Box Connector section of the file.
Add the client id that you copied and saved earlier as the value of the frevvo.box.connector.client.id parameter. Paste the client id for the box application that you created for in between the quotes.
Add the client secret that you copied and saved earlier as the value of the frevvo.box.connector.client.secret parameter. Paste the client secret for the box application that you created for in between the quotes.
Save the changes to the frevvo.xml file.
Start . If you are running v7.1+, remember to start the Insight server first.
Browse http://<your server:port>/box/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/Flows with the Save to Box.com wizard

Connect Forms and Flows with the Save to Box.com wizard

Login to your box account and create a folder for your form/flow. Let's say you have an Employee On-boarding workflow and you want to store all of the submissions in a folder named Employee On-Boarding.

To ensure interoperability across file systems, it is recommended that you follow a good naming standard such as POSIX when creating files and folders. For example, folder names can't contain slashes so a folder named '1/2/15' would not be valid.
Create your form or flow as usual. Generate a frevvo-PDF,map to your custom PDFs, upload attachments if required.
Login as a designer user.
Click the Edit icon to open your form/flow.
Click on the what happens to my data? icon on the designer toolbar.
Select the Save to box.com option.
In the wizard that pops up, provide your credentials. You’ll be redirected to login to box if you are logging into your account for the first time.
1. On successful login, you are asked to either grant or deny permission to the scopes specified in the box application that you created earlier. Click the Grant Access to Box button to continue.
2. When granted permission, the Oauth token is generated and stored in . The wizard will login to your box account, browse to find available folders and display them.
Select a parent folder (e.g. Employee On-boarding) and a submission folder. Let's say you want the name of the submission folder that contains the documents to be the new employee's First Name and Last Name,. Use a template that’s dynamically generated e.g. {FirstName} {LastName}. You can select the fields in your form/flow by clicking on the dropdown to the right of the Submission folder field.

Select the types of documents you want to send to box as part of the submission. The choices are:
- Send the data as a PDF attachment or other image type using the Send Snapshot dropdown. The image type options are PDF, PNG or JPG. Select the blank option from the dropdown to exclude this attachment in the submission.
- Attach an XML data document using the Send Data checkbox. This checkbox is checked by default. Uncheck it to exclude the XML data document in the submission.
- Attachments uploaded to your form/flow are included if the Send Files checkbox is checked. This checkbox is checked by default. Uncheck it to exclude attachments in the submission.
- If you have Pixel Perfect mapped PDFs (ex: W-4, I-9 etc…) associated with your forms/flows, choose the action you want to take from the Send Gen Forms control:
  • Check All to send all the Pixel Perfect PDFs. This is the default value.
  • Check None to send none of the PDFs
  • Check Select to display a list of all the PDFs associated with your form/flow. Click the ones you want to be part of the submission. Hold down the Shift key then click the files in the list to select all PDFs or hold the control key and click specific PDFs.
Click Finish.
Save your form or flow by clicking the save and exit icon.

If you do not select a parent and submission folder, submission files are stored under the box account root folder
When the parent folder field is specified and the submission folder is not ,submission files are stored under the parent folder.
When the submission folder field is specified and the parent folder is not, a submission folder is created under account root folder.
Folder names should not contain a / or \

Check Submissions on box.com

When the form or flow is submitted, the documents will be uploaded to your box account in the specified subfolder. All subfolders reside in the parent folder (Employee On-Boarding in our example).

Once in box, you can use all their features to collaborate, share and manage the submission documents.

Follow these steps to verify your stored submissions on box:

Test your form/flow, fill in data, add attachments, sign the form etc. and submit it.
Login to your box account and navigate to the folder you created earlier. See that it now contains a subfolder. The subfolder is dynamically named based on form data e.g. FirstName and LastName fields in the flow. Every time a workflow is submitted a new subfolder is created in this parent folder.
Inside the subfolder, you’ll see the uploaded files e.g. the frevvo generated PDF, a Federal W-4 and I - 9 and the form xml document. You can click on the PDF to preview it directly in the box UI.

Box will not open files without a file extension. Be sure to include the file extension in the name of any acroforms uploaded to for mapping Pixel Perfect PDFs.

Same Named Files show Revision Number on Box

Typically, a new subfolder is created on Box for each submission. Let's say you decide to send a submission to an existing subfolder and in the submission there are file(s) with the same name as file(s) that are already stored in the existing subfolder, It is reasonable to expect that the existing file will be overwritten by the new file with the same name or there will be 2 files with the same name in the existing subfolder .

Box handles this situation by:

Creating a new version of the file and assigning it a revision number
If you are using a free box acocunt, you will only have access to the latest version. For a developer/premium accounts, users can see the version history and download the previous versions of a file if necessary.

For example, an Employee On-boarding for Max Jones stores mapped PDFs of the I-9, W - 4, Connecticut W - 4 and the workflow after the first submission. Max runs through the Employee On-boarding a second time resulting in files with the same name as those generated from the first submission. Viewing the subfolder for Max Jones shows revision numbers for version 2 of each file

Troubleshooting

Doc Post Failure

If the submission doesn't reach box.com, your tenant or flow admin will receive an Doc Post Failure notification email reporting information about the error.

Determine the version of the Box Connector you are using:

To determine the version of the Box connector you are using:

Browse http://<your server:port>/box/info - the version information is returned as shown in the image.

Monitor Box connector Activity

To monitor Box connector activity:

Browse http://<your server:port>/box/trace - trace information is returned as shown in the image.

Uploading a file that exceeds the configured Max file size

The default size configured in the cloud for files uploaded to box.com is 10Mb - the same maximum file size for attachments in . Since users are prevented from uploading files to that exceed the maximum file size value, the files will not be posted to box.com either.

Uploading a file larger than 10 Mb generates the error shown in the frevvo logfile.

15:57:33.731 |-ERROR [http-nio-8082-exec-8] [o.s.b.c.w.ErrorPageFilter] - Forwarding to error page from request [/file] due to exception [Could not parse multipart servlet request; nested exception is java.lang.IllegalStateException: org.apache.tomcat.util.http.fileupload.FileUploadBase$FileSizeLimitExceededException: The field Upload24 exceeds its maximum permitted size of 1048576 bytes.]
org.springframework.web.multipart.MultipartException: Could not parse multipart servlet request; nested exception is java.lang.IllegalStateException: org.apache.tomcat.util.http.fileupload.FileUploadBase$FileSizeLimitExceededException: The field Upload24 exceeds its maximum permitted size of 1048576 bytes.

If you try to upload a file to your form/flow that is bigger than the specified size, users will see this message:

In-house customers can control the max file size by configuring the frevvo.attachment.maxsize parameter in the <frevvo-home>\tomcat\conf\Catalina\localhost\frevvo.xml file.