Deprecated. Represents an Scontrol component, corresponding to an s-control in the Salesforce user interface. For more information, see “About S-Controls” in the Salesforce online help. This metadata type extends the MetadataWithContent component and shares its fields.
The file suffix is .scf for the s-control file. The accompanying metadata file is named ScontrolName-meta.xml.
Scontrol components are stored in the scontrols folder in the corresponding package directory.
Scontrols are available in API version 10.0 and later.
This metadata type contains the following fields:
|Field Name||Field Type||Description|
|content||base64Binary||Content of the s-control. Base 64-encoded binary data. Prior to making an API call, client applications must encode the binary attachment data as base64. Upon receiving a response, client applications must decode the base64 data to binary. This conversion is usually handled for you by a SOAP client. This field is inherited from the MetadataWithContent component.|
|contentSource||SControlContentSource||Required. Determines how you plan to use the s-control:
|description||string||Optional text that describes the s-control. This only displays to users with “View All Data” permission (administrator).|
|encodingKey||Encoding (enumeration of type string)||Required. The default encoding setting is Unicode: UTF-8. Change it if you are passing information to a URL that requires data in a different format. This option is available when you select URL as the value for contentSource.|
|fileContent||base64||File contents displayed if you add this s-control to a custom link. The file can contain a Java applet, Active-X control, or any other type of content you want. This option only applies to s-controls with a value of HTML for contentSource.|
|fileName||string||The unique name for the s-control. This name can contain only underscores and alphanumeric characters, and must be unique in your organization. It must begin with a letter, not include spaces, not end with an underscore, and not contain two consecutive underscores. This field cannot be changed for components installed by a managed package. It is only relevant if the fileContent field also has a value. This is a new field in API version 14.0.|
|fullName||string||The s-control developer name used as a unique identifier for API access. The fullName can contain only underscores and alphanumeric characters. It must be unique, begin with a letter, not include spaces, not end with an underscore, and not contain two consecutive underscores. If this field contained characters before version 14.0 that are no longer allowed, the characters were stripped out of this field, and the previous value of the field was saved in the name field. This field is inherited from the Metadata component.|
|name||string||Required. The unique name for the s-control. It must contain alphanumeric characters only and begin with a letter. For example example_s_control.|
|supportsCaching||boolean||Required. Indicates whether the s-control supports caching (true) or not (false). Caching optimizes the page so that it remembers which s-controls are on the page when it reloads. This option only applies to HTML s-controls.|
The following sample creates the Myriad_Publishing.scf s-control, which creates a link to the website specified in the s-control. The corresponding Myriad_Publishing.scf-meta.xml metadata file follows the s-control file.
<?xml version="1.0" encoding="UTF-8"?> <Scontrol xmlns="http://soap.sforce.com/2006/04/metadata"> <contentSource>URL</contentSource> <description>s-control to open Myriad Publishing website.</description> <encodingKey>UTF-8</encodingKey> <name>Myriad Publishing</name> <supportsCaching>true</supportsCaching> </Scontrol>