AgentforceForDevelopersSettings | Metadata API Developer Guide

Parent Type and Manifest Access

This type extends the Metadata metadata type and inherits its fullName field.

In the package manifest, all org settings metadata types are accessed using the Settings name. See Settings for more details.

File Suffix and Directory Location

AgentforceForDevelopersSettings values are stored in the AgentforceForDevelopers.settings file in the settings folder. The .settings files are different from other named components because there’s only one settings file for each settings component.

Version

AgentforceForDevelopersSettings are available in API versions 62.0 and later.

Fields

Field Name	Field Type	Description
agentforceForDevelopersOptOut	boolean	Indicates whether Agentforce for Developers is enabled: `true` or `false`. If `true`, Agentforce for Developers isn't enabled in your org, which means that you've opted out of using it. If `false`, Agentforce for Developers is enabled. The default value is `false`.	.

Declarative Metadata Sample Definition

The following is an example of the AgentforceForDevelopers.settings file:

1<?xml version="1.0" encoding="UTF-8"?>
2        <AgentforceForDevelopersSettings xmlns="http://soap.sforce.com/2006/04/metadata">
3        <agentforceForDevelopersOptOut>false</agentforceForDevelopersOptOut>
4        </AgentforceForDevelopersSettings>

The following is an example package.xml manifest that references the previous definition.

1<?xml version="1.0" encoding="UTF-8"?>
2<Package xmlns="http://soap.sforce.com/2006/04/metadata">
3     <types>
4         <members>AgentforceForDevelopersSettings</members>
5         <name>Settings</name>
6     </types>
7     <version>62.0</version>
8</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.