DynamicFulfillmentOrchestratorSettings

Represents the settings for Dynamic Revenue Orchestrator.

Parent Type and Manifest Access 

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

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

File Suffix and Directory Location 

DynamicFulfillmentOrchestratorSettings values are stored in the DynamicFulfillmentOrchestratorSettings.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 

DynamicFulfillmentOrchestratorSettings components are available in API version 61.0 and later.

Fields 

Field NameField TypeDescription
enableDFOFalloutbooleanIndicates whether to enable fallout management to handle fallouts and retry policies (true) or not (false). The default value is false. See Turn On Feature to Manage Fallout.
enableDFOJeopardybooleanIndicates whether to enable management of Service Level Agreements (true) or not (false). The default value is false. See Turn On Feature to Manage Service Level Agreements.
enableDFOPrefbooleanIndicates whether to enable features of Dynamic Revenue Orchestrator (true) or not (false). The default value is false. See Turn On Dynamic Revenue Orchestrator.
enableDROFutureDatedTasksbooleanIndicates whether to enable the Future Dated Steps feature (true) or not (false). The default value is false. See Enable Future Dated Steps. Available in API version 63.0 and later.
enableDROInflightRequestbooleanIndicates whether to allow changes to fulfillment requests that are in progress (true) or not (false). The default value is false. Available in API version 64.0 and later.
enableDROTaskSourcebooleanIndicates whether to link a Salesforce manual task to a fulfillment step source (true) or not (false). The default value is false. See Enable the Linking of Task to Step Source. Available in API version 63.0 and later.

Declarative Metadata Sample Definition 

The following is an example of a DynamicFulfillmentOrchestratorSettings component.

1<DynamicFulfillmentOrchestratorSettings xmlns="http://soap.sforce.com/2006/04/metadata">
2     <enableDFOPref>true</enableDFOPref>
3     <enableDFOFallout>true</enableDFOFallout>
4     <enableDFOJeopardy>true</enableDFOJeopardy>
5     <enableDROFutureDatedTasks>true</enableDROFutureDatedTasks>
6     <enableDROInflightRequest>true</enableDROInflightRequest>
7     <enableDROTaskSource>true</enableDROTaskSource>
8</DynamicFulfillmentOrchestratorSettings>

The following is an example package.xml 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>DynamicFulfillmentOrchestrator</members>
5        <name>Settings</name>
6    </types>
7    <version>68.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.