Error while uploading file <filename>.pdf Extended Response is: Couldn't connect to the Box API due to a network error.
Output Specification
Output Folder Path:
The root folder to output too. Your repository folder structure will be replicated under this directory Output Folder ID:
Another option for selecting the output folder. Folder Ids can be retrieved from the url when viewing the folder in a browser. This will take precedence over path if supplied Include Un-Mapped Properties All metadata will be output, even if no mappings are supplied. These values will be applied as global properties to the file. Date/Date-Time Format Output format for the date. Box is restrictive on this, so changing either is not recommended.
Collaborations
Add Collaborations:
Add collaborations to files written. Collaborations will need to be added as part of a task in the format of [email]=role. The JavaScript task is useful for this. Strip Collaborations:
Will remove all collaborations before adding them. Collaborators Can View Path:
Sets the option to true on a collaboration. The collaborator can see the parent path of the document. Notify Collaborators on Add:
Collaborators will receive an email (not recommended). User ID to add Collaborations (Group Only):
Use a group id instead of an email.
Data
Remove document and previous versions if it fails to fully upload:
Used when outputting versions to Box. If a document is a version series fails to upload, Federation Services will delete the previously uploaded versions as well. They will be counted in the Removed column in the job status page Milliseconds to wait in response eto rate limit errors (multiplies times retries):
Box has a very strict rate limit and will return an error code 429 (Too Many Requests) fairly often. This tells Federation Services how long to wait before automatically retrying the call that failed. Number of retries to attempt before failing a document:
The name says it all. If a file with the name already exists in the parent folder, create a new version:
If unchecked, documents with the same name will fail if a document already in the target folder has the same name Move Files Instead of Write (Box to Box only):
Box has special methods for moving files within the same box organization. If this is checked, Federation Services will use those methods instead of reading and writing content. To do this you will need a task to manipulate the parent path of the document in order to rehome it. Copy Files Instead of Write (Box to Box only):
Same as moving, but box will copy the files to their new location, instead of move them. Pre Cache Folder Structure(experimental):
Federation Services will recursively walk the structure below the target folder and cache their paths and ids. This can take a long time and is not really of use unless there is already content under the target folder. Use Large Files Method on Files over 20 MB:
Will use Box’s large file APIs to more reliably upload large files
This method is currently bugged and will cause an error if called by a Service User account. If you use JWT Authentication, leave this unchecked Only Create Folders:
Works in tandem with pre caching. Prebuild the folder structure, then use a different job that pre-caches to reduce overall times needed to move the content (experimental) Only add template metadata if all listed fields are present:
This field allows you to regulate what fields are allowed to be empty for documents receiving a metadata template