Metadata API Developer Guide
jNewer Version Available
OmniChannelSettings
In the package manifest, all organization settings metadata types are accessed using the “Settings” name. See Settings for more details.
File Suffix and Directory Location
OmniChannelSettings values are stored in the OmniChannel.settings file in the settings folder. The .settings files are different from other named components because there is only one settings file for each settings component.
Version
OmniChannelSettings components are available in API version 44.0 and later.
Fields
| Field Name | Field Type | Description |
|---|---|---|
| enableOmniChannel | boolean | Indicates whether Omni-Channel is enabled, giving you access to the objects needed to set up the feature in your org. |
| enableOmniSkillsRouting | boolean | Indicates whether skills-based routing is enabled in your org. |
Declarative Metadata Sample Definition
The following is an example of a OmniChannelSettings component.
The following is an example package.xml that references the previous definition.
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.