...
The impersonate user field represents the Google user that will be used to write to. This should be in the form of an email address. If no Team Drive is specified, the release document will be released to this users user's Google Drive location.
If the process expects to write to a Team Drive (this is a shared drive location not associated to a specific user’s account, also called a Shared Drive), provide the ID of the team drive here. The ID can be found in the URL when selecting a team drive in the browser.
The Relative Path specifies where to output the file. ShareFile does not allow the release of files to the root, so a folder path is required. Specify a path, or use notation to create a dynamic path based on data in one or more process fields. Folders, paths (or portions of paths) will be created automatically on demand.
File Name is required, and will become the output file name in the destination. Again, you can use one or more process fields to construct a valid file name. Using the notation {p_OriginalFileName} will name a file based on the original file name processed by GlobalCapture. You might also consider using {PROCESSID} to name a document based on the GlobalCapture process that sourced it.
Use the Allow overwrite option if you want duplicate files to be overwritten. If this option is unchecked and you release a duplicate file, the process WILL NOT error, but the action will be noted in the process history.
Delete files after release should be enabled for any release step that is the last release step in a workflow. This option allows GlobalCapture to clean up after itself. Unchecking this option may be useful in troubleshooting scenarios, but should always be enabled in production workflows.
...