FileUploadAndDownloadSecuritySettings
File Suffix and Directory Location
FileUploadAndDownloadSecuritySettings components have the suffix .settings and are stored in the settings folder.
Version
FileUploadAndDownloadSecuritySettings components are available in API version 39.0 and later.
Fields
Field Name | Field Type | Description |
---|---|---|
dispositions | FileTypeDispositionAssignmentBean[] | Represents the metadata used to manage filetype behavior. This field is available in API version 39.0 and later. |
noHtmlUploadAsAttachment | boolean | Indicates whether to allow HTML uploads as attachments or document records. This field is available in API version 39.0 and later. |
FileTypeDispositionAssignmentBean
Represents the metadata used to manage filetype behavior.
Field Name | Field Type | Description |
---|---|---|
behavior | FileDownloadBehavior (enumeration of type string) | One of the following values:
|
filetype | FileType (enumeration of type string) | Although more filetypes exist, these are the only ones supported
by FileTypeDispositionAssignmentBean:
|
securityRiskFileType | boolean | Indicates filetypes that cannot have behavior set to EXECUTE, due to security risks. This field is read-only. |
Declarative Metadata Sample Definition
The following is an example of a FileUploadAndDownloadSecuritySettings component.
<FileUploadAndDownloadSecuritySettings xmlns="http://soap.sforce.com/2006/04/metadata">
<dispositions>
<behavior>HYBRID</behavior>
<fileType>AVI</fileType>
<securityRiskFileType>false</securityRiskFileType>
</dispositions>
<dispositions>
<behavior>HYBRID</behavior>
<fileType>WORD</fileType>
<securityRiskFileType>false</securityRiskFileType>
</dispositions>
<dispositions>
<behavior>HYBRID</behavior>
<fileType>WORD_X</fileType>
<securityRiskFileType>false</securityRiskFileType>
</dispositions>
<dispositions>
<behavior>DOWNLOAD</behavior>
<fileType>EXE</fileType>
<securityRiskFileType>true</securityRiskFileType>
</dispositions>
<dispositions>
<behavior>DOWNLOAD</behavior>
<fileType>HTML</fileType>
<securityRiskFileType>true</securityRiskFileType>
</dispositions>
<dispositions>
<behavior>DOWNLOAD</behavior>
<fileType>WEBVIEW</fileType>
<securityRiskFileType>true</securityRiskFileType>
</dispositions>
<dispositions>
<behavior>DOWNLOAD</behavior>
<fileType>RFC822</fileType>
<securityRiskFileType>true</securityRiskFileType>
</dispositions>
<dispositions>
<behavior>HYBRID</behavior>
<fileType>MOV</fileType>
<securityRiskFileType>false</securityRiskFileType>
</dispositions>
<dispositions>
<behavior>HYBRID</behavior>
<fileType>MP3</fileType>
<securityRiskFileType>false</securityRiskFileType>
</dispositions>
<dispositions>
<behavior>HYBRID</behavior>
<fileType>MP4</fileType>
<securityRiskFileType>false</securityRiskFileType>
</dispositions>
<dispositions>
<behavior>HYBRID</behavior>
<fileType>MPEG</fileType>
<securityRiskFileType>false</securityRiskFileType>
</dispositions>
<dispositions>
<behavior>HYBRID</behavior>
<fileType>PDF</fileType>
<securityRiskFileType>false</securityRiskFileType>
</dispositions>
<dispositions>
<behavior>HYBRID</behavior>
<fileType>POWER_POINT</fileType>
<securityRiskFileType>false</securityRiskFileType>
</dispositions>
<dispositions>
<behavior>HYBRID</behavior>
<fileType>POWER_POINT_X</fileType>
<securityRiskFileType>false</securityRiskFileType>
</dispositions>
<dispositions>
<behavior>DOWNLOAD</behavior>
<fileType>SVG</fileType>
<securityRiskFileType>true</securityRiskFileType>
</dispositions>
<dispositions>
<behavior>DOWNLOAD</behavior>
<fileType>FLASH</fileType>
<securityRiskFileType>true</securityRiskFileType>
</dispositions>
<dispositions>
<behavior>DOWNLOAD</behavior>
<fileType>TXML</fileType>
<securityRiskFileType>true</securityRiskFileType>
</dispositions>
<dispositions>
<behavior>DOWNLOAD</behavior>
<fileType>UNKNOWN</fileType>
<securityRiskFileType>true</securityRiskFileType>
</dispositions>
<dispositions>
<behavior>HYBRID</behavior>
<fileType>WAV</fileType>
<securityRiskFileType>false</securityRiskFileType>
</dispositions>
<dispositions>
<behavior>HYBRID</behavior>
<fileType>WMA</fileType>
<securityRiskFileType>false</securityRiskFileType>
</dispositions>
<dispositions>
<behavior>HYBRID</behavior>
<fileType>WMV</fileType>
<securityRiskFileType>false</securityRiskFileType>
</dispositions>
<dispositions>
<behavior>DOWNLOAD</behavior>
<fileType>XHTML</fileType>
<securityRiskFileType>true</securityRiskFileType>
</dispositions>
<dispositions>
<behavior>HYBRID</behavior>
<fileType>EXCEL</fileType>
<securityRiskFileType>false</securityRiskFileType>
</dispositions>
<dispositions>
<behavior>HYBRID</behavior>
<fileType>EXCEL_X</fileType>
<securityRiskFileType>false</securityRiskFileType>
</dispositions>
<dispositions>
<behavior>DOWNLOAD</behavior>
<fileType>XML</fileType>
<securityRiskFileType>true</securityRiskFileType>
</dispositions>
<noHtmlUploadAsAttachment>false</noHtmlUploadAsAttachment>
</FileUploadAndDownloadSecuritySettings>
The following is an example package.xml that references the previous definition.
<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
<types>
<members>FileUploadAndDownloadSecurity</members>
<name>Settings</name>
</types>
<version>39.0</version>
</Package>
Wildcard Support in the Manifest File
The wildcard character * (asterisk) in the package.xml manifest file doesn’t apply to metadata types for feature settings. The wildcard applies only when retrieving all settings, not for an individual setting. For details, see Settings. For information about using the manifest file, see Deploying and Retrieving Metadata with the Zip File.