Managing Files in OneTrust Integrations
The Integrations module offers several file transfer options to support the exchange and management of files between external systems or servers integrated with the application.
For more information on other file actions, see Using Create File Actions and Parsing Files with OneTrust Workflows.
Integration workflows can only have one Apply to Each logic action per workflow. This is designed to avoid excessive processing time, as workflows processing for more than 25 minutes will fail. OneTrust recommends to send a second Apply To Each loop to process in a subflow workflow.
OneTrust sends CSV files with capitalized file extensions by design (.CSV vs .csv). Ensure that you are accounting for the capitalization in your system integrations.
HTTP File Upload
You can upload files using multi-part, form-data via PUT or POST action/calls to any endpoint for generic systems that support file uploads. This ability is supported for any action whose account credentials are configured as the HTTP connector type.
Binary file uploads are not supported with this action as OneTrust cannot convert files to binary for sending. See About Cloud SDK & File Transfersfor details on how to support file uploads using binary.
For more information, see Uploading Files with HTTP Actions.
SFTP Read Directory
The Directory from FTP action can be used to assess what files exist in your server's directory. From there you can take additional actions to download or delete them and combine with Apply to Each logic or a Data Transformation action.
For more information on these logic actions, see Using Apply to Each Logic for Integration Workflows and Transforming Responses for Use in Apply to Each Logic.
#DataTransformationExample
<#list 0..step.ftp_0.fileInfoList?size-1 as n>
<#if (step.ftp_0.fileInfoList[n].fileName) == "myFile.csv">
${(step.ftp_0.fileInfoList[n].reference)!}
</#if>
</#list>File Upload
The Upload File to FTP action is useful if you were creating reports within the OneTrust application and need to pass the file to your designated SFTP server. Within the action's Request tab, you would need to define the server path and the given file ID (fileReference) for the created report. You can also include a custom name to override the default name that OneTrust would generate for the file before it is saved to the server.
File Download
The Download File(s) from FTP action can connect to your chosen server and download a file for local use or within the OneTrust application. It requires a user to specify the server path with the file name appended to the end to retrieve the correct file.
OneTrust does not allow downloads of zero byte files. You will receive a workflow execution error if a zero byte file download is attempted.
OneTrust recommends to download one file at at time to increase download speed and avoid workflow timeout issues. Avoid downloading multiple files in a single workflow. If you want to download multiple files from a SFTP folder, we recommend to:
-
Check the directory (Directory from FTP action) to discover all files.
-
Leverage Apply to Each action to perform a download for each file.
-
Download each file to a separate subflow by mentioning the file name within the SFTP download action.
For more information, see Using Apply to Each Logic for Integration Workflows and Using Subflows and Data Transformation in Integration Workflows .
File Deletion
The Delete File from FTP action is an intentional action to remove an unwanted file from your server. In this example, the triggered workflow is downloading the targeted file from the server, posting file's metadata to a Results Summary as data points, and then the workflow targets the file's path for deletion from the server.
This action will permanently delete the file from the desired location. This action cannot be undone, nor can the file be restored by OneTrust.
About Cloud SDK & File Transfers
OneTrust supports file transfers for Azure Blob Storage and Amazon S3 with credentials configured with the Cloud SDK connector type. This allows integration users to leverage seeded options rather than having to chunk calls from using the HTTPS File Upload actions.
When you add a connection for Azure Blob Storage or Amazon S3 via the Integrations Gallery, you can leverage the Cloud SDK credential along with the seeded actions to perform file transfers unique to each system (e.g. containers, buckets).
