Tips and FAQ

Yes. Cloud Elements does perform the x-dropbox-signature validation for handling Dropbox events.

We are in the process of normalizing the documents hub even further, but there are always a few unique API provider differences and the 'ID' used to make a GET by the root folder ID is one such difference.

Currently the following values can be used in these elements to make GET calls directly against the root folder by ID (for example, GET /folders/{id}/contents or GET /folders/{id}/metadata).

• Box: 0. For example GET /folders/0/contents.
• Dropbox: Double URL-encoded path: %252F. For example, GET /folders/%252F/contents.
• Google Drive: root.  For example, GET /folders/root/contents.
• OneDrive: root. For example, GET /folders/root/contents.
• ShareFile: Whatever value was input at instance provision as the Sharefile root folder, such as top. For example, GET /folders/top/contents.

If you do not permanently delete Dropbox files, they remain in your Trash folder and generate an UPDATED event type if they are re-created.

Dropbox includes a refId for certain APIs. This is the actual ID of the file sent back from Dropbox. It can be used as the ID with all API calls with the exception of GET /folders/{id}/contents.

The GET /folders/{id}/contents endpoint does not support the refId at this time.

In Dropbox, file links can only have one shared link at a time for a given file. This means if you generate a file link that has the default visibility of 'PUBLIC' then any subsequent calls to GET /files/{id}/links or GET /files/links will simply return the existing PUBLIC link rather than generating a new link. This is true even if you are trying to generate a new link with a different level of access such as visibility=TEAM_ONLY. Therefore if you need to create a new file link for any reason you will first need to revoke/delete the original file link and then generate a new file link.

Within the Dropbox element, this is accomplished by:

1. Create a new file link - in this example the link is generated based on the file path, but the same is true for links generated by file ID as well:
   GET /files/links

   { 
   "cloudElementsLink": "https://api.cloud-elements.com/elements/api-v2/external/documents/files?key=XXXXXXXXXX", 
   "providerViewLink": "https://www.dropbox.com/s/XXXXXXXXXX/yourFile.pdf?dl=0", 
   "providerLink": "https://www.dropbox.com/s/XXXXXXXXXX/yourFile.pdf?dl=1"
   }

2. Note that if you call GET /files/links again the same provider links will be returned. The cloudElementsLink url will be updated, but it will still point to the original provider link ID.
3. Revoke this file link and confirm a successful 200 response.
   DELETE /files/links
4. Now you can create a new file link.
   GET files/links
   

   { 
   "cloudElementsLink": "https://api.cloud-elements.com/elements/api-v2/external/documents/files?key=YYYYYYYYYY", 
   "providerViewLink": "https://www.dropbox.com/s/YYYYYYYYYY/yourFile.pdf?dl=0", 
   "providerLink": "https://www.dropbox.com/s/YYYYYYYYYY/yourFile.pdf?dl=1"
   }

If you enable the Document Hub Tagging (document.tagging) configuration parameter with certain elements from the Documents hub, the paths and tags for any documents accessed will be stored in the Cloud Elements database in clear text. Affected elements include a mention of this in their respective descriptions of the parameter.

Documents elements affected include:

• Dropbox
• Dropbox Business
• Egnyte
• Google Drive
• Sharepoint
• Syncplicity

See our Data Protection & Privacy documentation for specifics about our data storage and security policies.