Section | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
- 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
The Box 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 Some common issues with solutions are listed below.
Box Connector Logfile
If you are using the frevvo tomcat bundle, the Box Connector log is located in <frevvo-home>\tomcat\logs. The logfile is named box.YYYY-MM-DD.log. Searching a separate logfile makes it much easier to search for errors when troubleshooting connector issues. The connector is designed to use the /wiki/spaces/frevvo80/pages/975572178.
The default loglevel for the Box logfile is INFO. To see DEBUG level messages in the Box Connector log:
...
.
...
Code Block |
---|
logging.level.com.frevvo.connector=DEBUG
logging.level.com.frevvo.connectors=DEBUG |
Generate the Box Connector log in JSON format
...
Doc Post Failure
If the submission doesn't reach box.com, all tenant administrators or flow admins (if configured) will receive a Doc Post Failure notification email reporting information about the error.
...