Metadata API Developer Guide
jNote: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.
CaseSubjectParticle
File Suffix and Directory Location
CaseSubjectParticle components have the suffix .CaseSubjectParticle and are stored in the CaseSubjectParticles folder.
Version
Fields
| Field Name | Field Type | Description |
|---|---|---|
| index | int | Required. The order in which the custom Case Subject is generated, meaning if the social network is 0 and the social message is 1, then the subject generates as Twitter | Tweet. |
| textField | string | Specifies inbound social content added to Case Subject in case records. |
| type | CaseSubjectParticleType (enumeration of type string) | Required. Specifies the custom Case
Subject format from which inbound social content
appears in case records. Valid values are:
|
Declarative Metadata Sample Definition
This is a sample of a .CaseSubjectParticle file.
1<?xml version="1.0" encoding="UTF-8"?>
2<Package xmlns=http://soap.sforce.com/2006/04/metadata"">
3 <types>
4 <members>*</members>
5 <name>CaseSubjectParticle</name>
6 </types>
7 <version>41.0</version>
8</Package>Wildcard Support in the Manifest File
This metadata type doesn’t support the wildcard character * (asterisk) in the package.xml manifest file. For information about using the manifest file, see Deploying and Retrieving Metadata with the Zip File.